Replies: 1 comment
-
To clarify this, the exporter is not running on the rpi4, right? I would investigate why power switching the rpi also seems to kill the network connection to your server. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My hardware setup:
[Raspi <----tty console ---->(/dev/ttyUSB0 at server running exporter and coordinator) <---dev laptop--->]
System setup:
I have ser2net service running - which maps the local /dev/ttyUSB0 to tcp port 20410 - my exporter configuration has NetworkSerialPort exported at port 20410, host: , speed: 115200. This resource is added to place rpi_4. From laptop, I can use labgrid-client console command which gets me into the Raspi (so, it is working as expected). Now, in my use case, I am planning to upgrade the device with sysupgrade (which reboots the Raspi). So, in this case, if I reboot the Raspi, I get the error:
Error:
Coordinator:
I have the journalctl -u labgrid-coordinator.service -f (which outputs nothing)
Exporter:
Is there any way I can fix it? Or I just always restart coordinator, exporter every time my Raspi gets rebooted after sysupgrade?
Thank you :)
Beta Was this translation helpful? Give feedback.
All reactions