OpenVZ Forum: Support » No systemctl after update centos 7

Home » General » Support » No systemctl after update centos 7 (

) 1 Vote

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

No systemctl after update centos 7 [message #52282]

Wed, 16 December 2015 20:32

ku990
Messages: 3
Registered: December 2015
Location: aici

Junior Member

i have cron with " yum update -y " every day at 00:00 .
this is ok for few monts but today a have a big problem .

PROBLEM:
[root@host /]# systemctl status
Failed to get D-Bus connection: No such file or directory

============

Report message to a moderator

Re: No systemctl after update centos 7 [message #52284 is a reply to message #52282]

Mon, 21 December 2015 18:38

ku990
Messages: 3
Registered: December 2015
Location: aici

Junior Member

Report message to a moderator

Re: No systemctl after update centos 7 [message #52285 is a reply to message #52282]

Fri, 25 December 2015 19:20

zvv2
Messages: 4
Registered: January 2010

Junior Member

Try to update kernel.
Problem fixed in 042stab094.7
h ttps://wiki.openvz.org/Download/kernel/rhel6/042stab094.7
ms/hrtimer: Backport CLOCK_BOOTTIME feature, needed for latest systemd (#2937)

My tests:

[root@111 /]# uname -srv
Linux 2.6.32-042stab111.12 #1 SMP Thu Sep 17 11:38:20 MSK 2015

[root@111 /]# cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)

[root@111 /]# yum -y update

[root@111 /]# cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)

and after restart ve:

[root@111 /]# ps axufww
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0  41120  3580 ?        Ss   14:10   0:00 init -z
root         2  0.0  0.0      0     0 ?        S    14:10   0:00 [kthreadd/111]
root         3  0.0  0.0      0     0 ?        S    14:10   0:00  \_ [khelper/111]
root        66  0.0  0.0  34776  1672 ?        Ss   14:10   0:00 /usr/lib/systemd/systemd-udevd
root        70  0.0  0.0  36764  3044 ?        Ss   14:10   0:00 /usr/lib/systemd/systemd-journald
root       105  0.0  0.0  24224  1536 ?        Ss   14:10   0:00 /usr/lib/systemd/systemd-logind
root       108  0.0  0.1 226084  5060 ?        Ss   14:10   0:00 /usr/sbin/httpd -DFOREGROUND
apache     144  0.0  0.0 226084  2656 ?        S    14:10   0:00  \_ /usr/sbin/httpd -DFOREGROUND
root       112  0.0  0.0  82500  3596 ?        Ss   14:10   0:00 /usr/sbin/sshd -D
dbus       115  0.0  0.0  26412  1612 ?        Ss   14:10   0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root       117  0.0  0.0  27272   704 ?        Ss   14:10   0:00 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid
root       119  0.0  0.0  71276   984 ?        Ss   14:10   0:00 /usr/sbin/saslauthd -m /run/saslauthd -a pam -n 2
root       127  0.0  0.0  71276   716 ?        S    14:10   0:00  \_ /usr/sbin/saslauthd -m /run/saslauthd -a pam -n 2
root       120  0.0  0.0 234040  2948 ?        Ssl  14:10   0:00 /usr/sbin/rsyslogd -n
root       145  0.0  0.0   6404   816 tty1     Ss+  14:10   0:00 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 vt220
root       146  0.0  0.0  22748  1524 ?        Ss   14:10   0:00 /usr/sbin/crond -n
root       147  0.0  0.0   6404   812 tty2     Ss+  14:10   0:00 /sbin/agetty --noclear tty2 linux
root       172  0.0  0.0  90276  2288 ?        Ss   14:10   0:00 sendmail: accepting connections
smmsp      218  0.0  0.0  85712  1996 ?        Ss   14:10   0:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
root       381  0.0  0.0  27560   756 ?        Ss   14:10   0:00 vzctl: pts/0
root       382  0.0  0.0  11724  1868 pts/0    Ss   14:10   0:00  \_ -bash
root       427  0.0  0.0  35836  1452 pts/0    R+   14:15   0:00      \_ ps axufww

[Updated on: Fri, 25 December 2015 19:23]

Report message to a moderator

Re: No systemctl after update centos 7 [message #52286 is a reply to message #52285]

Fri, 25 December 2015 21:06

ku990
Messages: 3
Registered: December 2015
Location: aici

Junior Member

[root@ct reparare]# systemctl
Failed to get D-Bus connection: No such file or directory
[root@ct reparare]# rpm -i vzkernel-2.6.32-042stab103.5.src.rpm
warning: vzkernel-2.6.32-042stab103.5.src.rpm: Header V4 DSA/SHA1 Signature, key ID a7a1d4b6: NOKEY
[root@ct reparare]# reboot -f
got signal 9
exited from CT 100
root@Dedicat:/hdd/private/100/reparare# vzctl enter 100
entered into CT 100
[root@ct /]# uname -r
2.6.32-32-pve
[root@ct /]# systemctl start network
Failed to get D-Bus connection: No such file or directory
[root@ct /]#

042stab094.7 - can`t download ( 404 not found )

please help me ..

[Updated on: Fri, 25 December 2015 21:07]

Report message to a moderator

Re: No systemctl after update centos 7 [message #52297 is a reply to message #52282]

Fri, 15 January 2016 22:34

reallife
Messages: 7
Registered: February 2014

Junior Member

not relating to systemctl, but you should yum install yum-cron instead of manual cron
it has a nice update config, also emails you with results

Report message to a moderator

Re: No systemctl after update centos 7 [message #52333 is a reply to message #52282]

Fri, 26 February 2016 20:28

puravida
Messages: 6
Registered: September 2015
Location: USA

Junior Member

I am having this exact same issue. I just downloaded the latest (02/19/2016) available CentOS 7 64-bit (minimal) template from the OVZ templates directory and created a new VM from it. Nothing special from what I can tell.

I immediately get the error:

# systemctl
Failed to get D-Bus connection: No such file or directory

The image is built on the following:
Linux 2.6.32-042stab081.3 #1 SMP Mon Sep 9 20:07:47 MSK 2013
CentOS Linux release 7.2.1511 (Core)

I am running OpenNode 6.

I am surprised that this happens right "out of the box" on this template. The template I was using before did not have this issue, but it no longer contains packages that worked and updating to the new systemd on that image absolutely breaks the whole system. I am stuck since using the latest template also seems problematic.

Please help.

Thanks,

Brandon

Report message to a moderator

Re: No systemctl after update centos 7 [message #52334 is a reply to message #52282]

Fri, 26 February 2016 20:43

puravida
Messages: 6
Registered: September 2015
Location: USA

Junior Member

For posterity and others having the same issue, I am updating with research.

I found a thread (in French) in the softpedia forum on this issue. I cannot post the link because I have too few posts in this forum.

It suggests that my OpenNode kernel is too far out-of-date to support the systemd(219) running CentOS 7.2. Hopefully an update will correct that. Will report back.

[Updated on: Fri, 26 February 2016 20:43]

Report message to a moderator

Re: No systemctl after update centos 7 [message #52335 is a reply to message #52334]

Fri, 26 February 2016 21:02

puravida
Messages: 6
Registered: September 2015
Location: USA

Junior Member

Update: Unfortunately, the update didn't work, as I feared, since I'm still on OpenNode 6 (meaning CentOS 6) and the kernel updated but is still 2.6xx (apparently not good enough for systemd 219+). There still does not appear to be an OpenNode 7, so that's a bit frustrating.

I am so tired of spending months building a system, only to find just a couple of years later that it is broken due to changes and there is no upgrade path. I have spent my life basically re-building everything from scratch every few years, because things change so drastically (even though they worked fine before). If something works, they should continue to support it! /rant

Report message to a moderator

Re: No systemctl after update centos 7 [message #52336 is a reply to message #52335]

Fri, 26 February 2016 21:22

puravida
Messages: 6
Registered: September 2015
Location: USA

Junior Member

I just noticed that my updated OpenNode 6 kernel is the same as my CentOS 7-minimal kernel. Strange.

I tried restarting the VM to be sure it was using the latest vzkernel, but that did not help.

Any ideas would be greatly appreciated. At this point, it seems I may be forced to downgrade to CentOS 6 VMs... a step backwards. Such a pity. I just hope that at least that works.

Report message to a moderator

Re: No systemctl after update centos 7 [message #52337 is a reply to message #52282]

Fri, 26 February 2016 21:32

puravida
Messages: 6
Registered: September 2015
Location: USA

Junior Member

Ok, I think I understand the kernel version issue now.

So, my OpenNode 6 kernel is v2.6xx, which means my VZ kernel (even though CentOS 7) is limited to that kernel version.

My other CentOS 7 dedicated servers are running on the v3xx kernel.

So, OpenNode 6 simply cannot support anything that requires the v3xx kernel.

Report message to a moderator

Re: No systemctl after update centos 7 [message #52573 is a reply to message #52282]

Thu, 22 September 2016 10:16

Abadon
Messages: 4
Registered: August 2013
Location: Cyber Space

Junior Member

I had the same problem with CentOS 7 container and OpenVZ node with CentOS6 kernel 2.6.32-042stab108.6

The update to the latest stable OpenVZ kernel (currently 2.6.32-042stab117.14) resolved the issue.

[root@devovz01 ~]# vzctl enter 106
entered into CT 106
[root@host /]# yum update -y
Loaded plugins: fastestmirror
base                                                                                                                                                      | 3.6 kB  00:00:00     
extras                                                                                                                                                    | 3.4 kB  00:00:00     
updates                                                                                                                                                   | 3.4 kB  00:00:00     
(1/4): extras/7/x86_64/primary_db                                                                                                                         | 165 kB  00:00:00     
(2/4): base/7/x86_64/group_gz                                                                                                                             | 155 kB  00:00:00     
(3/4): updates/7/x86_64/primary_db                                                                                                                        | 7.8 MB  00:00:05     
(4/4): base/7/x86_64/primary_db                                                                                                                           | 5.3 MB  00:00:06     
Determining fastest mirrors
 * base: mirrors.coreix.net
 * extras: centos.serverspace.co.uk
 * updates: centos.serverspace.co.uk
Resolving Dependencies
--> Running transaction check
---> Package bash.x86_64 0:4.2.46-19.el7 will be updated
---> Package bash.x86_64 0:4.2.46-20.el7_2 will be an update
---> Package dbus.x86_64 1:1.6.12-13.el7 will be updated
---> Package dbus.x86_64 1:1.6.12-14.el7_2 will be an update
---> Package dbus-libs.x86_64 1:1.6.12-13.el7 will be updated
.............................................................
Updated:
  bash.x86_64 0:4.2.46-20.el7_2                 dbus.x86_64 1:1.6.12-14.el7_2                dbus-libs.x86_64 1:1.6.12-14.el7_2      glibc.x86_64 0:2.17-106.el7_2.8             
  glibc-common.x86_64 0:2.17-106.el7_2.8        initscripts.x86_64 0:9.49.30-1.el7_2.3       kmod.x86_64 0:20-8.el7_2                kmod-libs.x86_64 0:20-8.el7_2               
  kpartx.x86_64 0:0.4.9-85.el7_2.6              libarchive.x86_64 0:3.1.2-10.el7_2           libblkid.x86_64 0:2.23.2-26.el7_2.3     libmount.x86_64 0:2.23.2-26.el7_2.3         
  libsmbclient.x86_64 0:4.2.10-7.el7_2          libuuid.x86_64 0:2.23.2-26.el7_2.3           libwbclient.x86_64 0:4.2.10-7.el7_2     mariadb-libs.x86_64 1:5.5.50-1.el7_2        
  nscd.x86_64 0:2.17-106.el7_2.8                python.x86_64 0:2.7.5-39.el7_2               python-libs.x86_64 0:2.7.5-39.el7_2     samba.x86_64 0:4.2.10-7.el7_2               
  samba-client.x86_64 0:4.2.10-7.el7_2          samba-client-libs.x86_64 0:4.2.10-7.el7_2    samba-common.noarch 0:4.2.10-7.el7_2    samba-common-libs.x86_64 0:4.2.10-7.el7_2   
  samba-common-tools.x86_64 0:4.2.10-7.el7_2    samba-libs.x86_64 0:4.2.10-7.el7_2           systemd.x86_64 0:219-19.el7_2.13        systemd-libs.x86_64 0:219-19.el7_2.13       
  systemd-sysv.x86_64 0:219-19.el7_2.13         util-linux.x86_64 0:2.23.2-26.el7_2.3       

Complete!

systemctl status works without D-bus errors.

Report message to a moderator

Previous Topic:	OpenVZ and ZFS support
Next Topic:	OVZ 7 at CentOS 7?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Nov 04 10:49:24 GMT 2025

Total time taken to generate the page: 0.13215 seconds