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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
@gigahost is patching their hosts right now.
OVH released information about mandatory maintenance today https://public-cloud.status-ovhcloud.com/incidents/m5qn00qgl9zh even though many instances were already rebooted yesterday.
They seems to be completely paralyzed by this and the problems it caused. I'm waiting for manual reboot of dedicated server with failed IPMI ~12h and it seems there is no one available to do it..
Lmao that's quite a list from OVH. They couldn't just say "This scheduled maintenance affects: Everywhere"?
Should we put in a cancellation for any hosts that show no sign of patching?
Actually, I’m used to applying routine patches without notifying customers, so I don’t really see why I should change that. Do you think it’s important?
There are many reasons to keep systems up to date, and we’ve applied a number of important security-related patches over the last few months. In my experience, though, most customers aren’t particularly interested in receiving an announcement every time routine maintenance is performed.
In my opinion, as a paying customer of a service provider, I shouldn’t have to worry about those things in the first place. That’s exactly what I’m paying the provider to take care of.
@berohost
patched. talked to the man on discord.
common prohosting24 W
wow thank you
i have patched my macos so im good. Safe here. Use protection always. You have no "backdoor" into me. Weirdo.
@NDTN Did you patch for this @ Greencloud because only my Singapore VPS went down briefly for scheduled maintenance. Amsterdam and UK VPSes are unaffected, were they patched?
I think this was patched 2 days ago, as per their email.
I have not patched my private KVM node yet.
i am all in vaccine stocks, LETS GOOOOOOOO
Yes per: https://lowendtalk.com/discussion/comment/4829201/#Comment_4829201
Thank you
So nobody uses kernelcare?
They are slow in preparing a livepatch for some weird reason, still no fix for Almalinux 9
Pricing probably add up for a lot of systems on a large scale and really wasn't needed until AI dissected everything, especially for isolated environments. (edited my post but I am running KC on web hosting servers now since they're not very isolated)
I think in cases where there is a known security issue in which a VPS could be used to either crash the node or potentially gain admin privileges on the host node, that its important for providers to share what they have done to protect against it. Hopefully these types of things remain rare.
Cost is like $5/month per hypervisor, and most hypervisors these days have what, like 50+ customers on them each? That's only $0.1 per user.
I suppose you're right, but this is LET.
With price increases for everything every year, adding more and more recurring costs add up, and those recurring costs will have price increases of their own. It goes the same for transaction fees, some of these for low end services are like 10% of the recurring fee, but people would hate it if the TX fees were added upfront.
Probably 98% of people are OK with a quick reboot to apply security patches. I had only one person contact me during my reboots over the past week.
I just did some research and it is so easy to DIY live patches now. You just apt install the linux source for the kernel you are on, and use an app called kpatch and feed it a diff.
Is anyone experiencing issues with Layer7 Germany location? France is active, but I haven’t been able to connect to the Germany VPS for more than an hour. Could it be some kind of update? Anyone else having trouble?
congratulations, your downtime has been doubled.
Oh wow, what a funny thing…
yes. I have the €5/mo 5TB deal in Germany, and I haven't been able to access it for ~3hr
I had the same issue; for me, it worked again after I stopped and restarted it in the panel (in the web VNC it looked like it was on, but it didn't react to keyboard inputs; nothing in the logs).
I also have the 5€/mo 5 TB VPS. (Pretty sure that this was the first real downtime of that server in over a year; very reliable.)
While I'm not having any issue anymore, tagging @layer7 just in case (though I would assume someone has opened a ticket).
Thanks, power off/on worked. Reset hadn’t worked. Yes, it was the first downtime
Hi,
yes, perfect morning :-) ;-;
I had too much faith in proxmox / ZFS -- not exactly sure which one to blame --, turned out to be a bad idea to have too much faith ;-;
Just like mentioned already in the tickets, this was storage related.
But not because the storage is defective or full, but because proxmox thought its full.
Lead to proxmox bringing up an error IO flag ( seems to be new?! ) and blocking all IO.
All that needed to be done is power off -> power on. But most customers did not do that or just tried a software reset, that did not help.
Up to 3h downtime until we did this power off -> on for all instances ourselves...
Sorry for that!