reklama

CentOS 7 se nerestartoval po updatu systému

samalama

CentOS 7 se nerestartoval po updatu systému
« kdy: 26. 10. 2018, 13:22:39 »
centos 7 - niekolko tyzdnova cista instalacia (naviac len epel a bareos repozitar), po upgrade systemu sa server nerestartol.

Kód: [Vybrat]
# uname -a
Linux server 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
# yum update
...
...
...
# reboot

Broadcast message from root@server on pts/0 (Fri 2018-10-26 12:56:39 CEST):

The system is going down for reboot NOW!
                                                                       
# uptime
 13:02:16 up 30 days, 16:52,  1 user,  load average: 0.00, 0.05, 0.06


relevantne logy:

Kód: [Vybrat]
Oct 26 12:55:45 server yum[12523]: Updated: centos-release-7-5.1804.5.el7.centos.x86_64
Oct 26 12:55:45 server yum[12523]: Updated: nss-sysinit-3.36.0-7.el7_5.x86_64
Oct 26 12:55:46 server yum[12523]: Updated: nss-3.36.0-7.el7_5.x86_64
Oct 26 12:55:46 server yum[12523]: Updated: systemd-libs-219-57.el7_5.3.x86_64
Oct 26 12:55:47 server systemd: Closed udev Control Socket.
Oct 26 12:55:47 server systemd: Stopping udev Control Socket.
Oct 26 12:55:47 server systemd: Closed udev Kernel Socket.
Oct 26 12:55:47 server systemd: Stopping udev Kernel Socket.
Oct 26 12:55:47 server systemd: Stopping udev Kernel Device Manager...
Oct 26 12:55:47 server systemd: Stopped udev Kernel Device Manager.
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:47 server dbus[431]: [system] Reloaded configuration
Oct 26 12:55:48 server systemd: Reexecuting.
Oct 26 12:55:48 server systemd: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Oct 26 12:55:48 server systemd: Detected virtualization kvm.
Oct 26 12:55:48 server systemd: Detected architecture x86-64.
Oct 26 12:55:49 server systemd: Failed to connect to system bus: No such file or directory
Oct 26 12:55:49 server systemd: Failed to initialize D-Bus connection: No such file or directory
Oct 26 12:55:49 server systemd: Failed to connect to system bus: No such file or directory
Oct 26 12:55:49 server systemd: Failed to initialize D-Bus connection: No such file or directory
Oct 26 12:55:49 server yum[12523]: Updated: systemd-219-57.el7_5.3.x86_64
Oct 26 12:55:50 server yum[12523]: Updated: initscripts-9.49.41-1.el7_5.2.x86_64
Oct 26 12:55:56 server yum[12523]: Installed: kernel-3.10.0-862.14.4.el7.x86_64
Oct 26 12:55:57 server yum[12523]: Updated: systemd-sysv-219-57.el7_5.3.x86_64
Oct 26 12:55:57 server yum[12523]: Updated: nss-tools-3.36.0-7.el7_5.x86_64
Oct 26 12:55:58 server yum[12523]: Updated: kernel-headers-3.10.0-862.14.4.el7.x86_64
Oct 26 12:55:59 server yum[12523]: Updated: ghostscript-9.07-29.el7_5.2.x86_64
Oct 26 12:55:59 server yum[12523]: Updated: python2-acme-0.27.1-1.el7.noarch
Oct 26 12:56:08 server dracut[12702]: Executing: /sbin/dracut -f /boot/initramfs-3.10.0-862.14.4.el7.x86_64.img 3.10.0-862.14.4.el7.x86_64
...
Oct 26 12:56:18 server rsyslogd: imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
Oct 26 12:56:19 server dracut[12702]: *** Creating initramfs image file '/boot/initramfs-3.10.0-862.14.4.el7.x86_64.img' done ***
Oct 26 12:56:39 server systemd: Started /dev/initctl Compatibility Daemon.
Oct 26 12:56:39 server systemd: Starting /dev/initctl Compatibility Daemon...
Oct 26 12:56:39 server systemd-initctl: Failed to get D-Bus connection: No such file or directory
Oct 26 12:56:39 server systemd: systemd-initctl.service: main process exited, code=exited, status=1/FAILURE
Oct 26 12:56:39 server systemd: Unit systemd-initctl.service entered failed state.
Oct 26 12:56:39 server systemd: systemd-initctl.service failed.
Oct 26 12:56:39 server systemd: Started /dev/initctl Compatibility Daemon.
Oct 26 12:56:39 server systemd: Starting /dev/initctl Compatibility Daemon...
Oct 26 12:56:39 server systemd-initctl: Failed to get D-Bus connection: No such file or directory
Oct 26 12:56:39 server systemd: systemd-initctl.service: main process exited, code=exited, status=1/FAILURE
Oct 26 12:56:39 server systemd: Unit systemd-initctl.service entered failed state.
Oct 26 12:56:39 server systemd: systemd-initctl.service failed.
Oct 26 12:56:39 server systemd: Started /dev/initctl Compatibility Daemon.
Oct 26 12:56:39 server systemd: Starting /dev/initctl Compatibility Daemon...
Oct 26 12:56:39 server systemd-initctl: Failed to get D-Bus connection: No such file or directory
Oct 26 12:56:39 server systemd: systemd-initctl.service: main process exited, code=exited, status=1/FAILURE
Oct 26 12:56:39 server systemd: Unit systemd-initctl.service entered failed state.
Oct 26 12:56:39 server systemd: systemd-initctl.service failed.
Oct 26 12:56:39 server systemd: Started /dev/initctl Compatibility Daemon.
Oct 26 12:56:39 server systemd: Starting /dev/initctl Compatibility Daemon...
Oct 26 12:56:39 server systemd-initctl: Failed to get D-Bus connection: No such file or directory
Oct 26 12:56:39 server systemd: systemd-initctl.service: main process exited, code=exited, status=1/FAILURE
Oct 26 12:56:39 server systemd: Unit systemd-initctl.service entered failed state.
Oct 26 12:56:39 server systemd: systemd-initctl.service failed.
Oct 26 12:56:39 server systemd: Started /dev/initctl Compatibility Daemon.
Oct 26 12:56:39 server systemd: Starting /dev/initctl Compatibility Daemon...
Oct 26 12:56:39 server systemd-initctl: Failed to get D-Bus connection: No such file or directory
Oct 26 12:56:39 server systemd: systemd-initctl.service: main process exited, code=exited, status=1/FAILURE
Oct 26 12:56:39 server systemd: Unit systemd-initctl.service entered failed state.
Oct 26 12:56:39 server systemd: systemd-initctl.service failed.
Oct 26 12:56:39 server systemd: start request repeated too quickly for systemd-initctl.service
Oct 26 12:56:39 server systemd: Failed to start /dev/initctl Compatibility Daemon.
Oct 26 12:56:39 server systemd: Unit systemd-initctl.socket entered failed state.
Oct 26 12:56:39 server systemd: systemd-initctl.service failed.
...
Oct 26 13:01:01 server crond[19864]: pam_systemd(crond:session): Failed to connect to system bus: No such file or directory
...
Oct 26 13:10:01 server crond[20008]: pam_systemd(crond:session): Failed to connect to system bus: No such file or directory


server bezi doteraz.

co som urobil zle (okrem toho, ze som tam nutene musel nainstalovat systemd)?
« Poslední změna: 26. 10. 2018, 13:41:45 od Petr Krčmář »

reklama


samalama

skusil som este raz reboot:

# reboot
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

McGyver

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #2 kdy: 26. 10. 2018, 13:46:46 »
Cetl jsi ty logy, kdyz nam je ukazujes? Nejede ti dbus, neco sis tam pri tom update polamal. Vic mi kristalova koule nerika.

samalama

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #3 kdy: 26. 10. 2018, 13:57:48 »
neco sis tam pri tom update polamal

ja? co som akoze mal polamat pri yum update?

McGyver

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #4 kdy: 26. 10. 2018, 14:17:20 »
Cokoliv, bez logu to nepozname. Nevime, v jakem stavu ten system je. CentOS bezi na milionech serveru na svete, tohle neni normalni chovani v normalnim systemu. Mas tam neco shnileho, neprecetl sis logy zobrazene pri upgrade a ted brecis a chces pomoct. Oprav si dbus.


samalama

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #5 kdy: 26. 10. 2018, 14:31:34 »
akoze ja mam opravovat rozbity systemd?!

este raz: cista instalacia systemu, server lezal uhorom niekolko tyzdnov a dnes urobeny update. takze system sa sam od seba rozbil. chapes? a tak sa pytam, ako je to mozne?

jedina zmienka o dbus v logoch je len z predchadzajuce updatu:

Sep 25 19:46:52 server dbus[428]: [system] Reloaded configuration                                           
Sep 25 19:46:52 server dbus[428]: [system] Reloaded configuration
Sep 25 20:09:23 server systemd: Listening on D-Bus System Message Bus Socket.
Sep 25 20:09:23 server systemd: Starting D-Bus System Message Bus Socket.   
Sep 25 20:09:23 server systemd: Started D-Bus System Message Bus.       
Sep 25 20:09:23 server systemd: Failed to initialize D-Bus connection: No such file or directory
Sep 25 20:09:23 server systemd: Starting D-Bus System Message Bus...

kkt1

  • *****
  • 796
    • Zobrazit profil
Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #6 kdy: 26. 10. 2018, 14:41:05 »
ja mel za to, ze to je hlavni funkce systemd... ;)

McGyver

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #7 kdy: 26. 10. 2018, 15:53:25 »
Ty to nechces resit, jen sis prisel zanadavat. Kdybys to resit chtel, tak zacnes debugovat, proc ti ten dbus nestartuje. Se systemd to nijak nesouvisi, kdyz ti nejede dbus, tak se demony nedomluvi. Oprav si to.

samalama

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #8 kdy: 26. 10. 2018, 16:08:15 »
# uptime
 16:00:13 up 0 min,  1 user,  load average: 0.00, 0.00, 0.00

# systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Fri 2018-10-26 15:59:56 CEST; 48s ago
     Docs: man:dbus-daemon(1)
 Main PID: 294 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─294 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Oct 26 15:59:56 server systemd[1]: Started D-Bus System Message Bus.
Oct 26 15:59:56 server systemd[1]: Starting D-Bus System Message Bus...

# systemctl status dbus.socket
● dbus.socket - D-Bus System Message Bus Socket
   Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static; vendor preset: disabled)
   Active: active (running) since Fri 2018-10-26 15:59:56 CEST; 52s ago
   Listen: /run/dbus/system_bus_socket (Stream)

Oct 26 15:59:56 server systemd[1]: Listening on D-Bus System Message Bus Socket.
Oct 26 15:59:56 server systemd[1]: Starting D-Bus System Message Bus Socket.



# journalctl
...
Oct 26 15:59:56 server systemd[1]: Started D-Bus System Message Bus.
Oct 26 15:59:56 server systemd[1]: Failed to connect to system bus: No such file or directory
Oct 26 15:59:56 server systemd[1]: Failed to initialize D-Bus connection: No such file or directory
Oct 26 15:59:56 server systemd[1]: Starting D-Bus System Message Bus...

Oct 26 15:59:56 server systemd[1]: Starting Resets System Activity Logs...
Oct 26 15:59:56 server systemd[1]: Starting Run automatic yum updates as a cron job...
Oct 26 15:59:56 server systemd[1]: Starting LSB: Bring up/down networking...
Oct 26 15:59:56 server systemd[1]: Starting Network Time Service...
Oct 26 15:59:56 server systemd[1]: Starting Login Service...
Oct 26 15:59:56 server systemd[1]: Starting Permit User Sessions...
Oct 26 15:59:56 server systemd[1]: Starting ACPI Event Daemon...
Oct 26 15:59:56 server systemd[1]: Starting Dump dmesg to /var/log/dmesg...
Oct 26 15:59:56 server systemd-logind[301]: Failed to connect to system bus: No such file or directory
Oct 26 15:59:56 server ntpd[300]: ntpd 4.2.6p5@1.2349-o Fri Apr 13 12:52:27 UTC 2018 (1)
Oct 26 15:59:56 server systemd-logind[301]: Failed to fully start up daemon: No such file or directory
Oct 26 15:59:56 server systemd[1]: Started Run automatic yum updates as a cron job.
Oct 26 15:59:56 server ntpd[314]: proto: precision = 0.030 usec
Oct 26 15:59:56 server ntpd[314]: 0.0.0.0 c01d 0d kern kernel time sync enabled
Oct 26 15:59:56 server systemd[1]: Started Resets System Activity Logs.
Oct 26 15:59:56 server systemd[1]: Started Network Time Service.
Oct 26 15:59:56 server systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Oct 26 15:59:56 server ntpd[314]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 26 15:59:56 server ntpd[314]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 26 15:59:56 server ntpd[314]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 26 15:59:56 server ntpd[314]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 26 15:59:56 server ntpd[314]: Listen normally on 3 lo ::1 UDP 123
Oct 26 15:59:56 server ntpd[314]: Listening on routing socket on fd #20 for interface updates
Oct 26 15:59:56 server systemd[1]: Failed to start Login Service.
...



# su -
Oct 26 16:07:17 server su[861]: (to root) root on pts/0
Oct 26 16:07:17 server su[861]: pam_systemd(su-l:session): Failed to connect to system bus: No such file or directory
Oct 26 16:07:17 server su[861]: pam_unix(su-l:session): session opened for user root by root(uid=0)

Jenda

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #9 kdy: 26. 10. 2018, 16:17:04 »
echo b > /proc/sysrq-trigger

Lol Phirae

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #10 kdy: 26. 10. 2018, 18:22:44 »
Nevime, v jakem stavu ten system je.

To naopak víme naprosto přesně - systém je v  (_!_)

samalama

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #11 kdy: 26. 10. 2018, 20:02:44 »
echo b > /proc/sysrq-trigger

server sa restartol, ked som mu cez virt-manager poslal ctrl+alt+del, ale po reboote je stale poblem s d-bus, ktory podla niektorych sluzieb vraj nebezi, ale inac bezi, vid hore.

skusil som systemd.log_level=debug, ale nic mudreho to nevypisalo.

Fuki

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #12 kdy: 26. 10. 2018, 20:33:40 »
Ak mas pristup k masine tak ovela rychlejsie bude nova cista instalacia nez cely vikend lovit co sa pri update posralo.

samalama

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #13 kdy: 26. 10. 2018, 21:32:29 »
Ak mas pristup k masine tak ovela rychlejsie bude nova cista instalacia nez cely vikend lovit co sa pri update posralo.

cez virt-manager poslal ctrl+alt+del

je to kvm vm. a reinstalacia nie je risenie. tych instalacii som uz robil desiatky, taky problem sa este nevyskytol, takze ma to zaujma aj z toho pohladu, ci to teraz nezacne vyskakovat. a po druhe, realne chcem vediet, kde je problem (aj ked to robim nerad, pretoze systemd...)

okl

Re:CentOS 7 se nerestartoval po updatu systému
« Odpověď #14 kdy: 26. 10. 2018, 22:22:36 »
cau

mozes dat este vypis

#systemctl status systemd-logind


a pozri este ci je /var/run symlinknuty do /run

 

reklama