nmbath - Hi Guys, I hope this is the correct ch...
Hi Guys, I hope this is the correct channel to get some support and direction. I have what might be considered a unqiue setup. I have both a 12v and 23v Lithium and Victron setup on board with separate GX devices. I am not running the large image, due to CPU loading. Instead I have a RPI5 running docker nd two docker contains. Each container has an instance of Signalk with the Victron plugin and points at the relevant GX device,. So Signalk instance listening on port 13000 is pointing at the 12v GX and 23000 pointing at the 24v GX, all over dbus. This is all happily working, most of the time. Then I have a native instance of SignalK that is pulling in data from the two docker containers and acting as my master SignalK instance with all my plugins. I have found a few issues which I am struggling to track down.
1) If. GX device reboots, the relevant SIgnalK instance does not automatically reconnect to the dBus, therefore I have to manually restart it.
2) If a SignalK instance in the docker container restarts, the native instance listening on 3000, and pulling from 13000 and 23000 does not detect the relevant signalk instance has gone, then this master/native signalk instance needs to be resated.
3) The web browsers get confused.. So if I have a browser pointing and connected to 3000, another to 13000 and another to 23000 the authentication to each individual SignalK instance gets messed up and I have to log back in. So for instance restart 13000, and have to login then 3000 and 23000 logout.
Any ideas how I can debug the faulure to reconnect and authentciation issues>
1 Reply
the three problems are separate, even if triggered by your one setup
switched to mqtt from dbus quite a while ago. i don’t recall reconnect not working with mqtt
need to check both sk connection reconnects and the browser authentication confusion, but if you copy manually the exact same security settings to all your servers there should be no confusion