FS#43142 - [systemd] "Looping too fast. Throttling execution a little." on systemctl stop/start

Attached to Project: Arch Linux
Opened by Daniel (Dan39) - Wednesday, 17 December 2014, 19:15 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 03 July 2016, 21:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

When trying to systemctl start/stop a service systemctl hangs, and does not start/stop anything until I do ctrl+c, then it successfully starts/stops.

In journalctl I see

Dec 17 13:48:34 mypc systemd[1]: Looping too fast. Throttling execution a little.
Dec 17 13:48:33 mypc systemd[1]: Looping too fast. Throttling execution a little.
Dec 17 13:48:32 mypc systemd[1]: Looping too fast. Throttling execution a little.
Dec 17 13:48:31 mypc systemd[1]: Looping too fast. Throttling execution a little.
Dec 17 13:48:29 mypc systemd[1]: Looping too fast. Throttling execution a little.
Dec 17 13:48:28 mypc systemd[1]: Looping too fast. Throttling execution a little.
Dec 17 13:48:27 mypc systemd[1]: Looping too fast. Throttling execution a little.

repeated until I ctrl+c.
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 03 July 2016, 21:15 GMT
Reason for closing:  No response
Additional comments about closing:  This is typically a symptom, not an actual cause. If there's something specific you think upstream needs to do, please follow up on their bug tracker.
Comment by Doug Newgard (Scimmia) - Thursday, 18 December 2014, 16:41 GMT
Happening with what version? I'm assuming 217-8?
Comment by Daniel (Dan39) - Thursday, 18 December 2014, 17:19 GMT
Yes systemd 217-8

Last ran pacman -Syu on Dec 13, haven't rebooted since. I'm guessing if I reboot it will fix the issue :P

The only odd thing about my current system to note is I havn't upgraded the linux package since Nov 30, it is currently at 3.17.4-1. All other packages were last updated Dec 13, including linux-firmware. Will that cause issues since it is now newer version than linux package?
Comment by Dave Reisner (falconindy) - Thursday, 18 December 2014, 17:56 GMT
Please try with systemd 218. If it's still happening, disable your services in /etc. If after that, it's still happening, then please file a bug upstream with as much debugging information as possible.
Comment by Daniel (Dan39) - Friday, 19 December 2014, 00:36 GMT
ran all updates and rebooted. everything is fine now, will reply again if the issue shows back up. thanks
Comment by mielouk (mielouk) - Sunday, 10 May 2015, 15:23 GMT
  • Field changed: Percent Complete (100% → 0%)
I ask to reopen this bug. It happens on my remote server, which is quite annoying. Every second boot exactly the same message repeats, till someone has to soft-kill it, thus it doesn't power down by pressing the power button, as it is supposed to. The automated connection to AirVPN is coming up but no other external service like SSH, webinterfaces or any other external service is coming up. After the reboot everything is fine. Which information do you need? Hardware, the logs in a pastebin? This is quite sensitive information.
Comment by mielouk (mielouk) - Monday, 11 May 2015, 09:14 GMT
It happend to me about a month ago, don't know which version of systemd that was but it happend this time with systemd 219-6, kernel 4.0.1-1.

Hardware: Gigabyte GA-H77N-WIFI

Mai 09 16:35:14 X systemd-logind[501]: Failed to enable subscription: Connection timed out
Mai 09 16:35:14 X systemd[1]: Failed to register name: Connection timed out
Mai 09 16:35:14 X systemd[1]: Failed to set up API bus: Connection timed out
Mai 09 16:35:14 X systemd-logind[501]: Failed to fully start up daemon: Connection timed out

Mai 09 16:35:14 X systemd[1]: Failed to start Login Service.

Mai 09 16:35:17 X openvpn@aqua[524]: Initialization Sequence Completed
Mai 09 16:35:17 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:19 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:20 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:21 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:22 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:23 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:25 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:26 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:27 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:29 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 16:35:29 X INADYN[517]: Sat May 9 16:35:29 2015: W:IP: Error 0x65 resolving host name 'google.com'
Mai 09 16:35:29 X INADYN[517]: Sat May 9 16:35:29 2015: C:TCP: failed socket create in connect_thread...

Mai 09 16:35:14 X systemd-logind[501]: Failed to enable subscription: Connection timed out
Mai 09 16:35:14 X systemd[1]: Failed to register name: Connection timed out
Mai 09 16:35:14 X systemd[1]: Failed to set up API bus: Connection timed out
Mai 09 16:35:14 X systemd-logind[501]: Failed to fully start up daemon: Connection timed out

Mai 09 16:35:14 X systemd[1]: Failed to start Login Service.

FROM THIS POINT ON IT REPEATED CONTINOUSLY

Mai 09 17:47:25 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 17:47:27 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 17:47:28 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 17:47:29 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 17:47:30 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 17:47:32 X systemd[1]: Looping too fast. Throttling execution a little.
Mai 09 17:47:32 X INADYN[517]: Sat May 9 17:47:32 2015: W:IP: Error 0x65 resolving host name 'google.com'
Mai 09 17:47:32 X INADYN[517]: Sat May 9 17:47:32 2015: C:TCP: failed socket create in connect_thread...

Till it got soft killed via the powerbutton. (My powerbutton handler isn't very patient with the console;)

Please tell me if you need any other information.
Comment by Maxime de Roucy (akira86) - Monday, 29 February 2016, 23:54 GMT
Just for information, it seams to be a systemd bug :
https://lists.freedesktop.org/archives/systemd-devel/2015-September/034356.html

It can be "temporarily" fixed by : systemctl daemon-reexec
Comment by Dave Reisner (falconindy) - Saturday, 18 June 2016, 13:04 GMT
Is this still a problem with v230? There's never any one specific cause for this, but it's surely not a packaging problem.

Loading...