Arch Linux

Mister_Magotchi

Member

Registered: 2012-06-08

Posts: 13

[SOLVED] Problems After systemd Upgrade on OpenVZ x64

Today I did a full system upgrade inside of an OpenVZ container, and upon rebooting, the network interface wasn't up.

In OpenVZ's "serial" console, when I attempted to do anything with systemctl (like systemctl restart network), I got:
"Failed to get D-Bus connection: No such file or directory"

To fix it, I downgraded from systemd-212-1-x86_64 to systemd-211-1-x86_64 (and from systemd-sysvcompat-212-1-x86_64 to systemd-sysvcompat-211-1-x86_64 since I didn't know if I needed to or not).

Should I just wait for a newer systemd package and hope it starts working again at a later time, or is there something I can do to make my system work with the current systemd package?

Thanks

Last edited by Mister_Magotchi (2014-11-20 23:03:16)

Roukoswarf

Member

From: Ontario, Canada

Registered: 2012-10-04

Posts: 8

Website

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

I also am having this issue, you are likely using my openvz arch image.

I will try to figure out whats going on with the systemd people.

Mister_Magotchi

Member

Registered: 2012-06-08

Posts: 13

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

I didn't use your template.  I always build my own with mkarchroot.  Here's the script I use lately, and it's based on the one on the OpenVZ wiki.  Then I just rsync it over the top of a live system if a provider won't add the template for me or if it's too much hassle.

Regarding systemd, according to the warning at the top of the Arch wiki VPS page, systemd hasn't supported OpenVZ's current kernel since version 205.  Hopefully it's still possible to get it working somehow.

Additionally, it's currently only necessary to keep systemd at version 211.  It's working fine for me to keep systemd-sysvcompat at 212 (although this may create some yet-unknown compatibility issues).

Last edited by Mister_Magotchi (2014-04-03 05:05:47)

Roukoswarf

Member

From: Ontario, Canada

Registered: 2012-10-04

Posts: 8

Website

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

http://goo.gl/a2vama
"Require kernel 3.7 temporarily due to unconditional use of newer defines."
A commit notice from gentoo's ebuild for systemd may shed some light. not sure if its talking about systemd or the ebuild in particular, but I have a feeling it's systemd.
As I said, I am going to talk to some systemd people and see whats going on, as I don't really know the actual commits myself.

Last edited by Roukoswarf (2014-04-03 05:16:27)

cgm999

Member

Registered: 2013-07-18

Posts: 19

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

Any news about this? For now I've blocked systemd from updating in my openvz archlinux VPS

Roukoswarf

Member

From: Ontario, Canada

Registered: 2012-10-04

Posts: 8

Website

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

https://bugzilla.openvz.org/show_bug.cgi?id=2937

Reported, source found, and assigned.

Hope for a backport of the feature or some other workaround, CC yourself, show interest, etc.
When the issue is fixed and the kernel is updated, yell at your provider incessantly to update.

Mister_Magotchi

Member

Registered: 2012-06-08

Posts: 13

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

OpenVZ fixed this on 2014-11-06 in 042stab094.7, their latest stable kernel.

From the changelog:
"ms/hrtimer: Backport CLOCK_BOOTTIME feature, needed for latest systemd (#2937)"

Last edited by Mister_Magotchi (2014-11-20 23:00:35)

autonymous

Member

Registered: 2008-02-24

Posts: 31

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

Fixed (again) with the latest stable openvz kernel release:  https://openvz.org/Download/kernel/rhel6/042stab111.11

Bug - systemd 220+ doesn't work anymore under OpenVZ container (fixed) - https://bugs.openvz.org/browse/OVZ-6384#c11.

I just rolled one myself and confirmed it's fixed.

cgm999

Member

Registered: 2013-07-18

Posts: 19

Re: [SOLVED] Problems After systemd Upgrade on OpenVZ x64

I switched to use runit-musl(which are small static binaries) for my archlinux vps. So I do not need to worry about this anymore..

cgm@archlinux $ pstree -u

runit-+-kthreadd/102222---khelper/102222
      |-runsvdir-+-runsv---crond
      |          |-runsv---syslog-ng
      |          |-runsv---exim(exim)
      |          |-runsv---xinetd---sshd---sshd(build)---screen
      |          `-runsv---lighttpd(http)
      `-screen---bash(build)---pstree

cgm@archlinux $ ps axuOr|head -20
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         2  0.0  0.0      0     0 ?        S    Sep12   0:00 [kthreadd/102222]
root         3  0.0  0.0      0     0 ?        S    Sep12   0:00 [khelper/102222]
root         1  0.0  0.0    116    20 ?        Ss   Sep12   0:04 runit
root        78  0.0  0.0    124    36 ?        Ss   Sep12   0:00 runsv crond
root        79  0.0  0.0    124    36 ?        Ss   Sep12   0:00 runsv syslog-ng
root        80  0.0  0.0    124    40 ?        Ss   Sep12   0:00 runsv exim
root        81  0.0  0.0    124    40 ?        Ss   Sep12   0:00 runsv xinetd
root        82  0.0  0.0    124    40 ?        Ss   Sep12   0:00 runsv lighttpd
root        77  0.0  0.0    156    52 ?        Ss   Sep12   0:05 runsvdir -P /etc/sv-cgm log: ........syslog-ng .........................................................................................................................................................................................................................................................................................................................................................................................