My Linode has been up for more than a year!

That's a really bad idea…

Not sure why, running very smooth.

@ljhardy:

Not sure why, running very smooth.
You need to reboot to get kernel updates.

What would be a best practice in terms of how often to reboot?

@ljhardy:

What would be a best practice in terms of how often to reboot? Immediately after Linode makes any kernel update available. 143 hours after Linode makes any kernel update available. It's up to you.

If you want kernel updates without rebooting, look into something like ksplice.

@ljhardy:

Not sure why, running very smooth.

How much have you installed in the meantime. Are you sure it'll come back up?

@OverlordQ:

@ljhardy:

Not sure why, running very smooth.
How much have you installed in the meantime. Are you sure it'll come back up?
THIS. Always* reboot after doing major installs. Otherwise it WILL bite you in the ass.

• And/or make copious notes about what you've done.

Or if you want enforced, semi-regular reboots, you could just run in the Fremont datacenter… :wink: :wink:

Yeah, those of us with the 'pleasure' of being in fremont know pretty well whether our systems come up ok after a hard power off…

It should be noted that, since the above graph is live, it currently lists an uptime of 9 days ;)

@Guspaz:

the above graph is live
Ha, I didn't notice that. It seems that OP rebooted his Linode twice in the 3 weeks since hitting his 385-day uptime record. Since the Linode is definitely not in Fremont, we could assume that these were probably user-initiated reboots.

@jords:

Yeah, those of us with the 'pleasure' of being in fremont know pretty well whether our systems come up ok after a hard power off…

This is probably the best feature of the Fremont datacentre :P

@ljhardy:

…
Which Data Center do you use?

@TheClient:

@ljhardy:

…
Which Data Center do you use?
It looks like they're in the Dallas DC.