Howdy, Stranger!

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


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
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.

How long does it take for your VPS to reboot?

networknetwork Member
edited July 2024 in General

I recently bought a cheap VPS from RackNerd. I have a few VPSs from Hetzner and DO. Rebooting Hetzner and DO VPSs takes about 20-30 seconds (the time between when I press enter after typing "reboot" in SSH and the time I'm able to SSH into the VPS again) while my $1.5/month RackNerd VPS takes about 150 seconds.

Curious to hear how long it takes on other low end hosts.

Comments

  • Go check dmesg. Possibly a failed service blocked your booting process.

    Thanked by 1network
  • @Kousaka said:
    Go check dmesg. Possibly a failed service blocked your booting process.

    Wow thanks!! Found https://askubuntu.com/questions/949713/systemd-networkd-wait-online-service-causing-artful-to-take-over-2-minutes-to-bo and based on a suggestion there, added a timeout to systemd-networkd-wait-online.service, now boot takes around 30 seconds!

    systemd-analyze blame was showing that systemd-networkd-wait-online.service was taking over 2 minutes.

    Thanked by 2MikeA Tony40
  • @network said:

    @Kousaka said:
    Go check dmesg. Possibly a failed service blocked your booting process.

    Wow thanks!! Found https://askubuntu.com/questions/949713/systemd-networkd-wait-online-service-causing-artful-to-take-over-2-minutes-to-bo and based on a suggestion there, added a timeout to systemd-networkd-wait-online.service, now boot takes around 30 seconds!

    systemd-analyze blame was showing that systemd-networkd-wait-online.service was taking over 2 minutes.

    I still recommend investigating why it failed in the first place. Maybe DHCP issue or wrong interface name, but in case it is a server, you can just configure static address and route.

  • It's not uncommon for cheaper VPS providers to have longer reboot times due to potentially slower hardware or shared resources.
    The Windows OS may occasionally take longer to load because of updates, but in Linux, it should not exceed 20 seconds.
    If the longer reboot time is causing issues for you, it may be worth reaching out to RackNerd's support team to see if there are any optimizations.

  • bootboot Barred

    Thanked by 1Calin
  • ArrowBoiArrowBoi Member
    edited July 2024

    @boot said:

    I actually wanna know, when that shows up on hetrix, do I reboot it or let it be?

    cuz idk what to do about this

  • zGatozGato Member

    @ArrowBoi said:

    @boot said:

    I actually wanna know, when that shows up on hetrix, do I reboot it or let it be?

    cuz idk what to do about this

    nah nothing to worry about

    Thanked by 2ArrowBoi boot
  • farsighterfarsighter Member
    edited July 2024

    17 seconds here (Hetzner) until I get a ping. Tested using a while loop that checks every second from another server terminal so it's anywhere between 16-17 seconds

    Thanked by 1network
  • yoursunnyyoursunny Member, IPv6 Advocate

    Advanced idler never reboot their VPS.
    Buy - install - YABS - UptimeRobot - idle until expire or sold.

  • ralfralf Member

    @Kousaka said:
    Go check dmesg. Possibly a failed service blocked your booting process.

    Most of the problems I've had with slow reboots have actually been on shutdown. Things like database servers not quitting for a minute and then being kill -9'd and the actual reboot taking 5-10 seconds.

  • NJa64FNJa64F Barred

    so if you never reboot are you live patching the kernel or just not updating it ?
    Is there free live patching for Debian ?

  • IdlingIdling Member

    Racknerd has VNC viewer, you can view the boot process in real time there, it can be very helpful.

  • AndletAndlet Member

    Just 5s

  • emghemgh Member, Megathread Squad

    @jperkins said:
    so if you never reboot are you live patching the kernel or just not updating it ?
    Is there free live patching for Debian ?

    No

    Ubuntu’s free plan comes with LivePatch though, up to 5 machines for free I believe

  • NJa64FNJa64F Barred

    @emgh said:

    Ubuntu’s free plan comes with LivePatch though, up to 5 machines for free I believe

    thanks for the reply. just remembered why I went back to Debian

    sudo snap install canonical-livepatch

  • emghemgh Member, Megathread Squad

    @jperkins said:

    @emgh said:

    Ubuntu’s free plan comes with LivePatch though, up to 5 machines for free I believe

    thanks for the reply. just remembered why I went back to Debian

    sudo snap install canonical-livepatch

    I highly doubt a snap install will make LivePatch work on a non-Canonical kernel

  • emghemgh Member, Megathread Squad

    @totally_not_banned you know this?

  • NJa64FNJa64F Barred

    @emgh said:

    I highly doubt a snap install will make LivePatch work on a non-Canonical kernel

    I agree. rebooting isnt a big issue for me. Was just curious about the long uptimes if they were forgoing kernel updates to keep the service up

    Thanked by 1emgh
  • edited July 2024

    @emgh said:
    @totally_not_banned you know this?

    You mean LivePatch working with non-Ubuntu kernels? No, it 99% won't. That 1% is Cononical playing Mother Theresa and actually supplying patch sets for Debian (or whatever other kernel build) and saying that's highly unlikely is probably already a bit of an understatement.

    I'm a bit surprised that noone took up the task of hosting the patches for Debian yet. I mean at least for a single arch (probably amd64) it shouldn't be that much of a hassle, should it? At least when i read up on it building the patches seemed pretty straight forward.

    Thanked by 1emgh
  • In addition to the fact that installing snap packages on Debian is blasphemy

    Thanked by 1totally_not_banned
Sign In or Register to comment.