systemd: Failed to send signal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
systemd: Failed to send signal.
[ 3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer
[ 3.138119] systemd[1]: run-rpc_
[ 3.138185] systemd[1]: dev-mapper-
[ 3.138512] systemd[1]: run-rpc_
[ 3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected
[ 3.142958] systemd[1]: auth-rpcgss-
[ 3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected
[ 3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected
[ 3.165541] systemd[1]: dev-mapper-
[ 3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected
[ 3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected
[ 3.167130] systemd[1]: systemd-
[ 2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected
[ 2.929220] systemd[1]: systemd-
[ 3.024320] systemd[1]: sys-devices-
[ 3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected
[ 3.547019] systemd[1]: proc-sys-
[ 3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected
How to reproduce:
1. enable debug level journal
LogLevel=debug in /etc/systemd/
2. reboot the system
3. journalctl | grep "Failed to send"
sliu@vmlxhi-094:~$ lsb_release -rd
Description: Ubuntu 16.04.4 LTS
Release: 16.04
sliu@vmlxhi-094:~$ systemctl --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
sliu@vmlxhi-094:~$ dbus-daemon --version
D-Bus Message Bus Daemon 1.10.6
Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Here at Mozilla, we have 200 servers running on HP Moonshot system, all have same hardware configuration and Ubuntu 16.04.2. The OS is not up to date, we use it as is was released. We using a program to tests Firefox source code and after each test we reboot the servers using /sbin/reboot. After a while (between 24-48h - during this period ~6 reboots/h are made), randomly, all 200 servers get stuck at the reboot - see the ILO capture - and to bring it back we have to power cycle each of them.
On one of the beta servers, we have made the bellow updates/changes, set debug, set cron to reboot server after 5-10 min, however, the reboot freeze is still present: LINUX_DEFAULT= "reboot= bios" LINUX_DEFAULT= "acpi=off" LINUX_DEFAULT= "reboot= force" /kernel. ubuntu. com/~kernel- ppa/mainline/
- upgraded OS to Ubuntu 16.04.5 latest packages;
- used GRUB_CMDLINE_
- used GRUB_CMDLINE_
- GRUB_CMDLINE_
- upgraded Kernel to v4.15 (the main one from Ubuntu's repo);
- upgraded Kernel to v4.20 from https:/
- now we are testing the reboot with 4.20.3 from the above repo and working to update systemd.
Attached you can find the debug-log for: debuglogkernel- 4.4.txt log-kernel4- 15.txt log-kernel420. txt freeze. PNG
- kernel 4.4.0-66-generic #87-Ubuntu - shutdown-
- kernel 4.15 - shutdown-
- kernel 4.20 shutdown-
- ILO capture with the freeze ILO-reboot-
Please check all this logs/capture and let us know a solution. Thanks.