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 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
