Debian Bug report logs - #823346
systemd[1]: system-generators terminated by signal ALRM.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Jean-Luc Coulon \(f5ibh\)" <jean-luc.coulon@wanadoo.fr>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: systemd[1]: system-generators terminated by signal ALRM.

Date: Tue, 03 May 2016 22:06:16 +0200

Package: systemd-cron
Severity: important

Hi,

When I boot my system with systemd installed, it "freezes" (seems to) after 7
seconds or so. This is, on my system, jsut after enumerated the USB devices.
If I left and wait, it restart it normal boot sequence at 90 seconds or so. And
everything went fine.

If I "do something", it gets out of freeze quickier. I tried to plug / unplug an
USB device (I started with the enumerated ones thinking one of them is the
culprit).

An other guy said he has the same message while he swiched from a hdd to a ssd.
I'm on a ssd by this occured very recently. The system has worked flawlessly
for several months. He said that the timeout is shorter if he creates some
entropy pressing many keys on the keyboard.

As the message is related to systemd, I've reinstalle sysvinit. And this fixed
the problem.

I've seen an upgrade of systemd on sid so I tried to reinstall systemd. I got
the same problem.

BUT: if I keep systemd but remove systemd-cron, I've not this problem.

Here is the part of the boot log where the problem appears:
[ 7.405270] usb 1-6: new high-speed USB device number 4 using xhci_hcd
[ 7.578858] usb 1-6: New USB device found, idVendor=0424, idProduct=2514
[ 7.579007] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 7.579746] hub 1-6:1.0: USB hub found
[ 7.579939] hub 1-6:1.0: 2 ports detected
[ 7.858529] usb 1-6.1: new full-speed USB device number 5 using xhci_hcd
[ 7.957340] usb 1-6.1: New USB device found, idVendor=045e, idProduct=0745
[ 7.957489] usb 1-6.1: New USB device strings: Mfr=1, Product=2, SerialNumber
=0
[ 7.957661] usb 1-6.1: Product: Microsoft® 2.4GHz Transceiver v6.0
[ 7.957801] usb 1-6.1: Manufacturer: Microsoft
[ 93.198778] systemd[1]: system-generators terminated by signal ALRM.
[ 93.274495] systemd[1]: Listening on Journal Audit Socket.
[ 93.275318] systemd[1]: Started Dispatch Password Requests to Console Directory
Watch.
[ 93.276091] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 93.276835] systemd[1]: Listening on udev Control Socket.


The USB devices are a EATON UPS and my keyboard/mouse.
I tried to unplug them before the boot and I get the same problem.
If I unplug one of them while if "freeze" state, the boot process resumes.
If I plug anything (usb disk, usb key), it resumes also.

So for the moment, I've the system running with systemd, systemd-cron is
uninstalled and I've cron/anacron instead.

Regards

Jean-Luc





-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-rc5-i7-1.1 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Message #10 received at 823346@bugs.debian.org (full text, mbox, reply):

From: Alexandre Detiste <alexandre.detiste@gmail.com>

To: "Jean-Luc Coulon (f5ibh)" <jean-luc.coulon@wanadoo.fr>, 823346@bugs.debian.org

Subject: Re: Bug#823346: systemd[1]: system-generators terminated by signal ALRM.

Date: Tue, 03 May 2016 22:44:36 +0200

Hum,

That's interresting, I've had the same problem for a while,
but I have had other things to worry about so I didn't investigage it yet.

Here boot hangs at "Welcome to Jessie !" or something  but just pressing any key (PS/2 keyboard)
is enough to make it go further.

Nothing changed in systemd-cron & it has been pretty much "done" for a long time now;
so problem is likely somewhere else. I guess blindly re-assigning it to systemd
won't help (and that already happens so many times).

> He said that the timeout is shorter if he creates some
> entropy pressing many keys on the keyboard.

Same thing here


I'll just this bug open for now.

Greets,

Le mardi 3 mai 2016 22:06:16, vous avez écrit :
> Package: systemd-cron
> Severity: important
> 
> Hi,
> 
> When I boot my system with systemd installed, it "freezes" (seems to) after 7
> seconds or so. This is, on my system, jsut after enumerated the USB devices.
> If I left and wait, it restart it normal boot sequence at 90 seconds or so. And
> everything went fine.
> 
> If I "do something", it gets out of freeze quickier. I tried to plug / unplug an
> USB device (I started with the enumerated ones thinking one of them is the
> culprit).
> 
> An other guy said he has the same message while he swiched from a hdd to a ssd.
> I'm on a ssd by this occured very recently. The system has worked flawlessly
> for several months. He said that the timeout is shorter if he creates some
> entropy pressing many keys on the keyboard.
> 
> As the message is related to systemd, I've reinstalle sysvinit. And this fixed
> the problem.
> 
> I've seen an upgrade of systemd on sid so I tried to reinstall systemd. I got
> the same problem.
> 
> BUT: if I keep systemd but remove systemd-cron, I've not this problem.
> 
> Here is the part of the boot log where the problem appears:
> [ 7.405270] usb 1-6: new high-speed USB device number 4 using xhci_hcd
> [ 7.578858] usb 1-6: New USB device found, idVendor=0424, idProduct=2514
> [ 7.579007] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [ 7.579746] hub 1-6:1.0: USB hub found
> [ 7.579939] hub 1-6:1.0: 2 ports detected
> [ 7.858529] usb 1-6.1: new full-speed USB device number 5 using xhci_hcd
> [ 7.957340] usb 1-6.1: New USB device found, idVendor=045e, idProduct=0745
> [ 7.957489] usb 1-6.1: New USB device strings: Mfr=1, Product=2, SerialNumber
> =0
> [ 7.957661] usb 1-6.1: Product: Microsoft® 2.4GHz Transceiver v6.0
> [ 7.957801] usb 1-6.1: Manufacturer: Microsoft
> [ 93.198778] systemd[1]: system-generators terminated by signal ALRM.
> [ 93.274495] systemd[1]: Listening on Journal Audit Socket.
> [ 93.275318] systemd[1]: Started Dispatch Password Requests to Console Directory
> Watch.
> [ 93.276091] systemd[1]: Listening on Device-mapper event daemon FIFOs.
> [ 93.276835] systemd[1]: Listening on udev Control Socket.
> 
> 
> The USB devices are a EATON UPS and my keyboard/mouse.
> I tried to unplug them before the boot and I get the same problem.
> If I unplug one of them while if "freeze" state, the boot process resumes.
> If I plug anything (usb disk, usb key), it resumes also.
> 
> So for the moment, I've the system running with systemd, systemd-cron is
> uninstalled and I've cron/anacron instead.
> 
> Regards
> 
> Jean-Luc
> 
> 
> 
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.6.0-rc5-i7-1.1 (SMP w/8 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 

Message #15 received at 823346@bugs.debian.org (full text, mbox, reply):

From: Felipe Sateler <fsateler@debian.org>

To: Alexandre Detiste <alexandre.detiste@gmail.com>, 823346@bugs.debian.org

Cc: "Jean-Luc Coulon (f5ibh)" <jean-luc.coulon@wanadoo.fr>

Subject: Re: Bug#823346: systemd[1]: system-generators terminated by signal ALRM.

Date: Tue, 3 May 2016 19:17:59 -0300

On 3 May 2016 at 17:44, Alexandre Detiste <alexandre.detiste@gmail.com> wrote:
>
> Hum,
>
> That's interresting, I've had the same problem for a while,
> but I have had other things to worry about so I didn't investigage it yet.
>
> Here boot hangs at "Welcome to Jessie !" or something  but just pressing any key (PS/2 keyboard)
> is enough to make it go further.
>
> Nothing changed in systemd-cron & it has been pretty much "done" for a long time now;
> so problem is likely somewhere else. I guess blindly re-assigning it to systemd
> won't help (and that already happens so many times).
>
> > He said that the timeout is shorter if he creates some
> > entropy pressing many keys on the keyboard.
>
> Same thing here
>
>
> I'll just this bug open for now.

FWIW, we have already received this bug on package systemd: #823337

-- 

Saludos,
Felipe Sateler

Message #20 received at 823346@bugs.debian.org (full text, mbox, reply):

From: Alexandre Detiste <alexandre.detiste@gmail.com>

To: 823337@bugs.debian.org, 823346@bugs.debian.org, 822431@bugs.debian.org

Subject: Re: systemd: Boot stalls for 90 s at early boot (system-generators terminated by signal ALRM)

Date: Fri, 06 May 2016 20:12:12 +0200

Found it :-)

This is a Python bug: https://bugs.python.org/issue26839

Sorry for cross posting to the three bugs.

I don't know, how/wether these 3 bugs should those been merged.

Martin/Matthias, can you handle this ?

-----

How I found it:

The first line I get in dmesg after typing something at the keyboard is  "random: nonblocking pool is initialized"

systemd-cron does uses Python's hashlib to compute md5's; but that doesn't need any source of randomness at all.

Now I see even an empty python program
with only the shebang line would still trigger this delay;
so this had to be a python runtime related bug.


Alexandre

Message #37 received at 823346@bugs.debian.org (full text, mbox, reply):

From: peter <peter.newey@yahoo.co.uk>

To: 823346@bugs.debian.org

Subject: Bug report#821877

Date: Tue, 10 May 2016 07:06:51 +0100

Package: python3.5

Version: 3.5.1-12

Hallo

I submitted bug #821877 after updating to python3.5 version 3.5.1-11 so 
returned to using version 3.5.1-10

Seeing an update available  to use version 3.5.1.-12 I expected my 
problem to be solved. However this version appeared to cause the same delay.


Seeing my bug linked to this bug number I tried :

So for the moment, I've the system running with systemd, systemd-cron is
uninstalled and I've cron/anacron instead.

from the bug comments.

So updated to python3.5 version 3.5.1-12 and without systemd-cron , but 
using cron and anacron ,there is no delay with start up

Message #40 received at 824379-close@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: 824379-close@bugs.debian.org

Subject: Bug#824379: fixed in python3.5 3.5.1-14

Date: Thu, 09 Jun 2016 17:04:21 +0000

Source: python3.5
Source-Version: 3.5.1-14

We believe that the bug you reported is fixed in the latest version of
python3.5, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 824379@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated python3.5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 09 Jun 2016 17:41:54 +0200
Source: python3.5
Binary: python3.5 python3.5-venv libpython3.5-stdlib python3.5-minimal libpython3.5-minimal libpython3.5 python3.5-examples python3.5-dev libpython3.5-dev libpython3.5-testsuite idle-python3.5 python3.5-doc python3.5-dbg libpython3.5-dbg
Architecture: source
Version: 3.5.1-14
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose <doko@debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Description:
 idle-python3.5 - IDE for Python (v3.5) using Tkinter
 libpython3.5 - Shared Python runtime library (version 3.5)
 libpython3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 libpython3.5-dev - Header files and a static library for Python (v3.5)
 libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
 libpython3.5-stdlib - Interactive high-level object-oriented language (standard library
 libpython3.5-testsuite - Testsuite for the Python standard library (v3.5)
 python3.5  - Interactive high-level object-oriented language (version 3.5)
 python3.5-dbg - Debug Build of the Python Interpreter (version 3.5)
 python3.5-dev - Header files and a static library for Python (v3.5)
 python3.5-doc - Documentation for the high-level object-oriented language Python
 python3.5-examples - Examples for the Python language (v3.5)
 python3.5-minimal - Minimal subset of the Python language (version 3.5)
 python3.5-venv - Interactive high-level object-oriented language (pyvenv binary, v
Closes: 824379
Changes:
 python3.5 (3.5.1-14) unstable; urgency=medium
 .
   * Update to 20160609 from the 3.5 branch.
     - A new version of typing.py provides several new classes and
       features: @overload outside stubs, Reversible, DefaultDict, Text,
       ContextManager, Type[], NewType(), TYPE_CHECKING, and numerous bug
       fixes (note that some of the new features are not yet implemented in
       mypy or other static analyzers).  Also classes for PEP 492
       (Awaitable, AsyncIterable, AsyncIterator) have been added (in fact
       they made it into 3.5.1 but were never mentioned).
     - Issue #25738: Stop http.server.BaseHTTPRequestHandler.send_error() from
       sending a message body for 205 Reset Content.  Also, don't send Content
       header fields in responses that don't have a body.
     - Issue #21313: Fix the "platform" module to tolerate when sys.version
       contains truncated build information.
     - Issue #26839: On Linux, :func:`os.urandom` now calls ``getrandom()`` with
       ``GRND_NONBLOCK`` to fall back on reading ``/dev/urandom`` if the urandom
       entropy pool is not initialized yet. Closes: #824379.
     - Issue #27164: In the zlib module, allow decompressing raw Deflate streams
       with a predefined zdict.
     - Issue #24291: Fix wsgiref.simple_server.WSGIRequestHandler to completely
       write data to the client.  Previously it could do partial writes and
       truncate data.  Also, wsgiref.handler.ServerHandler can now handle stdout
       doing partial writes, but this is deprecated.
     - Issue #26809: Add ``__all__`` to :mod:`string`.
     - Issue #26373: subprocess.Popen.communicate now correctly ignores
       BrokenPipeError when the child process dies before .communicate()
       is called in more/all circumstances.
     - Issue #24759: Make clear in idlelib.idle_test.__init__ that the directory
       is a private implementation of test.test_idle and tool for maintainers.
     - Issue #27196: Stop 'ThemeChanged' warnings when running IDLE tests.
       These persisted after other warnings were suppressed in #20567.
     - Issue #20567: Revise idle_test/README.txt with advice about avoiding
       tk warning messages from tests.  Apply advice to several IDLE tests.
     - Issue #26884: Fix linking extension modules for cross builds.
     - Issue #26014: Update 3.x packaging documentation:
       * "See also" links to the new docs are now provided in the legacy pages
       * links to setuptools documentation have been updated
     - Issue #27229: Fix the cross-compiling pgen rule for in-tree builds.
   * Don't run multiprocessing tests during the profiling build.
Checksums-Sha1:
 eb952aa73473632b3eb17674222da20e4a14e8e6 3233 python3.5_3.5.1-14.dsc
 9f42aa6213777400c271398b788a3b35b59a56ce 663984 python3.5_3.5.1-14.debian.tar.xz
Checksums-Sha256:
 660d2174856cdf95358211eabe15c7d0439da4c06a9905d982e6e29fd75301ae 3233 python3.5_3.5.1-14.dsc
 3871f070b3c21d15aa85b2901719e066b7f4fd59c9dd5781c311a86e133bf4dc 663984 python3.5_3.5.1-14.debian.tar.xz
Files:
 3da5ca0d2f36030024437341b1724348 3233 python optional python3.5_3.5.1-14.dsc
 e6cd9d58d69f061931e6d633ffcb82a5 663984 python optional python3.5_3.5.1-14.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXWZMpAAoJEL1+qmB3j6b1qnoP/jlu86va/KqI7GmHiHd9wHEw
rsMbscOw726lnsd5w3dz5SrnIgxLcr12u0wA5fjDpM7neenvIhpkNH4w5clnbju1
8xYTlsqF53sOkPKT26/00JuKg2uX8fDSgkrnpjBlosJpJXHMzuKhChJYJraisl3V
VWRci03Ph2nMPBOGRab6dQySkvKYFzPdorKz3t7fQafT3mh6fsl2ue3cAeC9/gMX
yX5tcPB5u7naVKsUtJX/eIT9T5mvVGuJ/K0KNN9LmvB51A56UfpuQHPqMwN5U9BQ
FBiscosxKnKNN0wMqT4xa1RqM8Q2A1jRL4QJ6/2EbAkYfa/0sf5zU640XdRY7E7E
RnfyD7GyhkzW7EBhL9lFSJDz8Zvz6wfKuqX2fbBKf203R8H5Z6ibRhfRoOJBGHOs
kypce48ANwbkOEwOMq+7nVHbizGbZgUj9xfd4SVUlhfZS2vpu/mTxbAQgQSBAM1k
w7wIuenwUN2K41dJ8qVs2ifsy9Bfrgm7OPPtimDe8vYCqBrDnE1qM1RbDDqi5j+e
x1sbTqaeFJcsI1m4WdB2raMtmwLd5+vkFCBYq1uHdN+uo0b6sD5vpHBinut/iltE
kjlIbw6aKajafB+CaHgvsh/5vDZ5loUsNEO98ix4okYGknN+3fQHCGdlN/Ey9RDR
Y55/vf11gYTNO2XCDCCv
=IpF0
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.