Re: no error handling in Yum any more?
On Mon, Dec 22, 2014 at 05:20:01PM +, Tom Hughes wrote: On 22/12/14 17:07, Jan Kratochvil wrote: On Mon, 22 Dec 2014 05:59:50 +0100, Felix Miata wrote: I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. During F20-F21 upgrade I had to run along something like while sleep 1;do killall systemctl;done (the real command was longer) as many %post scripts tried to restart their daemon but during the upgrade each systemctl command was timing out with very long delay. I had that as well - the cause is that systemd asserts and goes into panic mode which means it no longer responds to systemctl calls. It didn't happen to all my machines but it did to a couple of them. The fix is to kill the dbus-daemon process - after that the systemctl calls will still fail but will do so quickly rather than slowly. You will also won't be able to do a clean reboot so will have to resort to something like sync; reboot -ff to reboot after it completes. FWIW I saw pretty much identical symptoms on 3 different machines. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
Maybe it's caused by buggy sctiptlets, I met this weeks ago on dbus. -- Yours sincerely, Christopher Meng http://cicku.me -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
On 12/21/2014 10:59 PM, Felix Miata wrote: I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. Ps on another tty shows Yum is still running. Disk space and RAM are ample. Top shows virtually no CPU in use. Nothing seems amis in the tail of /var/log/yum.log. How does one find out why nothing is happening? strace -p $YUM_PID -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
On Mon, 22 Dec 2014 05:59:50 +0100, Felix Miata wrote: I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. During F20-F21 upgrade I had to run along something like while sleep 1;do killall systemctl;done (the real command was longer) as many %post scripts tried to restart their daemon but during the upgrade each systemctl command was timing out with very long delay. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
On 22/12/14 17:07, Jan Kratochvil wrote: On Mon, 22 Dec 2014 05:59:50 +0100, Felix Miata wrote: I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. During F20-F21 upgrade I had to run along something like while sleep 1;do killall systemctl;done (the real command was longer) as many %post scripts tried to restart their daemon but during the upgrade each systemctl command was timing out with very long delay. I had that as well - the cause is that systemd asserts and goes into panic mode which means it no longer responds to systemctl calls. It didn't happen to all my machines but it did to a couple of them. The fix is to kill the dbus-daemon process - after that the systemctl calls will still fail but will do so quickly rather than slowly. You will also won't be able to do a clean reboot so will have to resort to something like sync; reboot -ff to reboot after it completes. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
On 22/12/14 17:20, Tom Hughes wrote: On 22/12/14 17:07, Jan Kratochvil wrote: On Mon, 22 Dec 2014 05:59:50 +0100, Felix Miata wrote: I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. During F20-F21 upgrade I had to run along something like while sleep 1;do killall systemctl;done (the real command was longer) as many %post scripts tried to restart their daemon but during the upgrade each systemctl command was timing out with very long delay. I had that as well - the cause is that systemd asserts and goes into panic mode which means it no longer responds to systemctl calls. It didn't happen to all my machines but it did to a couple of them. The evidence to look for to see if you are hitting this problem is messages in the journal like this: Dec 05 09:08:21 gosford.compton.nu systemd[1]: Assertion 'path' failed at ../src/shared/cgroup-util.c:913, function cg_is_empty_recursive(). Aborting. Dec 05 09:08:21 gosford.compton.nu systemd[1]: Caught ABRT, dumped core as pid 3376. along with a core. file in the root directory. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
On Mon, 22 Dec 2014 18:20:01 +0100, Tom Hughes wrote: The fix is to kill the dbus-daemon process - after that the systemctl calls will still fail but will do so quickly rather than slowly. OK, goot to know. You will also won't be able to do a clean reboot so will have to resort to something like sync; reboot -ff to reboot after it completes. Yes, confirming that. Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
On Mon, 22 Dec 2014 18:28:58 +0100, Tom Hughes wrote: The evidence to look for to see if you are hitting this problem is messages in the journal like this: Dec 05 09:08:21 gosford.compton.nu systemd[1]: Assertion 'path' failed at ../src/shared/cgroup-util.c:913, function cg_is_empty_recursive(). Aborting. Dec 05 09:08:21 gosford.compton.nu systemd[1]: Caught ABRT, dumped core as pid 3376. Yes, and then apparently started the timeouts: Dec 11 10:56:38 host2 systemd[1]: Assertion 'path' failed at ../src/shared/cgroup-util.c:913, function cg_is_empty_recursive(). Aborting. Dec 11 10:56:38 host2 systemd[1]: Caught ABRT, dumped core as pid 10486. Dec 11 10:56:38 host2 systemd[1]: Freezing execution. Dec 11 10:57:03 host2 dbus[840]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Dec 11 10:57:28 host2 dbus[840]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Dec 11 10:57:53 host2 dbus[840]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
no error handling in Yum any more?
I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. Ps on another tty shows Yum is still running. Disk space and RAM are ample. Top shows virtually no CPU in use. Nothing seems amis in the tail of /var/log/yum.log. How does one find out why nothing is happening? -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: no error handling in Yum any more?
I've seen this before - it's probably some network glitch. I fixed it by killing the yum job, rebooting, running 'yum clean all' and running a speed test before restarting the yum job. On Sun, Dec 21, 2014 at 8:59 PM, Felix Miata mrma...@earthlink.net wrote: I started a yum upgrade process. When it reached 342/784 (@avahi) over half an hour ago, the screen writing from the process simply halted. Ps on another tty shows Yum is still running. Disk space and RAM are ample. Top shows virtually no CPU in use. Nothing seems amis in the tail of /var/log/yum.log. How does one find out why nothing is happening? -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Twitter: http://twitter.com/znmeb; OSJourno: Robust Power Tools for Digital Journalists https://osjourno.com Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
