Package: qcontrol
Version: 0.5.5-2
Severity: normal
Dear Maintainer, qcontrol.service failing to start on QNAP TS-412
Situtation is somewhat similar to earlier bug #781866.
But in contrast with previous bug manual restart via
systemctl restart qcontrol.service qcontrold.service
does not help: status of qcontrol.service is still failed.
But after manual restart Status led became green while it was flashing
red/green immediately after boot.
Below if output of `journalctl |grep qcontrol`:
Aug 08 12:56:20 puck qcontrol[552]: System boot completed.
Aug 08 12:56:20 puck qcontrol[552]: Error connecting to socket: No such
file or directory
Aug 08 12:56:20 puck systemd[1]: qcontrol.service: Control process
exited, code=exited status=255
Aug 08 12:56:21 puck systemd[1]: qcontrol.service: Unit entered failed
state.
Aug 08 12:56:21 puck systemd[1]: qcontrol.service: Failed with result
'exit-code'.
Aug 08 13:18:53 puck qcontrol[1365]: System boot completed.
Aug 08 13:18:53 puck qcontrol[1365]: Error connecting to socket: No
such file or directory
Aug 08 13:18:53 puck systemd[1]: qcontrol.service: Control process
exited, code=exited status=255
Aug 08 13:18:53 puck systemd[1]: qcontrol.service: Unit entered failed
state.
Aug 08 13:18:53 puck systemd[1]: qcontrol.service: Failed with result
'exit-code'.
Aug 08 13:24:11 puck systemd[1]: Starting LSB: Start qcontrol daemon...
Aug 08 13:24:11 puck qcontrol[1405]: System boot completed.
Aug 08 13:24:11 puck qcontrol[1405]: Error connecting to socket: No
such file or directory
Aug 08 13:24:11 puck systemd[1]: qcontrol.service: Control process
exited, code=exited status=255
Aug 08 13:24:11 puck systemd[1]: qcontrol.service: Unit entered failed
state.
Aug 08 13:24:11 puck systemd[1]: qcontrol.service: Failed with result
'exit-code'.
Aug 08 13:24:11 puck qcontrold[1406]: Starting qcontrol daemon:
qcontrol.
Aug 08 13:24:11 puck systemd[1]: Started LSB: Start qcontrol daemon.
Aug 08 13:24:11 puck qcontrol[1419]: qcontrol 0.5.5 daemon starting.
Aug 08 13:24:11 puck qcontrol[1419]: Register evdev on
/dev/input/by-path/platform-gpio_keys-event
Aug 08 13:24:11 puck qcontrol[1419]: ts41x:
/sys/class/gpio/gpio45/value does not exist, trying to enable
Aug 08 13:24:11 puck qcontrol[1419]: ts41x: unable to open gpio control
file
Aug 08 13:24:11 puck qcontrol[1419]: confdir: loading from
/etc/qcontrol.d...
Aug 08 13:24:13 puck qcontrol[1419]: ts41x: temperature 45
Aug 08 13:24:13 puck qcontrol[1419]: ts41x: temperature 45 setting fan
to "high"
Aug 08 13:24:18 puck qcontrol[1419]: ts41x: temperature 44 setting fan
to "medium"
Aug 08 13:29:13 puck qcontrol[1419]: ts41x: temperature 42
Aug 08 13:39:13 puck qcontrol[1419]: ts41x: temperature 40
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 4.9.0-3-marvell
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages qcontrol depends on:
ii libc6 2.24-11+deb9u1
ii liblua5.1-0 5.1.5-8.1+b2
ii udev 232-25+deb9u1
qcontrol recommends no packages.
qcontrol suggests no packages.
-- no debconf information
