running gecko service is killed #5
Comments
|
Hi Thomas, |
|
Hi, I use this as first line:
|
|
Try it in the gecko.service file |
|
i changed as written by you without any change `pi@raspberrypi-iob:/opt/geckoclient/service $ sudo systemctl start gecko.service Jan 15 18:18:29 raspberrypi-iob systemd[1]: gecko.service: Service RestartSec=100ms expired, scheduling restart. |
|
should light and pump1 switch to on while start client.py? `pi@raspberrypi-iob:/opt/geckoclient $ python3.10 client.py
` |
|
after update to lates version 0.5.3 I had these issues: `pi@raspberrypi-iob:/opt/geckoclient $ python3.10 client.py
Additionally there was a gecko_client.log in dirctory og opt/geckoclient
But still no logs in /var/log But issue are not related by time |
|
Ediditing of gecko.service under /etc/systemd/system/gecko.service about `pi@raspberrypi-iob:/etc/systemd/system $ sudo systemctl start gecko.service Jan 16 16:39:01 raspberrypi-iob systemd[1]: gecko.service: Service RestartSec=100ms expired, scheduling restart. |
|
Hi, Find the log in the folder where geckolclient is placed can be normal as it is the fallback location in the case the configured on (in your case /var/log) is not writable. That can happen when you run the with your account and not with the system account. For the service startup, exit code 203 can point to a not existing or not executable binary. See https://unix.stackexchange.com/questions/472950/systemd-status-203-exec-error-when-creating-new-service for example. |
|
Hi again :-) "light and pumps should not be switched on when the client is started. Maybe some leftover commands in MQTT?" this is every thing i start client.py I changed to correct path:
In gecko.service: -rw-rw-r-- 1 root root 203 Jan 17 12:11 gecko.service Directory listing pi@raspberrypi-iob:/opt/geckoclient $ ls -la Then only minor updates about python path and status of crash while trying to start service: `pi@raspberrypi-iob:/etc/systemd/system $ sudo systemctl enable gecko.service Jan 18 10:41:23 raspberrypi-iob systemd[1]: gecko.service: Service RestartSec=100ms expired, scheduling restart. |
|
this occured after startes client.py manualy: `pi@raspberrypi-iob:/opt/geckoclient $ ./client.py
This is in Log:
|
|
here is some more information, hope so: `pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl status gecko.service Jan 18 11:07:14 raspberrypi-iob systemd[1]: gecko.service: Service RestartSec=100ms expired, scheduling restart. pi@raspberrypi-iob:/opt/geckoclient $ journalctl _PID=1024 |
|
it is running now permanently :-) pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl status gecko.service But: then i can not use the app to control spa. No data is shown there |
|
Hi, |
|
Hi, yeah step by step :-) I am using offical geck app "in touch 2" to control spa with remote functions. Screen while gecko service running:
Screen without runing gecko service running
I have no blower too. Only Pump 1&2 and circulation pump with light(s) Soon with "in mix 300" modul to control color and brightness more comfortable. Do you know if it is supported from software? To control device I will use my iobroker system. fhem is running to on same raspi. there will be some ttp223 sensors connected to esp with tasmota to send manual done sensor switch to my mqtt server to. S I can control Spa from many points in Spa :-) |
|
Dear Thomas, |
After a long way i got correct os/config to run your code :-)
while i got no updates in mytt server i checked status of service. it was killed meanwhile:
`pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl start gecko.service
pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl status gecko.service
● gecko.service - Gecko client service
Loaded: loaded (/etc/systemd/system/gecko.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-01-13 12:31:20 CET; 135ms ago
Main PID: 9516 (python3)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/gecko.service
└─9516 /usr/bin/python3 /opt/geckoclient/client.py
Jan 13 12:31:20 raspberrypi-iob systemd[1]: Started Gecko client service.
pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl status gecko.service
● gecko.service - Gecko client service
Loaded: loaded (/etc/systemd/system/gecko.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-01-13 12:31:21 CET; 9min ago
Process: 9520 ExecStart=/usr/bin/python3 /opt/geckoclient/client.py (code=exited, status=1/FAILURE)
Main PID: 9520 (code=exited, status=1/FAILURE)
Jan 13 12:31:21 raspberrypi-iob systemd[1]: gecko.service: Service RestartSec=100ms expired, scheduling restart.
Jan 13 12:31:21 raspberrypi-iob systemd[1]: gecko.service: Scheduled restart job, restart counter is at 5.
Jan 13 12:31:21 raspberrypi-iob systemd[1]: Stopped Gecko client service.
Jan 13 12:31:21 raspberrypi-iob systemd[1]: gecko.service: Start request repeated too quickly.
Jan 13 12:31:21 raspberrypi-iob systemd[1]: gecko.service: Failed with result 'exit-code'.
Jan 13 12:31:21 raspberrypi-iob systemd[1]: Failed to start Gecko client service.
pi@raspberrypi-iob:/opt/geckoclient $
`
I still have no geckoclient log where i could have a look. Debuglevel was changed to "DEBUG" too.
Services:
`pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl stop gecko.service
pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl start gecko.service
pi@raspberrypi-iob:/opt/geckoclient $ sudo systemctl status gecko.service
● gecko.service - Gecko client service
Loaded: loaded (/etc/systemd/system/gecko.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-01-13 12:48:21 CET; 4s ago
Process: 11607 ExecStart=/usr/bin/python3 /opt/geckoclient/client.py (code=exited, status=1/FAILURE)
Main PID: 11607 (code=exited, status=1/FAILURE)
Jan 13 12:48:21 raspberrypi-iob systemd[1]: gecko.service: Service RestartSec=100ms expired, scheduling restart.
Jan 13 12:48:21 raspberrypi-iob systemd[1]: gecko.service: Scheduled restart job, restart counter is at 5.
Jan 13 12:48:21 raspberrypi-iob systemd[1]: Stopped Gecko client service.
Jan 13 12:48:21 raspberrypi-iob systemd[1]: gecko.service: Start request repeated too quickly.
Jan 13 12:48:21 raspberrypi-iob systemd[1]: gecko.service: Failed with result 'exit-code'.
Jan 13 12:48:21 raspberrypi-iob systemd[1]: Failed to start Gecko client service.
pi@raspberrypi-iob:/opt/geckoclient $ python3.10 client.py
`
The text was updated successfully, but these errors were encountered: