Bug 21985

Summary:	MCC becomes a white window during packages update (systemd[1]: Looping too fast. Throttling execution a little.)
Product:	Mageia	Reporter:	Christian C <bugzzzz>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	basesystem, mageiatools, marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakconf-12.60-1.mga5, systemd	CVE:
Status comment:
Attachments:	MCC window after packages update Result of some commands

Description Christian C 2017-11-05 21:22:07 CET

Description of problem:
I ran the MCC to make an update, started the update and when I looked at the result, the window was white and I couldn't close it (/usr/bin/perl /usr/libexec/drakrpm-update --embedded 283133810) but with a kill -9 3573 (see attached file).
After killing the process, I got a lot of messages "...Freeing read locks..." while searching the drakrpm-update package (see attached file). I don't know if there is a relation !!

Version-Release number of selected component (if applicable):
rpmdrake-6.20.1-1.mga5

How reproducible:
I don't know. It's the first time.

Steps to Reproduce:
1. start the MCC
2. run an update
3.

Comment 1 Christian C 2017-11-05 21:24:49 CET

Created attachment 9773 [details]
MCC window after packages update

Comment 2 Christian C 2017-11-05 21:31:34 CET

Created attachment 9774 [details]
Result of some commands

Result of commands,
while the white MCC window was displayed :
# cat /var/log/messages
# ps -ef|grep drak
after the white MCC window was closed :
# rpm -qf /usr/libexec/drakrpm-update

Comment 3 Marja Van Waes 2017-11-05 23:15:01 CET

It goes wrong right after the third update transaction gets started:

Nov  5 17:45:30 localhost [RPM][3573]: Transaction ID 59ff402a started
Nov  5 17:45:31 localhost [RPM][3573]: install clamav-db-0.99.2-1.2.mga5.noarch: success
Nov  5 17:45:32 localhost systemd[1]: Unknown serialization item 'subscribed=:1.1'
Nov  5 17:45:32 localhost systemd[1]: Looping too fast. Throttling execution a little.

After that the message about "Looping too fast" is repeated thousands of times.
Transaction ID 59ff402a never finishes. 



I don't know what the culprit is. CC'ing the mageiatools and the basesystem maintainers.

Source RPM: drakconf-12.60-1.mga5 => drakconf-12.60-1.mga5, systemd
CC: (none) => basesystem, mageiatools, marja11
Summary: MCC becomes a white window after packages update => MCC becomes a white window during packages update (systemd[1]: Looping too fast. Throttling execution a little.)

Comment 4 Christian C 2017-11-07 11:35:32 CET

>I don't know what the culprit is. CC'ing the mageiatools and the basesystem >maintainers.
Maybe systemd.
After restarting the computer, I could run the MCC without problem.

Comment 5 Marja Van Waes 2017-11-07 11:56:27 CET

(In reply to Christian CHEVALIER from comment #4)
>> I don't know what the culprit is. CC'ing the mageiatools and the basesystem 
>> maintainers.
> Maybe systemd.

Yeah, something gave systemd a hiccup.... maybe it endlessly attempted to restart a service that kept failing? But if so, then I don't know which service it was, and what made it fail.

> After restarting the computer, I could run the MCC without problem.

Thanks for the feedback. I was about to close this report, but will leave it open as "UNCONFIRMED" so that it'll be found more easily if someone else hits this issue.

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 6 Marja Van Waes 2018-06-11 23:04:28 CEST

(In reply to Marja Van Waes from comment #5)

> 
> > After restarting the computer, I could run the MCC without problem.
> 
> Thanks for the feedback. I was about to close this report, but will leave it
> open as "UNCONFIRMED" so that it'll be found more easily if someone else
> hits this issue.

That was last year and no one reported here they hit the same issue, so whatever it was, it's fixed.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => FIXED