{"action":"created","issue":{"url":"https://api.github.com/repos/geerlingguy/ansible-role-security/issues/21","repository_url":"https://api.github.com/repos/geerlingguy/ansible-role-security","labels_url":"https://api.github.com/repos/geerlingguy/ansible-role-security/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/geerlingguy/ansible-role-security/issues/21/comments","events_url":"https://api.github.com/repos/geerlingguy/ansible-role-security/issues/21/events","html_url":"https://github.com/geerlingguy/ansible-role-security/issues/21","id":177457254,"number":21,"title":"CentOS 7 Docker test gets stuck starting Fail2Ban","user":{"login":"geerlingguy","id":481677,"avatar_url":"https://avatars.githubusercontent.com/u/481677?v=3","gravatar_id":"","url":"https://api.github.com/users/geerlingguy","html_url":"https://github.com/geerlingguy","followers_url":"https://api.github.com/users/geerlingguy/followers","following_url":"https://api.github.com/users/geerlingguy/following{/other_user}","gists_url":"https://api.github.com/users/geerlingguy/gists{/gist_id}","starred_url":"https://api.github.com/users/geerlingguy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geerlingguy/subscriptions","organizations_url":"https://api.github.com/users/geerlingguy/orgs","repos_url":"https://api.github.com/users/geerlingguy/repos","events_url":"https://api.github.com/users/geerlingguy/events{/privacy}","received_events_url":"https://api.github.com/users/geerlingguy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-09-16T15:41:52Z","updated_at":"2016-09-16T16:35:58Z","closed_at":null,"body":"During the Travis tests, CentOS 7 gets stuck on:\r\n\r\n```\r\nTASK [role_under_test : Ensure fail2ban is running and enabled on boot.] *******\r\n\r\nNo output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.\r\n\r\nThe build has been terminated\r\n```\r\n\r\nI can reproduce the issue on Docker for Mac 1.12.0/.1, and if I run `journalctl --no-pager`, I notice a _lot_ of the following:\r\n\r\n```\r\nSep 16 15:33:54 1b08686e974b systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:33:56 1b08686e974b systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:33:57 1b08686e974b systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:33:58 1b08686e974b systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:34:00 1b08686e974b systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:34:01 1b08686e974b systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:34:02 1b08686e974b systemd[1]: Looping too fast. Throttling execution a little.\r\n```\r\n\r\nIt seems these messages occur after I install fail2ban, which triggers an update to systemd (with `yum install -y fail2ban`):\r\n\r\n```\r\nSep 16 15:39:31 7c6e69e84968 yum[201]: Installed: python-decorator-3.4.0-3.el7.noarch\r\nSep 16 15:39:31 7c6e69e84968 yum[201]: Updated: systemd-libs-219-19.el7_2.13.x86_64\r\nSep 16 15:39:31 7c6e69e84968 systemd[1]: Closed udev Control Socket.\r\nSep 16 15:39:31 7c6e69e84968 systemd[1]: Closed udev Kernel Socket.\r\nSep 16 15:39:31 7c6e69e84968 systemd[1]: Stopped udev Kernel Device Manager.\r\nSep 16 15:39:32 7c6e69e84968 systemd[1]: Reexecuting.\r\nSep 16 15:39:32 7c6e69e84968 systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)\r\nSep 16 15:39:32 7c6e69e84968 systemd[1]: Detected virtualization docker.\r\nSep 16 15:39:32 7c6e69e84968 systemd[1]: Detected architecture x86-64.\r\nSep 16 15:39:32 7c6e69e84968 systemd[1]: Failed to install release agent, ignoring: File exists\r\nSep 16 15:39:57 7c6e69e84968 systemd[1]: Failed to register match for Disconnected message: Connection timed out\r\nSep 16 15:40:22 7c6e69e84968 systemd[1]: Failed to register match for Disconnected message: Connection timed out\r\nSep 16 15:40:22 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:22 7c6e69e84968 yum[201]: Updated: systemd-219-19.el7_2.13.x86_64\r\nSep 16 15:40:23 7c6e69e84968 systemd[1]: Configuration file /usr/lib/systemd/system/ebtables.service is marked executable. Please remove executable permission bits. Proceeding anyway.\r\nSep 16 15:40:23 7c6e69e84968 systemd[1]: Configuration file /usr/lib/systemd/system/ebtables.service is marked executable. Please remove executable permission bits. Proceeding anyway.\r\nSep 16 15:40:23 7c6e69e84968 systemd[1]: Reloading.\r\nSep 16 15:40:23 7c6e69e84968 yum[201]: Installed: ebtables-2.0.10-13.el7.x86_64\r\nSep 16 15:40:24 7c6e69e84968 yum[201]: Installed: systemd-python-219-19.el7_2.13.x86_64\r\nSep 16 15:40:24 7c6e69e84968 yum[201]: Installed: grubby-8.28-17.el7.x86_64\r\nSep 16 15:40:24 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:24 7c6e69e84968 yum[201]: Installed: ssmtp-2.64-14.el7.x86_64\r\nSep 16 15:40:24 7c6e69e84968 yum[201]: Installed: libselinux-python-2.2.2-6.el7.x86_64\r\nSep 16 15:40:24 7c6e69e84968 yum[201]: Installed: python-slip-0.4.0-2.el7.noarch\r\nSep 16 15:40:24 7c6e69e84968 yum[201]: Installed: python-slip-dbus-0.4.0-2.el7.noarch\r\nSep 16 15:40:25 7c6e69e84968 systemd[1]: Configuration file /usr/lib/systemd/system/ebtables.service is marked executable. Please remove executable permission bits. Proceeding anyway.\r\nSep 16 15:40:25 7c6e69e84968 systemd[1]: Reloading.\r\nSep 16 15:40:25 7c6e69e84968 systemd[1]: Configuration file /usr/lib/systemd/system/ebtables.service is marked executable. Please remove executable permission bits. Proceeding anyway.\r\nSep 16 15:40:25 7c6e69e84968 yum[201]: Installed: firewalld-0.3.9-14.el7.noarch\r\nSep 16 15:40:25 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:26 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:27 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:28 7c6e69e84968 yum[201]: Installed: linux-firmware-20150904-43.git6ebf5d5.el7.noarch\r\nSep 16 15:40:29 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:30 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:31 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\nSep 16 15:40:32 7c6e69e84968 systemd[1]: Looping too fast. Throttling execution a little.\r\n```\r\n\r\nSome references that _could_ be helpful:\r\n\r\n  - https://github.com/systemd/systemd/issues/719\r\n  - http://unix.stackexchange.com/questions/266678/why-does-systemd-prints-looping-too-fast-and-what-to-do"},"comment":{"url":"https://api.github.com/repos/geerlingguy/ansible-role-security/issues/comments/247647474","html_url":"https://github.com/geerlingguy/ansible-role-security/issues/21#issuecomment-247647474","issue_url":"https://api.github.com/repos/geerlingguy/ansible-role-security/issues/21","id":247647474,"user":{"login":"geerlingguy","id":481677,"avatar_url":"https://avatars.githubusercontent.com/u/481677?v=3","gravatar_id":"","url":"https://api.github.com/users/geerlingguy","html_url":"https://github.com/geerlingguy","followers_url":"https://api.github.com/users/geerlingguy/followers","following_url":"https://api.github.com/users/geerlingguy/following{/other_user}","gists_url":"https://api.github.com/users/geerlingguy/gists{/gist_id}","starred_url":"https://api.github.com/users/geerlingguy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geerlingguy/subscriptions","organizations_url":"https://api.github.com/users/geerlingguy/orgs","repos_url":"https://api.github.com/users/geerlingguy/repos","events_url":"https://api.github.com/users/geerlingguy/events{/privacy}","received_events_url":"https://api.github.com/users/geerlingguy/received_events","type":"User","site_admin":false},"created_at":"2016-09-16T16:35:58Z","updated_at":"2016-09-16T16:35:58Z","body":"The above seems to have fixed the issue locally. Will re-run latest tests on Travis too."}}
{"actor":{"display_login":"geerlingguy"}}