Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › I purchased a low end service and its performing like a low end service - Page 4
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

I purchased a low end service and its performing like a low end service

124»

Comments

  • BruhGamer12BruhGamer12 Member

    @emgh said:

    @BruhGamer12 said:
    You should leak their costumer database online as proper revenge obviously.

    I'll ask if I can buy it (gonna dispute anyway)

    You seem to know a lot about disputes. Hetzner banned my account and sent me to collections over $0.06 unpaid because I forgot(true story) How do I dispute that with my bank?

    Thanked by 1emgh
  • emghemgh Member

    @BruhGamer12 said:

    @emgh said:

    @BruhGamer12 said:
    You should leak their costumer database online as proper revenge obviously.

    I'll ask if I can buy it (gonna dispute anyway)

    You seem to know a lot about disputes. Hetzner banned my account and sent me to collections over $0.06 unpaid because I forgot(true story) How do I dispute that with my bank?

    Tell them that you've changed your mind since you bought it.

    @Void said:

    @BruhGamer12 said:
    You should leak their costumer database online as proper revenge obviously.

    Not before demanding $200 ransom money

    Nice! Free provider tag! :blush:

    Thanked by 1shruub
  • VoidVoid Member

    @emgh said:

    Nice! Free provider tag! :blush:

    lol no, not all $200 is related to provider tag

  • wotetiwoteti Member

    @BruhGamer12 said:
    You seem to know a lot about disputes. Hetzner banned my account and sent me to collections over $0.06 unpaid because I forgot(true story) How do I dispute that with my bank?

    You should pay the collections firm $0.07 then send another collections firm to haunt their ass over the $0.01 they owe you.

    REVENGE!

    Thanked by 2emgh shruub
  • zw1tt3r1onzw1tt3r1on Member

    these low end services are supposed to be for running low end stuff anyways

    Thanked by 1emgh
  • Daniel15Daniel15 Veteran
    edited February 18

    @zGato said:

    @oplink said:
    Stop buying 1GB crappy vps accounts. That's the problem with some of the sub 5/mo accounts. Our smallest shared vCPU plans are 2vcore and 4GB ram! These specs are slowly becoming the normal as OSs are needing more and more resources.

    debian 12 runs just fine even with 512MB KVM ;)
    I even told you on DMs the use case of these "crappy 1GB boxes" but whatever.

    Debian 12's minimum is actually 256MB RAM: https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html. They 'recommend' 512 MB RAM, but 13 of the servers for dnstools.ws are 256MB RAM and 5GB disk with Debian 12. Works fine with plenty of RAM to spare. The software for the DNSTools nodes (https://github.com/Daniel15/dnstools/tree/master/src/DnsTools.Worker) uses around 50MB RAM.

    Thanked by 3emgh crunchbits shruub
  • zGatozGato Member

    @Daniel15 said:

    @zGato said:

    @oplink said:
    Stop buying 1GB crappy vps accounts. That's the problem with some of the sub 5/mo accounts. Our smallest shared vCPU plans are 2vcore and 4GB ram! These specs are slowly becoming the normal as OSs are needing more and more resources.

    debian 12 runs just fine even with 512MB KVM ;)
    I even told you on DMs the use case of these "crappy 1GB boxes" but whatever.

    Debian 12's minimum is actually 256MB RAM: https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html. They 'recommend' 512 MB RAM, but 13 of the servers for dnstools.ws are 256MB RAM and 5GB disk with Debian 12. Works fine with plenty of RAM to spare. The software for the DNSTools nodes (https://github.com/Daniel15/dnstools/tree/master/src/DnsTools.Worker) uses around 50MB RAM.

    Debian 11 KVM won't run on 256MB. OpenVZ or some other shared kernel virtualization will make it work though.
    Some stripped down templates might make KVM work though.

    Thanked by 1oplink
  • emghemgh Member

    @Daniel15 said: Debian 12's minimum is actually 256MB RAM: https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html

    Isn't that Debian 11 though?

  • emghemgh Member

    Although same RAM requirements for 12: https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html

  • oplinkoplink Member, Patron Provider

    @Daniel15 said:

    @zGato said:

    @oplink said:
    Stop buying 1GB crappy vps accounts. That's the problem with some of the sub 5/mo accounts. Our smallest shared vCPU plans are 2vcore and 4GB ram! These specs are slowly becoming the normal as OSs are needing more and more resources.

    debian 12 runs just fine even with 512MB KVM ;)
    I even told you on DMs the use case of these "crappy 1GB boxes" but whatever.

    Debian 12's minimum is actually 256MB RAM: https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html. They 'recommend' 512 MB RAM, but 13 of the servers for dnstools.ws are 256MB RAM and 5GB disk with Debian 12. Works fine with plenty of RAM to spare. The software for the DNSTools nodes (https://github.com/Daniel15/dnstools/tree/master/src/DnsTools.Worker) uses around 50MB RAM.

    Thanks for the use case info for a tiny vps. I guess I need to consider adding a 1GB 1Core plan back to our website.

  • emghemgh Member
    edited February 18

    I just set up Debian 12 on a 2 GB VPS (I think).

    Shut it down.

    Changed to 256 MB.

    Kernel panic not syncing system is deadlocked on memory.

    Virtfusion ISO, so I guess they might modify it A BIT but probably not that much?

    Thanked by 1zGato
  • Daniel15Daniel15 Veteran
    edited February 18

    @zGato said:

    @Daniel15 said:

    @zGato said:

    @oplink said:
    Stop buying 1GB crappy vps accounts. That's the problem with some of the sub 5/mo accounts. Our smallest shared vCPU plans are 2vcore and 4GB ram! These specs are slowly becoming the normal as OSs are needing more and more resources.

    debian 12 runs just fine even with 512MB KVM ;)
    I even told you on DMs the use case of these "crappy 1GB boxes" but whatever.

    Debian 12's minimum is actually 256MB RAM: https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html. They 'recommend' 512 MB RAM, but 13 of the servers for dnstools.ws are 256MB RAM and 5GB disk with Debian 12. Works fine with plenty of RAM to spare. The software for the DNSTools nodes (https://github.com/Daniel15/dnstools/tree/master/src/DnsTools.Worker) uses around 50MB RAM.

    Debian 11 KVM won't run on 256MB. OpenVZ or some other shared kernel virtualization will make it work though.
    Some stripped down templates might make KVM work though.

    It works fine as long as you use the 32-bit version (which is called "i386" even though it's an i686 build 🤔).

    Installer runs fine. It runs in "low memory" mode, complains that it needs at least 273MB RAM, and you have to select which components to load. nic-modules, partman-auto and partman-ext3 are sufficient.

    Works fine though.

    The graphics get a bit corrupted towards the end, but it doesn't affect the functionality

    It boots fine, with 195MB RAM available: (totally fine for DNSTools since the nodes only need ~50MB RAM)

    64-bit installs fine, but deadlocks on RAM availability at boot:

    The deadlock happens when the initrd (initial RAM disk) is being decompressed. There's just not enough RAM for the initrd, the kernel, and the kernel memory+buffers. It could potentially be worked around if the initrd could be reduced in size plus a custom kernel with fewer options to reduce the disk space required. Once the kernel boots, the initrd is unmounted, so if you can get past the boot then it should work fine. The initrd has all the drivers that the kernel requires to boot.

    Thanked by 2emgh sh97
  • ChrisMillerChrisMiller Member

    @emgh said: I’m SHOOK

    Thanked by 1emgh
  • emghemgh Member

    @Daniel15 Ah yes, used 64 bit

  • DataIdeas-JoshDataIdeas-Josh Member, Patron Provider

    @emgh said:
    I just set up Debian 12 on a 2 GB VPS (I think).

    Shut it down.

    Changed to 256 MB.

    Kernel panic not syncing system is deadlocked on memory.

    Virtfusion ISO, so I guess they might modify it A BIT but probably not that much?

    I've been seeing more issues with Ubuntu on 10GB of space.

  • Daniel15Daniel15 Veteran

    @emgh said:
    @Daniel15 Ah yes, used 64 bit

    There's no real advantage of 64-bit on a system with only 256MB RAM. 64-bit uses quite a bit more RAM, as all pointers are double the size (64-bit instead of 32-bit).

    Debian's going to discontinue their 32-bit build soon (they're the last distro to support it), but I think the lowest-end VPSes will increase to 512MB at some point. It keeps increasing over time. 10+ years ago, "low end" meant 128MB or even 64MB RAM.

    Thanked by 1emgh
  • emghemgh Member
    edited February 19

    @Daniel15 said:

    @emgh said:
    @Daniel15 Ah yes, used 64 bit

    There's no real advantage of 64-bit on a system with only 256MB RAM. 64-bit uses quite a bit more RAM, as all pointers are double the size (64-bit instead of 32-bit).

    Debian's going to discontinue their 32-bit build soon (they're the last distro to support it), but I think the lowest-end VPSes will increase to 512MB at some point. It keeps increasing over time. 10+ years ago, "low end" meant 128MB or even 64MB RAM.

    Yeah. Realistically, it’ll increase to Debian’s minimum without tuning for 64bit (512 MB)

    However, plenty providers already start at 1 or even 2 GB, and it does make sense as for many of them, the IP cost is way higher than the RAM cost at less RAM for IPv4

  • shruubshruub Member

    @Daniel15 said:

    @zGato said:

    @Daniel15 said:

    @zGato said:

    @oplink said:
    Stop buying 1GB crappy vps accounts. That's the problem with some of the sub 5/mo accounts. Our smallest shared vCPU plans are 2vcore and 4GB ram! These specs are slowly becoming the normal as OSs are needing more and more resources.

    debian 12 runs just fine even with 512MB KVM ;)
    I even told you on DMs the use case of these "crappy 1GB boxes" but whatever.

    Debian 12's minimum is actually 256MB RAM: https://www.debian.org/releases/bullseye/amd64/ch03s04.en.html. They 'recommend' 512 MB RAM, but 13 of the servers for dnstools.ws are 256MB RAM and 5GB disk with Debian 12. Works fine with plenty of RAM to spare. The software for the DNSTools nodes (https://github.com/Daniel15/dnstools/tree/master/src/DnsTools.Worker) uses around 50MB RAM.

    Debian 11 KVM won't run on 256MB. OpenVZ or some other shared kernel virtualization will make it work though.
    Some stripped down templates might make KVM work though.

    It works fine as long as you use the 32-bit version (which is called "i386" even though it's an i686 build 🤔).

    Installer runs fine. It runs in "low memory" mode, complains that it needs at least 273MB RAM, and you have to select which components to load. nic-modules, partman-auto and partman-ext3 are sufficient.

    Works fine though.

    The graphics get a bit corrupted towards the end, but it doesn't affect the functionality

    It boots fine, with 195MB RAM available: (totally fine for DNSTools since the nodes only need ~50MB RAM)

    64-bit installs fine, but deadlocks on RAM availability at boot:

    The deadlock happens when the initrd (initial RAM disk) is being decompressed. There's just not enough RAM for the initrd, the kernel, and the kernel memory+buffers. It could potentially be worked around if the initrd could be reduced in size plus a custom kernel with fewer options to reduce the disk space required. Once the kernel boots, the initrd is unmounted, so if you can get past the boot then it should work fine. The initrd has all the drivers that the kernel requires to boot.

    I wonder, is myunraid.net your domain or is that included in the unraid subscription?

  • Daniel15Daniel15 Veteran
    edited February 19

    @shruub said: wonder, is myunraid.net your domain or is that included in the unraid subscription?

    It's part of Unraid that allows you to use HTTPS for a local server without having to use your own domain. They copied Plex's approach, which you can read about here: https://words.filippo.io/how-plex-is-doing-https-for-all-its-users/

    Essentially, each user has a subdomain under myunraid.net or plex.direct that's a hash of some sort, and they automatically issue a wildcard TLS certificate for that subdomain (*.de0bbbdfce5c.......myunraid.net). Then, every subdomain under that is just an IP, for example the 10-1-1-12.de0bb.......myunraid.net resolves to 10.1.1.12.

    They do have a remote access feature that also uses this domain, but I don't use that. I use a VPN (Tailscale) for remote access.

    Thanked by 1shruub
  • shruubshruub Member

    @Daniel15 said:

    @shruub said: wonder, is myunraid.net your domain or is that included in the unraid subscription?

    It's part of Unraid that allows you to use HTTPS for a local server without having to use your own domain. They copied Plex's approach, which you can read about here: https://words.filippo.io/how-plex-is-doing-https-for-all-its-users/

    Essentially, each user has a subdomain under myunraid.net or plex.direct that's a hash of some sort, and they automatically issue a wildcard TLS certificate for that subdomain (*.de0bbbdfce5c.......myunraid.net). Then, every subdomain under that is just an IP, for example the 10-1-1-12.de0bb.......myunraid.net resolves to 10.1.1.12.

    They do have a remote access feature that also uses this domain, but I don't use that. I use a VPN (Tailscale) for remote access.

    That is amazing! Thanks for the detailed explanation!

Sign In or Register to comment.