Posts: 43
Threads: 9
Joined: May 2018
Reputation:
0
Re-installed Raspian Buster and then Openplotter settings 2.0.17. From that I installed Signalk 2.0.6
The installtion didn't so any errors, and claimed the signlk server is running on port 3000.
This isn't the case though. A simple 'sudo netstat -tlnp | grep 3000" does not show anything.
I tried re-installing signalk but still the server doesn't load at boot.
I then manually ran an installation of it, but again it would not run at boot. The server runs fine if I manually load it by typing 'signalk-server' but i really need it running from boot.
I don't know if this is a problem with OP 2.0.17 and/or Signalk 2.0.6 or even the current version of Buster, as my other sim card had slightly older versions of all the software.
Posts: 43
Threads: 9
Joined: May 2018
Reputation:
0
Thanks I'll just use that image and save the hassle.
Cheers.
Posts: 330
Threads: 5
Joined: Mar 2018
Reputation:
24
If something doesn’t work first take a look at syslog.
Also try
sudo systemctl status signalk.service
sudo systemctl status signalk.socket
Sent from my iPhone using Tapatalk
Posts: 2,853
Threads: 60
Joined: Mar 2016
Reputation:
267
2019-12-09, 03:28 PM
(This post was last modified: 2019-12-09, 03:28 PM by Sailoog.)
Some background to this issue...
Running "sudo signalk-server-setup" is the same than installing SIgnal K from the openplotter-signalk-installer app.
Signal K runs as a service. After installing you should have 2 files in /etc/systemd/system: signalk.service and signalk.socket
to start signal k run:
sudo systemctl start signalk.service
sudo systemctl start signalk.socket
and to make signal k to start at startup run:
sudo systemctl enable signalk.service
sudo systemctl enable signalk.socket
If something goes wrong you should have error entries in /var/log/syslog file
Posts: 4
Threads: 1
Joined: Jun 2019
Reputation:
0
I've got a RP3+ with OP2.0. Signal K service doesn't start.
I followed the advises above:
pi@openplotter:/etc/systemd/system $ sudo systemctl start signalk.service
pi@openplotter:/etc/systemd/system $ sudo systemctl start signalk.socket
pi@openplotter:/etc/systemd/system $ sudo systemctl enable signalk.service
pi@openplotter:/etc/systemd/system $ sudo systemctl enable signalk.socket
pi@openplotter:/etc/systemd/system $ sudo systemctl status signalk.service
* signalk.service
Loaded: loaded (/etc/systemd/system/signalk.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-01-03 11:13:22 CET; 1min 44s ago
Main PID: 1459 (code=exited, status=127)
Jan 03 11:13:22 openplotter systemd[1]: signalk.service: Service RestartSec=100ms expired, scheduling restart
Jan 03 11:13:22 openplotter systemd[1]: signalk.service: Scheduled restart job, restart counter is at 5.
Jan 03 11:13:22 openplotter systemd[1]: Stopped signalk.service.
Jan 03 11:13:22 openplotter systemd[1]: signalk.service: Start request repeated too quickly.
Jan 03 11:13:22 openplotter systemd[1]: signalk.service: Failed with result 'exit-code'.
Jan 03 11:13:22 openplotter systemd[1]: Failed to start signalk.service.
Daniel, Sailing Rocinante