OpenMarine

Full Version: OpenPlotter 4 roadmap
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Old RTL-AIS service is removed, AIS Catcher service is running, and the network tab in OpenPlotter Settings includes port 8100. But http://localhost:8100 gives a "ERR_CONNECTION_REFUSED" error.
@TVR did you update of packages?
I've installed using the OpenPlotter-Settings app. Here's what I see:

[attachment=2820]
try telnet localhost on this port 8100 - no every service talks html.
@TVR As I said, please update your ais-catcher package
Code:
sudo apt update
sudo apt upgrade
(2024-04-17, 01:04 PM)BlackSea Wrote: [ -> ]@TVR As I said, please update your ais-catcher package
Code:
sudo apt update
sudo apt upgrade

Bingo! Updated ais-catcher using sudo apt upgrade, and the web page is now displayed on http://localhost:8100/.

I'm nowhere near the sea at the moment so I'm not picking up any AIS signals, but everything else appears to be working correctly now. Thanks @BlackSea for the fix.
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:
[attachment=2821]
(2024-04-17, 02:58 PM)TVR Wrote: [ -> ]
(2024-04-17, 01:04 PM)BlackSea Wrote: [ -> ]@TVR As I said, please update your ais-catcher package
Code:
sudo apt update
sudo apt upgrade

Bingo! Updated ais-catcher using sudo apt upgrade, and the web page is now displayed on http://localhost:8100/.

I'm nowhere near the sea at the moment so I'm not picking up any AIS signals, but everything else appears to be working correctly now. Thanks @BlackSea for the fix.

"Bingo" Indeed ! I did the sudo apt update and sudo apt upgrade then changed AIS settings to Port 8100. Had to put the PPM back to zero and all went green. Turned on my AIS Transmitter and.. As you say "Bingo!" .
All working. 
Thanks to all !
sudo apt upgrade
(2024-04-18, 12:45 AM)Chookfoot Wrote: [ -> ]"Bingo" Indeed ! I did the sudo apt update and sudo apt upgrade then changed AIS settings to Port 8100. Had to put the PPM back to zero and all went green. Turned on my AIS Transmitter and.. As you say "Bingo!" .
All working. 
Thanks to all !

You can keep using 10110 UDP port if you want. 8100 is the fixed TCP port for the web.

Are you getting AIS targets?
(2024-04-18, 10:00 AM)Sailoog Wrote: [ -> ]
(2024-04-18, 12:45 AM)Chookfoot Wrote: [ -> ]"Bingo" Indeed ! I did the sudo apt update and sudo apt upgrade then changed AIS settings to Port 8100. Had to put the PPM back to zero and all went green. Turned on my AIS Transmitter and.. As you say "Bingo!" .
All working. 
Thanks to all !

You can keep using 10110 UDP port if you want. 8100 is the fixed TCP port for the web.

Are you getting AIS targets?
Yes, getting targets.
Thanks
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24