As a heads-up, had a problem with one of our Buster servers last night at pretty much bang on midnight when it stopped responding to http/https requests (not sure if thats when sympl updates would roll out?)
I’m struggling to work out the exact issue, and it’s only affected one server so far out of about 10. (I do know this server still looks to be running mod-php rather than fpm, the other servers are probably all fpm. We haven’t changed anything on the site for probably best part of a year)
I’ve narrowed it down to apache disliking zz-mass-hosting.ssl.conf for some reason - if i run apachectl configtest it says the syntax is okay, if i restart apache it bails with it in use (and annoyingly can’t see a reason why in the logs other than it just exits). If i unlink zz-mass-hosting.ssl.conf from sites-enabled then apache’s happy to start again (seems okay with the non-ssl version, which suggests maybe something to do with ssl).
Would anything have changed with zz-mass-hosting.ssl.conf in the latest release?
Can’t see anything obvious amiss in it’s vhost entry, and as i said it passes configtest so i’m at a bit of a loss as to what’s up with it (we don’t actually use the zz-mass-hosting so I’ve just removed it from sites-enabled to get the site up and running again)
(Just to mention, I’ve split this into it’s own topic under support, and contacted @tricky for some more info to see if I can identify the issue, although I don’t think it’s related to the other recent issue with new installs.)
It sounds like these are containers, rather than proper virtual machines (with their own disks, BIOS, etc), especially with Debian Bullseye on a 4.19 kernel.
From what I can tell the iomart setup isn’t entirely full VMs (ie: typical boot times, BIOS, install from ISO, etc), and I’m not confident their ‘migrations’ went as planned as they seemed to have halted them with no further info on migrating users.
Looking at the Hostinger site, it may be a similar container-based thing there also (at least for their VPS product).
If you want to reimage and send me credentials via a PM, I can take a quick look.
As a side note, I thought this may have been a dependency issue, with a missing package in some images, but having imaged VMs with Debian 10 and 11 netboot images with nothing included, everything at least seems to work as expected.
Just to answer this publicly for anyone else who may come across it, that looks to be because the Hostinger VPSs are actually containers running on a Redhat host, and are missing a few standard Debian packages like dbus (you can install it manually with apt install dbus). I’ll add that to the dependences for sympl-core, but you’re likely to run into other issues.
Apart from that, while things are mostly configured as normal, Sympl doesn’t seem to be able to get the IPs on the network interface - this is old Symbiosis code so I’ll need to look into how it’s trying to query things, and there are ways around it to get web services up and running, but things like sympl-firewall aren’t going to work by default.
If anyone else encounters this issue, you’re probably best looking at a full VM in the medium to long term until this can be identified and changes made to Sympl to support it.
As always, I’d suggest Mythic Beasts virtual servers, as they’re full VMs similar to the old BigV setups, running stock Debian images, and they provide a great deal of support to the project!