2024-04-17, 06:06 PM
(This post was last modified: 2024-04-17, 06:25 PM by Herz_aus_Stahl.)
hi,
two days ago signalk just stopped working after days without any problem. If I start it, it starts shortly, then stops and I get this:
pi@openplotter:~ $ sudo service signalk status
● signalk.service
Loaded: loaded (/etc/systemd/system/signalk.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-04-17 17:59:58 BST; 1s ago
TriggeredBy: × signalk.socket
Main PID: 7060 (signalk-server)
Tasks: 8 (limit: 9248)
CPU: 1.979s
CGroup: /system.slice/signalk.service
├─7060 /bin/sh /home/pi/.signalk/signalk-server
└─7063 node /usr/lib/node_modules/signalk-server/bin/signalk-server -c /home/pi/.signalk
Apr 17 17:59:58 openplotter systemd[1]: Started signalk.service.
pi@openplotter:~ $ sudo service signalk status
× signalk.service
Loaded: loaded (/etc/systemd/system/signalk.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-04-17 18:00:04 BST; 7s ago
Duration: 1.339s
TriggeredBy: × signalk.socket
Process: 7103 ExecStart=/home/pi/.signalk/signalk-server (code=exited, status=1/FAILURE)
Main PID: 7103 (code=exited, status=1/FAILURE)
CPU: 1.988s
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Consumed 1.988s CPU time.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Scheduled restart job, restart counter is at 5.
Apr 17 18:00:04 openplotter systemd[1]: Stopped signalk.service.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Consumed 1.988s CPU time.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Start request repeated too quickly.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Failed with result 'exit-code'.
Apr 17 18:00:04 openplotter systemd[1]: Failed to start signalk.service.
pi@openplotter:~ $
I can't say for sure if that happend after an upgrade, but I guess it.
I just made sudo apt update and upgrade.
I already tried reinstalling signalk but didn't help
It is a raspi5 with openpleotter 4, Pican-m hat and an SSD.
can anyone help me?
EDIT:
two days ago signalk just stopped working after days without any problem. If I start it, it starts shortly, then stops and I get this:
pi@openplotter:~ $ sudo service signalk status
● signalk.service
Loaded: loaded (/etc/systemd/system/signalk.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-04-17 17:59:58 BST; 1s ago
TriggeredBy: × signalk.socket
Main PID: 7060 (signalk-server)
Tasks: 8 (limit: 9248)
CPU: 1.979s
CGroup: /system.slice/signalk.service
├─7060 /bin/sh /home/pi/.signalk/signalk-server
└─7063 node /usr/lib/node_modules/signalk-server/bin/signalk-server -c /home/pi/.signalk
Apr 17 17:59:58 openplotter systemd[1]: Started signalk.service.
pi@openplotter:~ $ sudo service signalk status
× signalk.service
Loaded: loaded (/etc/systemd/system/signalk.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-04-17 18:00:04 BST; 7s ago
Duration: 1.339s
TriggeredBy: × signalk.socket
Process: 7103 ExecStart=/home/pi/.signalk/signalk-server (code=exited, status=1/FAILURE)
Main PID: 7103 (code=exited, status=1/FAILURE)
CPU: 1.988s
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Consumed 1.988s CPU time.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Scheduled restart job, restart counter is at 5.
Apr 17 18:00:04 openplotter systemd[1]: Stopped signalk.service.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Consumed 1.988s CPU time.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Start request repeated too quickly.
Apr 17 18:00:04 openplotter systemd[1]: signalk.service: Failed with result 'exit-code'.
Apr 17 18:00:04 openplotter systemd[1]: Failed to start signalk.service.
pi@openplotter:~ $
I can't say for sure if that happend after an upgrade, but I guess it.
I just made sudo apt update and upgrade.
I already tried reinstalling signalk but didn't help
It is a raspi5 with openpleotter 4, Pican-m hat and an SSD.
can anyone help me?
EDIT: