please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: dbus (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I have found that if I set the reboot once at 15 min, the server works
for 5-6 days. If the reboots are done once at 10 min, the server get
stuck in 24-48h max. Now I'm testing the reboots once at 20min, it
should take 10 days or more until is stuck.
Also, I have tried all "reboot=" grub options,
I have activated RuntimeWatchdogSec=20s and ShutdownWatchdogSec=1min in
/etc/systemd/system.conf and set the reboot, the server get stuck in
105min.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17834
The test server get stuck after ~9h, here is the debug log.
** Attachment added: "shutdown-log-process.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5241740/+files/shutdown-log-process.txt
--
You received this bug notification because you are a member of Ubu
I think it stuck in firmware/hardware instead of userspace process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bu
Tested with multiple OSs, all stuck: Ubuntu 14, Fedora 29, Arch Linux
current 2019.02.01.
We received a detailed note from the next level of support with HPE and
decided to test with Ubuntu 16 (our production one) and set "ps -ef >>
/shutdown-log.txt" in to the debug.sh script. Maybe we can see so
This get stuck in max 5 hours. We'll try to install a non systemd
Ubuntu, like v14 to test it.
** Attachment added: "centos7.PNG"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5240612/+files/centos7.PNG
--
You received this bug notification because you are a memb
Or a kernel regression, Centos 7 uses an older kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug go to:
http
We installed Centos 7 and started the reboot test now. If this fail
again then is a hardware issue, if not, then it can be from Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
s
Well, I don't think trials and errors can get any fruitful result, this
issue really needs hardware vendor to investigate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Faile
That was already tested and no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug go to:
https://bugs.launchpad
Try kernel parameter "acpi=off".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug go to:
https://bugs.launchpad.net
I have disabled the acpi services (acpid.path, acpid.service,
acpid.socket and set up the reboot once at 5 min. The server get stuck
after 13h.
Something else to try?
** Attachment added: "reboot-acpi-off.zip"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/52401
> Any other suggestion from your side?
The system hang in this bug is really hardware related, so HPE needs to take a
deeper look.
For someone like us that cannot dig into firmware/hardware and need to
find a solution at software level, in general I'll start with disabling
runtime power managemen
After 5 hours of reboot the server is stuck. See the attached debug log
and ILO capture.
** Attachment added: "Ubuntu-18.zip"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5238635/+files/Ubuntu-18.zip
--
You received this bug notification because you are a member
We sent all the logs and captures data to HPE and they asked to update
the BIOS to the latest one. We already using the latest firmware, 4
months past the recommended firmware. Also, we have 200 servers with
Windows 10 doing same test - reboot after each test and there are no
hangs. HPE stated that
After 36h of rebooting, the system is stuck. Attached is the debug log.
** Attachment added: "shutdown-logsysd237.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5232412/+files/shutdown-logsysd237.txt
--
You received this bug notification because you are a mem
We will notify them if the systemd does not fix the issue. So far, after
the systemd upgrade, the server reboots fine in 24h test (reboot once at
5 min).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Please let the hardware vendor know. This is highly likely a platform bug.
AFAICT, systemd has done its part, so the bug is either in the kernel (less
likely) or in the BIOS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
reboot=pci does not help, it get stuck after 19 hours (reboot once at 5
min). Attached is the debug log. On ILO we get the same as I sent in my
first post - see capture from the arhive.
We'll update systemd to 237 and test it.
** Attachment added: "shutdown-log-reboot-pci.txt"
https://bugs.la
I did not tried reboot=pci, will try now. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug go to:
https://b
Have you tried other reboot quirk like "reboot=pci"? It may help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
systemd: Failed to send signal
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
syste
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783499
Title:
sy
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
25 matches
Mail list logo
