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
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
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.
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
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
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
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
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
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
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
10 matches
Mail list logo
