@bnealon
I have made a few changes. Can this deb file be installed without errors?
@Paulchen-Panther thanks very much for the build, doesnt seem to have changed much sadly :o(
I made a fresh install of Raspbian Buster, then SSH'd in from another machine as the default user 'Pi' and this was the first thing i did after that:
Heres my download and install output:
Code
pi@raspberrypi:~/Hyperion.ng/03.08.19 $ wget -qN https://github.com/Paulchen-Panther/hyperion.ng/raw/systemctl/Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
pi@raspberrypi:~/Hyperion.ng/03.08.19 $ ls
Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
pi@raspberrypi:~/Hyperion.ng/03.08.19 $ dpkg -i Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
dpkg: error: requested operation requires superuser privilege
pi@raspberrypi:~/Hyperion.ng/03.08.19 $ sudo dpkg -i Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
Selecting previously unselected package hyperion.ng-rpi.
(Reading database ... 91802 files and directories currently installed.)
Preparing to unpack Hyperion.NG-Beta.1.0.0-Linux-rpi.deb ...
/var/lib/dpkg/tmp.ci/preinst: 1: /var/lib/dpkg/tmp.ci/preinst: #!/bin/sh: not found
---Hyperion ambient light preinst ---
Unpacking hyperion.ng-rpi (1.0.0) ...
dpkg: dependency problems prevent configuration of hyperion.ng-rpi:
hyperion.ng-rpi depends on libqt5serialport5 (>= 5.5.0); however:
Package libqt5serialport5 is not installed.
hyperion.ng-rpi depends on libavahi-compat-libdnssd1 (>= 0.6.31); however:
Package libavahi-compat-libdnssd1 is not installed.
hyperion.ng-rpi depends on libpython3.5; however:
Package libpython3.5 is not installed.
dpkg: error processing package hyperion.ng-rpi (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
hyperion.ng-rpi
pi@raspberrypi:~/Hyperion.ng/03.08.19 $ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following package was automatically installed and is no longer required:
rpi.gpio-common
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
libavahi-compat-libdnssd1 libpython3.5 libpython3.5-minimal libpython3.5-stdlib libqt5serialport5
The following NEW packages will be installed:
libavahi-compat-libdnssd1 libpython3.5 libpython3.5-minimal libpython3.5-stdlib libqt5serialport5
0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 3,905 kB of archives.
After this operation, 17.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://raspbian.raspberrypi.org/raspbian buster/main armhf libqt5serialport5 armhf 5.11.3-2 [31.2 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian buster/main armhf libavahi-compat-libdnssd1 armhf 0.7-4+b1 [46.4 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython3.5-minimal armhf 3.5.4-4 [572 kB]
Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython3.5-stdlib armhf 3.5.4-4 [2,095 kB]
Get:5 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython3.5 armhf 3.5.4-4 [1,160 kB]
Fetched 3,905 kB in 1s (3,652 kB/s)
Selecting previously unselected package libqt5serialport5:armhf.
(Reading database ... 91826 files and directories currently installed.)
Preparing to unpack .../libqt5serialport5_5.11.3-2_armhf.deb ...
Unpacking libqt5serialport5:armhf (5.11.3-2) ...
Selecting previously unselected package libavahi-compat-libdnssd1:armhf.
Preparing to unpack .../libavahi-compat-libdnssd1_0.7-4+b1_armhf.deb ...
Unpacking libavahi-compat-libdnssd1:armhf (0.7-4+b1) ...
Selecting previously unselected package libpython3.5-minimal:armhf.
Preparing to unpack .../libpython3.5-minimal_3.5.4-4_armhf.deb ...
Unpacking libpython3.5-minimal:armhf (3.5.4-4) ...
Selecting previously unselected package libpython3.5-stdlib:armhf.
Preparing to unpack .../libpython3.5-stdlib_3.5.4-4_armhf.deb ...
Unpacking libpython3.5-stdlib:armhf (3.5.4-4) ...
Selecting previously unselected package libpython3.5:armhf.
Preparing to unpack .../libpython3.5_3.5.4-4_armhf.deb ...
Unpacking libpython3.5:armhf (3.5.4-4) ...
Setting up libqt5serialport5:armhf (5.11.3-2) ...
Setting up libavahi-compat-libdnssd1:armhf (0.7-4+b1) ...
Setting up libpython3.5-minimal:armhf (3.5.4-4) ...
Setting up libpython3.5-stdlib:armhf (3.5.4-4) ...
Setting up libpython3.5:armhf (3.5.4-4) ...
Setting up hyperion.ng-rpi (1.0.0) ...
---Hyperion ambient light postinstall ---
---> init deamon: systemd
Invalid unit name "hyperiond@pi
pi
pi.service" was escaped as "hyperiond@pi\x0api\x0api.service" (maybe you should use systemd-escape?)
Created symlink /etc/systemd/system/multi-user.target.wants/hyperiond@pi\x0api\x0api.service → /etc/systemd/system/hyperiond@.service.
Invalid unit name "hyperiond@pi
pi
pi" was escaped as "hyperiond@pi\x0api\x0api" (maybe you should use systemd-escape?)
Failed to start hyperiond@pi\x0api\x0api.service: Unit hyperiond@pi\x0api\x0api.service has a bad unit file setting.
See system logs and 'systemctl status hyperiond@pi\x0api\x0api.service' for details.
---> Install Hyperion desktop icons
---> Raspberry Pi found, but SPI is not set, we write "dtparam=spi=on" to /boot/config.txt
--> systemctl start hyperiond for user pi pi pi
-----------------------------------------------------------------------------
---> Hyperion has been installed/updated!
--->
---> Hyperion has been installed as service, it will start on each system startup
---> For configuration, visit with your browser: 192.168.0.6:8090
---> or if already used by another service try: 192.168.0.6:8091
Please reboot your Raspberry Pi, we inserted dtparam=spi=on to /boot/config.txt
-----------------------------------------------------------------------------
Webpage: www.hyperion-project.org
Wiki: wiki.hyperion-project.org
Forum: forum.hyperion-project.org
-----------------------------------------------------------------------------
Processing triggers for libc-bin (2.28-10+rpi1) ...
pi@raspberrypi:~/Hyperion.ng/03.08.19 $ systemctl status hyperiond@pi\x0api\x0api.service
● hyperiond@pix0apix0api.service - Hyperion ambient light systemd service for user pix0apix0api
Loaded: loaded (/etc/systemd/system/hyperiond@.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Alles anzeigen
I then restarted the service, and here's the logs. It appears to keep cycling the service due to a failure for user `pix0apix0api`, is this user correct?
Code
Aug 03 20:43:36 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Main process exited, code=exited, status=217/USER
Aug 03 20:43:36 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Failed with result 'exit-code'.
Aug 03 20:43:38 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Service RestartSec=2s expired, scheduling restart.
Aug 03 20:43:38 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Scheduled restart job, restart counter is at 35.
Aug 03 20:43:38 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:38 raspberrypi systemd[1]: Started Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:38 raspberrypi systemd[1123]: hyperiond@pix0apix0api.service: Failed to determine user credentials: No such process
Aug 03 20:43:38 raspberrypi systemd[1123]: hyperiond@pix0apix0api.service: Failed at step USER spawning /usr/bin/hyperiond: No such process
Aug 03 20:43:38 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Main process exited, code=exited, status=217/USER
Aug 03 20:43:38 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Failed with result 'exit-code'.
Aug 03 20:43:41 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Service RestartSec=2s expired, scheduling restart.
Aug 03 20:43:41 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Scheduled restart job, restart counter is at 36.
Aug 03 20:43:41 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:41 raspberrypi systemd[1]: Started Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:41 raspberrypi systemd[1124]: hyperiond@pix0apix0api.service: Failed to determine user credentials: No such process
Aug 03 20:43:41 raspberrypi systemd[1124]: hyperiond@pix0apix0api.service: Failed at step USER spawning /usr/bin/hyperiond: No such process
Aug 03 20:43:41 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Main process exited, code=exited, status=217/USER
Aug 03 20:43:41 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Failed with result 'exit-code'.
Aug 03 20:43:43 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Service RestartSec=2s expired, scheduling restart.
Aug 03 20:43:43 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Scheduled restart job, restart counter is at 37.
Aug 03 20:43:43 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:43 raspberrypi systemd[1]: Started Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:43 raspberrypi systemd[1125]: hyperiond@pix0apix0api.service: Failed to determine user credentials: No such process
Aug 03 20:43:43 raspberrypi systemd[1125]: hyperiond@pix0apix0api.service: Failed at step USER spawning /usr/bin/hyperiond: No such process
Aug 03 20:43:43 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Main process exited, code=exited, status=217/USER
Aug 03 20:43:43 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Failed with result 'exit-code'.
Aug 03 20:43:45 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Service RestartSec=2s expired, scheduling restart.
Aug 03 20:43:45 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Scheduled restart job, restart counter is at 38.
Aug 03 20:43:45 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:45 raspberrypi systemd[1]: Started Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:45 raspberrypi systemd[1126]: hyperiond@pix0apix0api.service: Failed to determine user credentials: No such process
Aug 03 20:43:45 raspberrypi systemd[1126]: hyperiond@pix0apix0api.service: Failed at step USER spawning /usr/bin/hyperiond: No such process
Aug 03 20:43:45 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Main process exited, code=exited, status=217/USER
Aug 03 20:43:45 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Failed with result 'exit-code'.
Aug 03 20:43:47 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Service RestartSec=2s expired, scheduling restart.
Aug 03 20:43:47 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Scheduled restart job, restart counter is at 39.
Aug 03 20:43:47 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:47 raspberrypi systemd[1]: Started Hyperion ambient light systemd service for user pix0apix0api.
Aug 03 20:43:47 raspberrypi systemd[1127]: hyperiond@pix0apix0api.service: Failed to determine user credentials: No such process
Aug 03 20:43:47 raspberrypi systemd[1127]: hyperiond@pix0apix0api.service: Failed at step USER spawning /usr/bin/hyperiond: No such process
Aug 03 20:43:47 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Main process exited, code=exited, status=217/USER
Aug 03 20:43:47 raspberrypi systemd[1]: hyperiond@pix0apix0api.service: Failed with result 'exit-code'.
Alles anzeigen
Cheers!