I've been running arch on a VPS for years now, never had any serious problems until this:
When I updated systemd from 204-3 to 208-10, the VPS stopped booting.
I was able to downgrade systemd and systemd-sysvcompat to 204-3 and the VPS rebooted normally.
This is starting to become a problem because since I upgraded dbus (1.6.18-1 -> 1.6.18-3), my syslog is empty.
On top of that I've had to keep libgcrypt <= 1.5.3-1 because otherwise systemd 204 doesn't work any more.
I would like to fix this before any more problems pile up.
My VPS provider uses OpenVZ, with the latest RHEl6 build ( 2.6.32-042stab084.17 ) via ksplice/uptrack.
The vzctl logs from my provider do not say anything helpful, and like I was describing,
my syslogs have been empty for a while so nothing in there either...
Anyone have any insight on what is going on?
Last edited by thanil (2014-01-24 19:56:28)
Hi falconindy and thanks for the reply,
Since my VPS provider doesn't plan to update their kernel, what do you recommend I do? Is there any hope in using arch on VPS?
How recent should their kernel be to support arch? Is there a minimum supported version?
Well, even the lts kernel in Arch is from the 3.10 series, so I think that should be a reasonable version. But I am merely speculating, falconindy would be able to answer this better.
Also, if a VPS provider lets you load custom kernels, this question becomes pointless.
Last edited by x33a (2014-01-24 17:56:29)
I don't know the exact kernel version that require. But just as an example, the previous linux-lts kernel (3.0.y) began to silently break in strange ways probably almost a year ago. I suspect that our current LTS may be incompatible with Arch userspace by the end of 2014, but this will likely be a more noticeable breakage.
I can't really recommend running anything other than the current kernel in [core].
Last edited by falconindy (2014-01-24 19:05:06)
Thanks for the replies. What I'm getting from this is that since a lot of virtualization environments run on old kernels (OpenVZ is based on RHEL 6 for example) there is no hope for running Arch on a VPS anymore? I'll go and warn people on the wiki page then. I think we can mark this topic as closed.
That's sad, I really enjoyed having Arch on all my servers.
Sure there is, just not on OpenVZ. Get away from a container based setup to one that provides an actual virtual machine and lets you load your own kernel and you'll be fine.
Last edited by Scimmia (2014-01-24 19:44:06)
Sorry about that, I fixed it.
you might want to check out linode.com.
They do list Arch Linux 2013.06 as the current version of arch they support for install, but look at their kernel page here :
Booting with apg Openrc, NOT systemd.
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them
In case anyone else wants to keep using Arch Linux on an OpenVZ VPS (or another container that may be running older kernels), here is the list of packages that you need to keep on old versions:
systemd-204-3 systemd-sysvcompat-204-3 libgcrypt-1.5.3-1 dbus-1.6.18-3 libdbus-1.6.18-3
My main problem was that systemd > 204 did not boot on my VPS and the other packages can't handle such an old version of systemd any more. There may be more recent versions of these that still work and I know this isn't ideal so don't attempt this unless you really want this unstable setup. If anyone has managed to run this setup successfully without having to keep those outdated versions around let me know.
Also I do know that switching to a VM-based provider (instead of container-based) would solve this but I really like my current provider and they only support OpenVZ.
Currently on latest stable OpenVZ kernel 2.6.32-042stab085.20 Arch Linux works fine, only you can't use systemd-212 as it uses kernel features which aren't available in OpenVZ kernel.
So upgrade systemd to latest systemd 211 and then blacklist it with IgnorePkg in /etc/pacman.conf
All other packages can be updated to latest versions.
libsystemd 212-2 systemd 211-1 systemd-sysvcompat 212-2 libgcrypt 1.6.1-1 dbus 1.8.0-1 dbus-glib 0.102-1 libdbus 1.8.0-1
EDIT: BTW I reported this bug to OpenVZ - systemd 212 doesn't work because of missing kernel features
Last edited by davispuh (2014-04-10 16:39:23)
Thanks for the reply! I tried the package versions you recommended but I get the same error I've had since systemd-205. I tried calling systemd manually but I get the following:
# init --log-level=debug systemd 211 running in user mode for user 0/root. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR) Failed to make us a subreaper: Invalid argument Perhaps the kernel version is too old (< 3.4?) Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd. Failed to create root cgroup hierarchy: Invalid argument Failed to allocate manager object: Invalid argument
Do you have any idea how to solve this? My VPS is running the latest RHEL6 OpenVZ kernel.
@davispuh good one reporting the bug, i didnt manage to sit down long enough to isolate the error, CC'd myself to it.
The moment this is fixed, I'm going to make another Arch OpenVZ image for openvz.org, been quite a while since I've seen a need in updating the image, but making one while on the new kernel will give me a chance to ensure there is no other issues with new systemd features.