Me to #DigitalOcean support: my droplet has been running for a few days and then kernel panicking with errors in the block layer requiring a reboot, I think there might be a drive problem.
DO support: If your droplet won't boot, it's probably the boot loader [boot loader troubleshooting paste].
Me: ...
I've been happy with these guys for a long time, but this is not confidence-inspiring.
=> More informations about this toot | More toots from elb@social.sdf.org
Oh good another first liner came back and said he sees some 100% CPU usage and gave me a bunch of links to generic performance monitoring advice, including a slashdot article. Meanwhile the highest CPU usage I see on the graph is THE NODE REBOOTING AFTER THE KERNEL PANIC and it's not near 100%.
=> More informations about this toot | More toots from elb@social.sdf.org
Update! A new first-line tech support guy came along, told me it's a boot problem again, and gave me some hints on how to fsck and attach to the recovery console.
None of them have addressed the fact that it's a kernel panic, nor do any of them seem to have any idea what a kernel panic is. Or maybe they're just not even reading the ticket?
=> More informations about this toot | More toots from elb@social.sdf.org
@elb I've been hosting on UpCloud and pleased with the performance, especially the MaxIOPS storage. Here's a €25 credit https://upcloud.com/signup/?promo=B9R57Y
=> More informations about this toot | More toots from kai@ajin.la This content has been proxied by September (3851b).Proxy Information
text/gemini