Venus 3.66 and 3.73 Signalk does not work, no network service

[mokosh]

Hi,

Any help much appreciated.

I have Ekrano GX with VenusOS Large 3.66 installed. I have enabled SignalK but Node Red is disabled.

Signalk is not reachable by any URL (e.g. http://192.168.253.110:3000 or http://venus.local:3000 or by clicking openlink in the remote console).

A network port scan shows that the port 3000 is not open on the Ekrano, screenshots below show this.

I have done the following:

-Reboot ekrano after enabling signalk
-Reinstall 3.66 Normal Firmware image, then reinstall 3.66 large firmware, and then reboot.
-Install beta version 3.70~45 which has same effect, and then go back to version 3.66

I do NOT have any modification and I do not have SSH enabled to log in and check the service of signalk.

I have tried different web browser and have also cleared all history and cache of the browser.

How can I fix this please?

Many thanks,

Alex

[mokosh]

OK, so I enabled SSH to do some troubleshooting. SIgnalk seems to run but does not open a network port. I cant open the web page.

The signalk service runs:

root@ekrano:/var/log/signalk-server# tail current
@4000000068eecdc82e6d23b4 *** WARNING *** The program ‘node’ uses the Apple Bonjour compatibility layer of Avahi.
@4000000068eecdc82e7188b4 *** WARNING *** Please fix your application to use the native API of Avahi!
@4000000068eecdc82e75a764 *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
@4000000068eecdc82e772a1c *** WARNING *** The program ‘node’ called ‘DNSServiceRegister()’ which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
@4000000068eecdc82e79d99c *** WARNING *** Please fix your application to use the native API of Avahi!
@4000000068eecdc82e7ac3fc *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
@4000000068eecdc9222639c4 signalk-server running at 0.0.0.0:3000
@4000000068eecdc9222668a4
@4000000068eecdd90b79dfb4 *** starting signalk-server ***
@4000000068eecddb0c746c54 *** Starting signalk ***
root@ekrano:/var/log/signalk-server#

And shows in the process list:

root@ekrano:/var/log/signalk-server# ps | grep signalk*
819 root 1768 S supervise signalk-server
1646 root 1780 S multilog t s25000 n4 /var/log/signalk-server
3709 signalk 289m R node /usr/lib/node_modules/signalk-server/bin/signalk-server -c /data/conf/signalk
3972 root 2704 S grep signalk*
root@ekrano:/var/log/signalk-server#

Bit never opens a network port:

root@ekrano:/var/log/signalk-server# netstat -lantu
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:1881 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN
tcp 0 0 192.168.253.110:42366 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN
tcp 0 0 172.24.24.1:43109 0.0.0.0:* LISTEN
tcp 0 0 172.24.24.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 169.254.10.111:40158 0.0.0.0:* LISTEN
tcp 0 0 198.18.7.250:58447 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8883 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:48426 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:41629 127.0.0.1:52560 ESTABLISHED
tcp 0 980 192.168.253.110:22 192.168.253.100:61161 ESTABLISHED
tcp 0 0 192.168.253.110:59434 18.198.160.64:443 ESTABLISHED
tcp 0 0 192.168.253.110:49744 3.74.23.129:443 ESTABLISHED
tcp 0 0 192.168.253.110:47214 84.22.107.120:80 ESTABLISHED
tcp 0 0 127.0.0.1:60400 127.0.0.1:9001 ESTABLISHED
tcp 0 0 127.0.0.1:52560 127.0.0.1:41629 ESTABLISHED
tcp 0 0 127.0.0.1:9001 127.0.0.1:60400 ESTABLISHED
tcp 0 0 192.168.253.110:37157 172.67.74.152:443 TIME_WAIT
tcp 0 0 192.168.253.110:47242 63.176.63.169:443 ESTABLISHED
tcp 0 0 192.168.253.110:51180 44.220.111.214:443 TIME_WAIT
tcp 0 0 192.168.253.110:48414 44.220.111.60:443 TIME_WAIT
tcp 0 0 198.18.7.250:42023 104.26.12.205:443 TIME_WAIT
tcp 0 100 192.168.253.110:443 192.168.253.100:61158 ESTABLISHED
tcp 0 0 192.168.253.110:53280 44.220.111.8:443 TIME_WAIT
tcp 0 0 192.168.253.110:59434 44.220.111.102:443 TIME_WAIT
tcp 0 0 :::1883 :::* LISTEN
tcp 0 0 :::8000 :::* LISTEN
tcp 0 0 :::9001 :::* LISTEN
tcp 0 0 :::443 :::* LISTEN
tcp 0 0 :::80 :::* LISTEN
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 ::1:53 :::* LISTEN
tcp 0 0 :::8883 :::* LISTEN
tcp 0 0 ::1:59303 ::1:1883 ESTABLISHED
tcp 0 0 ::1:1883 ::1:59303 ESTABLISHED
udp 0 0 172.24.24.1:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
udp 0 0 0.0.0.0:67 0.0.0.0:*
udp 0 0 198.18.7.250:58447 0.0.0.0:*
udp 0 0 172.24.24.1:43109 0.0.0.0:*
udp 0 0 0.0.0.0:47248 0.0.0.0:*
udp 0 0 169.254.10.111:40158 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 0.0.0.0:5355 0.0.0.0:*
udp 0 0 127.0.0.1:48426 0.0.0.0:*
udp 0 0 192.168.253.110:58700 192.168.253.1:53 ESTABLISHED
udp 0 0 239.255.255.250:1900 0.0.0.0:*
udp 0 0 198.18.7.250:1900 0.0.0.0:*
udp 0 0 239.255.255.250:1900 0.0.0.0:*
udp 0 0 169.254.10.111:1900 0.0.0.0:*
udp 0 0 239.255.255.250:1900 0.0.0.0:*
udp 0 0 172.24.24.1:1900 0.0.0.0:*
udp 0 0 239.255.255.250:1900 0.0.0.0:*
udp 0 0 192.168.253.110:1900 0.0.0.0:*
udp 0 0 239.255.255.250:1900 0.0.0.0:*
udp 0 0 127.0.0.1:1900 0.0.0.0:*
udp 0 0 192.168.253.110:42366 0.0.0.0:*
udp 0 0 0.0.0.0:50050 0.0.0.0:*
udp 0 0 192.168.253.110:55261 192.168.253.1:53 ESTABLISHED
udp 0 0 ::1:53 :::*
udp 0 0 :::5353 :::*
udp 0 0 :::5355 :::*
root@ekrano:/var/log/signalk-server#

Iptables, is the firewall blocking?:

root@ekrano:/var/log/signalk-server# iptables --listChain INPUT (policy ACCEPT)target     prot opt source               destinationACCEPT     all  –  anywhere             anywherenew-conn   all  –  anywhere             anywhere             ctstate NEW

Chain FORWARD (policy ACCEPT)target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)target     prot opt source               destination

Chain new-conn (1 references)target     prot opt source               destinationACCEPT     tcp  –  anywhere             anywhere             tcp dpt:sshREJECT     tcp  –  anywhere             anywhere             tcp dpt:1883 reject-with icmp-port-unreachableREJECT     tcp  –  anywhere             anywhere             tcp dpt:9001 reject-with icmp-port-unreachableACCEPT     tcp  –  anywhere             anywhere             tcp dpt:8883root@ekrano:/var/log/signalk-server#

[mokosh]

It seems to have been a corrupt signalk install. I followed instructions here and that seems to have fixed it:

New Install - Wont Start

[mokosh]

FYI. This issue is back. After upgrading to Venus OS 3.73 on Ekrano GX SignalK is broken after rebooting.

No items were listed in the changelog wrt to updates or changes in Signalk.

[nickdb (Nick)]

How are you connecting to your cerbo? Are you using both the wifi and Ethernet port simultaneously?

[mokosh]

Hi,

My first post in thread shows how I connect to the device web browser wise.

My wifi is connected to my Raynet Wireless network. DHCP assigned addressing

My RJ45 Ethernet is connected to my boats LAN, DHCP assigned addressing

Ve.can 1 is connected to NMEA2000 using victron adapter

Ve.can2 is connected to Lynx BMS NG and solar etc

This has been working well in v 3.72, problems started today.

In fact, its behaving weirdly even now. I can reset the signalk installation using the howto in this thread and then I have reinstalled it fresh, added my plugins and then it died immediately again.

So I have removed and reinstalled venus and signalk again and made zero configurations apart from putting the boats specs in the Server settings. I will then add 1 plugin at a time to see if there is an issue there.

The plugins I use and installed are below:

[nickdb (Nick)]

There have been some network changes a little while back.
You now need to set the active internet interface so the system knows what to route through, typically the wifi adapter, it is configurable on each interface.
You can also try change the LAN gateway to 0.0.0.0 that resolved some routing issues.
Obviously, be sure to use different ranges on each, we have seen some users using the same range on both.
It sounds like a routing or binding issue not that anyone else has reported this yet, though signalk users are a small group.
There have been zero changes to signalk.

[mokosh]

Hi,

Thanks for the tip. I hadnt noticed that setting before:

Yes, am aware of running separate network segments and the resultant ip addressing requirements.

I will see how it goes turning that setting off on one interface.

Alex

[nickdb (Nick)]

That should negate the need for a 0000 gateway on the copper port but its worth a shot. Hope it helps.