[BlueOnyx:22344] Re: sysetmctl dbus errors after automatic updates

Wed Aug 22 04:28:10 -05 2018

Hi all

Same problem here...

But instead of PHP-FPM service errors i have Server Desktop and NGINX SSL-PROXY not running anymore...

[root at xxx]# systemctl list-unit-files

Works OK, get a list back with 327 unit files

[root at xxx]# systemctl --user list-unit-files

Failed to get D-Bus connection: Connection refused

[root at xx]# systemctl daemon-reexec

Failed to get D-Bus connection: Too many levels of symbolic links

Also got the same error in ps aux

dbus       823  0.0  0.0  58220  2480 ?        Ss   Aug17   0:18 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

this started at yesterday's updates at 06:00am 21 aug 2018

kind regards

janwillem

From: Blueonyx <blueonyx-bounces at mail.blueonyx.it> on behalf of Jochen Demmer <jdemmer at relaix.net>
Reply-To: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it>
Date: Wednesday, 22. August 2018 at 11:08
To: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it>
Subject: [BlueOnyx:22343] sysetmctl dbus errors after automatic updates

Hi,

running Blue Onyx on CentOS 7.5 in a VM with

base-blueonyx-glue-5209R-5.20180819BX01.el7.noarch

We run automatic updates on the system.  Yesterday morning there were

some packages updated:

Aug 21 03:09:14 Updated: systemd-libs.x86_64 219-57.el7_5.1

Aug 21 03:09:14 Updated: audit-libs.x86_64 2.8.1-3.el7_5.1

Aug 21 03:09:14 Updated: libuuid.x86_64 2.23.2-52.el7_5.1

Aug 21 03:09:14 Updated: libblkid.x86_64 2.23.2-52.el7_5.1

Aug 21 03:09:14 Updated: libmount.x86_64 2.23.2-52.el7_5.1

Aug 21 03:09:15 Updated: systemd.x86_64 219-57.el7_5.1

Aug 21 03:09:15 Updated: systemd-sysv.x86_64 219-57.el7_5.1

Aug 21 03:09:15 Updated: util-linux.x86_64 2.23.2-52.el7_5.1

Aug 21 03:09:15 Updated: selinux-policy.noarch 3.13.1-192.el7_5.6

Aug 21 03:09:15 Updated: kpartx.x86_64 0.4.9-119.el7_5.1

Aug 21 03:09:15 Updated: dracut.x86_64 033-535.el7_5.1

Aug 21 03:09:16 Updated: initscripts.x86_64 9.49.41-1.el7_5.1

Aug 21 03:09:16 Updated: device-mapper-multipath-libs.x86_64

0.4.9-119.el7_5.1

Aug 21 03:09:16 Updated: base-system-locale-es_ES.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-locale-da_DK.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-locale-en_US.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-ui.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-locale-fr_FR.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-locale-it_IT.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: mariadb-libs.x86_64 1:5.5.60-1.el7_5

Aug 21 03:09:16 Updated: base-system-locale-de_DE.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-blueonyx-glue.noarch 5209R-5.20180819BX01.el7

Aug 21 03:09:16 Updated: base-system-glue.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: jss.x86_64 4.4.0-13.el7_5

Aug 21 03:09:16 Updated: base-system-locale-nl_NL.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-locale-ja_JP.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-locale-pt_PT.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: base-system-capstone.noarch 1.2.0-0BX18.el7

Aug 21 03:09:16 Updated: tomcatjss.noarch 7.2.1-7.el7_5

Aug 21 03:09:16 Updated: base-blueonyx-capstone.noarch

5209R-5.20180819BX01.el7

Aug 21 03:09:17 Updated: mariadb.x86_64 1:5.5.60-1.el7_5

Aug 21 03:09:17 Updated: device-mapper-multipath.x86_64 0.4.9-119.el7_5.1

Aug 21 03:09:17 Updated: dracut-network.x86_64 033-535.el7_5.1

Aug 21 03:09:18 Updated: dracut-config-rescue.x86_64 033-535.el7_5.1

Aug 21 03:09:24 Updated: selinux-policy-targeted.noarch 3.13.1-192.el7_5.6

Aug 21 03:09:24 Updated: audit.x86_64 2.8.1-3.el7_5.1

Aug 21 03:09:24 Updated: libgudev1.x86_64 219-57.el7_5.1

Aug 21 03:09:24 Updated: audit-libs.i686 2.8.1-3.el7_5.1

Aug 21 03:09:24 Updated: systemd-libs.i686 219-57.el7_5.1

See what happens in the log:

Aug 21 03:09:14 our.host.name dbus[14093]: [system] Reloaded configuration

Aug 21 03:09:14 our.host.name dbus[14093]: [system] Reloaded configuration

Aug 21 03:09:14 our.host.name dbus[14093]: [system] Reloaded configuration

Aug 21 03:09:14 our.host.name dbus[14093]: [system] Reloaded configuration

Aug 21 03:09:14 our.host.name dbus[14093]: [system] Reloaded configuration

Aug 21 06:00:36 our.host.name dbus[14093]: [system] Reloaded configuration

We then received an email about some thing behaving strangely at 03:15h

the same day.

Active Monitor has detected recent changes in the state of your server appliance.

For more details, please see the Active Monitor section of the Server Desktop.

Summary of changes:

* The service PHP-FPM is not running and could not be restarted. Please check the logfiles for error messages related to this service and run 'systemctl status php-fpm.service' as root from the command line to troubleshoot the problem. If you are still unable to access the PHP-FPM, please visit http://BlueOnyx.it/ for technical support.

- The service PHP-FPM is not running and could not be restarted. Please check the logfiles for error messages related to this service and run 'systemctl status php-fpm.service' as root from the command line to troubleshoot the problem. If you are still unable to access the PHP-FPM, please visit http://BlueOnyx.it/ for technical support.

- The service PHP-FPM 5.6 is not running and could not be restarted. Please check the logfiles for error messages related to this service and run 'systemctl status php-fpm-5.6.service' as root from the command line to troubleshoot the problem. If you are still unable to access the PHP-FPM 5.6, please visit http://BlueOnyx.it/ for technical support.

* The SSHd server is not running and could not be restarted. In the Server Desktop, try turning the SSHd server off then on again to see if this corrects the problem. If the SSHd server is still unable to start, try rebooting the server itself by clicking the Reboot Now button in the Power menu under System Settings. If the SSHd server is still unable to start, please refer http://BlueOnyx.it/ for technical support.

Now I cannot use systemctl any more:

[root at our log]# systemctl list-unit-files

Failed to get D-Bus connection: Too many levels of symbolic links

[root at our log]# systemctl --user list-unit-files

Failed to get D-Bus connection: Connection refused

[root at our log]# systemctl daemon-reexec

Failed to get D-Bus connection: Too many levels of symbolic links

ps aux showing me this process:

dbus     14093  0.0  0.0  58080   412 ?        Ss   Jul09   0:00

/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile

--systemd-activation

Any idea what happened here? I would restart the server in order to

bring things back online but maybe I can circumvent that...

Thank you

-- 

Jochen Demmer

System- und Netzwerkspezialist

RelAix Networks GmbH

Kackertstraße 10

52072 Aachen

Tel.:      0241 / 990001-206

Fax:       0241 / 990001-149

E-Mail:    jdemmer at relaix.net

Internet:  http://www.relaix.net/

Geschäftsführer: Thomas Neugebauer

Amtsgericht Aachen, HRB 15108

_______________________________________________

Blueonyx mailing list

Blueonyx at mail.blueonyx.it

http://mail.blueonyx.it/mailman/listinfo/blueonyx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20180822/acff5cb7/attachment.html>