Your message dated Wed, 13 May 2015 19:53:40 +0000 with message-id <e1ysciq-0006qw...@franck.debian.org> and subject line Bug#781886: fixed in qcontrol 0.5.4-2 has caused the Debian Bug report #781886, regarding qcontrol failure to start on boot sometimes (jessie, systemd?) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 781886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: qcontrol Version: 0.5.4-1 Severity: normal After a recent wheezy->jessie upgrade, I noticed that qcontrol sometimes fails to start on boot (or qcontrold? not sure what the difference is). I noticed this because on one QNAP TS-419, "journalctl -f" seemed to log temperatures occasionally, while on another QNAP TS-419, there were no such messages. The front LED was also flashing red until qcontrol was properly started manually. Below is "journalctl|grep qcontrol". As you can see, I managed to get it going by manually stopping and starting the qcontrol and qcontrold services. Perhaps systemd is starting the qcontrol service too early during boot? (The system was only booted on apr 02 12:08, not on apr 03 even though the qcontrol log lines mention system boot completed) Apr 02 12:08:27 hostname systemd[1]: Starting LSB: Start qcontrol daemon... Apr 02 12:08:28 hostname qcontrol[617]: qcontrol 0.5.4 daemon starting. Apr 02 12:08:28 hostname qcontrold[480]: Starting qcontrol daemon: qcontrol. Apr 02 12:08:28 hostname qcontrol[617]: evdev: Error opening /dev/input/by-path/platform-gpio-keys-event: No such file or directory Apr 02 12:08:28 hostname qcontrol[617]: register() - Error loading module Apr 02 12:08:28 hostname systemd[1]: Started LSB: Start qcontrol daemon. Apr 02 12:08:36 hostname systemd[1]: qcontrol.service: control process exited, code=exited status=255 Apr 02 12:08:36 hostname systemd[1]: Unit qcontrol.service entered failed state. Apr 02 12:08:36 hostname qcontrol[972]: System boot completed. Apr 02 12:08:36 hostname qcontrol[972]: Error connecting to socket: No such file or directory Apr 03 15:45:43 hostname qcontrol[17505]: System boot completed. Apr 03 15:45:43 hostname qcontrol[17505]: Error connecting to socket: No such file or directory Apr 03 15:45:43 hostname systemd[1]: qcontrol.service: control process exited, code=exited status=255 Apr 03 15:45:43 hostname systemd[1]: Unit qcontrol.service entered failed state. Apr 03 15:47:20 hostname systemd[1]: Stopping LSB: Start qcontrol daemon... Apr 03 15:47:20 hostname qcontrold[17602]: Stopping qcontrol daemon: qcontrol. Apr 03 15:47:20 hostname systemd[1]: Stopped LSB: Start qcontrol daemon. Apr 03 15:47:23 hostname systemd[1]: Starting LSB: Start qcontrol daemon... Apr 03 15:47:23 hostname qcontrold[17624]: Starting qcontrol daemon: qcontrol. Apr 03 15:47:23 hostname systemd[1]: Started LSB: Start qcontrol daemon. Apr 03 15:47:23 hostname qcontrol[17628]: qcontrol 0.5.4 daemon starting. Apr 03 15:47:23 hostname qcontrol[17628]: confdir: loading from /etc/qcontrol.d... Apr 03 15:47:25 hostname qcontrol[17649]: System boot completed. Apr 03 15:47:25 hostname qcontrol[17628]: System status: start Apr 03 15:47:28 hostname qcontrol[17628]: ts41x: temperature 34 Apr 03 15:47:28 hostname qcontrol[17628]: ts41x: temperature 34 setting fan to "high" Apr 03 15:47:33 hostname qcontrol[17628]: ts41x: temperature 34 setting fan to "medium" Apr 03 15:47:38 hostname qcontrol[17628]: ts41x: temperature 34 setting fan to "low" Apr 03 23:19:37 hostname qcontrol[17628]: ts41x: temperature 32 Apr 04 04:05:59 hostname qcontrol[17628]: ts41x: temperature 34 Apr 04 04:36:08 hostname qcontrol[17628]: ts41x: temperature 32 Apr 04 07:43:13 hostname qcontrol[17628]: ts41x: temperature 31 setting fan to "silence" -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.16.0-4-kirkwood Locale: LANG=en_US.UTF-8, LC_CTYPE=nb_NO.iso88591 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qcontrol depends on: ii libc6 2.19-17 ii liblua5.1-0 5.1.5-7.1 ii udev 215-12 qcontrol recommends no packages. qcontrol suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: qcontrol Source-Version: 0.5.4-2 We believe that the bug you reported is fixed in the latest version of qcontrol, 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 781...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Campbell <i...@debian.org> (supplier of updated qcontrol 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 13 May 2015 20:02:02 +0100 Source: qcontrol Binary: qcontrol qcontrol-udeb Architecture: source Version: 0.5.4-2 Distribution: unstable Urgency: medium Maintainer: Ian Campbell <i...@debian.org> Changed-By: Ian Campbell <i...@debian.org> Description: qcontrol - hardware control for QNAP Turbo Station devices qcontrol-udeb - hardware control for QNAP Turbo Station devices (udeb) Closes: 749127 781886 Changes: qcontrol (0.5.4-2) unstable; urgency=medium . * Update Vcs-* to point to anonscm. * Wait for necessary devices to appear before starting. (Closes: #781886). This works around an issue exposed by systemd LSB compatibility mode. Proper systemd support will come later. * Update path to examples in man page. (Closes: #749127) * Update to standards version 0.9.6, no changes required. Checksums-Sha1: a8c089f044d06f4a7db1ce57fc0b2343d77a13e4 1949 qcontrol_0.5.4-2.dsc 5e3a8aef6d62e4866a9583dbbd3164c35398a5a1 10008 qcontrol_0.5.4-2.debian.tar.xz Checksums-Sha256: 11dead2b25807f9f5d492be036bd94b0b48303ee6cf9b36c90d2c6c4a62f3dd3 1949 qcontrol_0.5.4-2.dsc afd6a8d93caf20e2e0142f2cbf74fd618ac4b244b16135589497f54055067788 10008 qcontrol_0.5.4-2.debian.tar.xz Files: f8bdae6968c56590b8268fe5a2eaeda9 1949 utils optional qcontrol_0.5.4-2.dsc f88c8b16c15171f70a69c0a864d3d6c9 10008 utils optional qcontrol_0.5.4-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJVU5+2AAoJECouJZ9pWkbG1FgP/0EaOagTpDe2IgQidsZtzkwM y9YIhxowJ+0KG67q/4XwuJIOK5nXdchMkEPnsQCovxZnAEhP8F5diEB2EdPV4Ile cv7B1RV+q+vEelBFpSfwPvnUZWz+1klrhgqRTRtEB7e3xHGiO64XCSByLg9FzRs/ mNX6lEYg9J4niRgvHleRR2x9ZcJX1G3U5DoUatLl4kYPRhiaO4OKYffUZ8hW2U5E mlKU9syQxvebHRCePHhqFJnEv/GaOzeka5NvrTXPJYKiRJV+ed6CObD5Dl7XIfau y/KuNWUjGykisQPegzUO5qfO0Oe2hKlizgtSSbQ6EtAiCjK/21q1AkDaL6a7fRQg +7MpC93MTwipfpMJtZsF5tfU0vcaCnaqBI2NrCys24g8jpPymtyyKD2J/BxzTZQ+ ndhZwZ2hXxFJP40e4iJit5HdtXU56L367X9bZcgVD4vqISPsllDvGAPWr9FZAi64 /jePF8+H669LgLvW2FvfrA4v8WiZWJfG5Fw30UN1ayNaDDdl6jJAKcLIey1OVp/S Dn3EkYGjUyGQgfjG7e2NlaltlFsk1yKadUOICIGvVDluLksXmL/RiraJxMV9WmJl A5htAwoRJOlqwu2C9dwwHu4fMBg/jueAg2z3yBx4EdW8FMyiBglzfc+GSjvYgOva zltuGd9EaKYSG3e/BMow =sFT2 -----END PGP SIGNATURE-----
--- End Message ---
