STM32 branch can't restart after overrideSpeed(0)

[EeeLo]

STM32 branch can't restart motor after overrideSpeed(0), the code call end() after overrideSpeed(0). @ramboerik

[pidpawel]

Hi! We're in the middle of rewrite of the websetup protocol which will make issues like this go away entirely (and we'll still add the option to pull new configs manually I think). What's more - a simple restart of husarnet-daemon already does this pull so if that's not working there may be a deeper issue. Is websetup being added to the whitelist? Are you able to ping it?

[adamkrawczyk]

@pidpawel I'm waiting for the update - the restart of tha daemon does not affect it. the device is added to the network and visible on the dashboard but not added to the other device list. I'm abble to ping websetup

[rubenanapu]

I was also having this same problem today (on The Construct), @pidpawel and @DominikN

My problem was with Network ID 9506, if this helps.

Someone reported a problem in which ROS2 topics were not being listed.

Problem details

When I tried to replicate the problem, I installed The Construct scripts again, which added again the "robot" device on Husarnet, so there were two devices with the same name (I don't know if this is a problem. If it is a problem, I still don't know how to auto remove old devices when users are re-joining, because I don't know when they will run their scripts. We really remove old and duplicated devices automatically but only when users disconnect the rosject)

Anyway, I checked on Husarnet web (app.husarnet.com) and found the robot (actually, a computer) and the rosject's xterm listed there.

On the rosject, I ran _**husarnet status**_ and cat /etc/hosts, and everything seemed ok.

I then checked husarnet status and cat /etc/hosts on the robot (my pc, actually), and the rosject's xterm neither the master were found. On the rosject and on Husarnet web, master was correctly set as an alternative name to the robot (my pc).

Husarnet logs

When I checked the logs with journalctl -u husarnet, I found this text repeating a lot (my local time is UTC-3):

set 26 15:46:34 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:46:34 INFO     hello 1 from fc9424d5fe1cc8736484db5ecc4b3fc3
set 26 15:46:34 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:46:34 WARNING  peer fc9424d5fe1cc8736484db5ecc4b3fc3 is not on the whitelist
set 26 15:46:34 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:46:34 WARNING  peer fc9424d5fe1cc8736484db5ecc4b3fc3 is not on the whitelist

Every now and then I also saw this:

set 26 15:46:01 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:46:01 ERROR tried to serialize unexpected peer to base message type: NAT_INIT_TRANSIENT

Older logs showed this:

set 26 15:43:23 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:23 INFO     remote command: whitelist-add, arguments: fc941f7b3324da1e50d6516c5a0c8a17
set 26 15:43:23 ruben-alves-dell husarnet-daemon[16670]: 2023-09-26_15:43:23 INFO     running hooks under path /var/lib/husarnet/hook.hosttable_changed.d
set 26 15:43:23 ruben-alves-dell husarnet-daemon[16676]: 2023-09-26_15:43:23 INFO     running /var/lib/husarnet/hook.hosttable_changed.d/hosttable_changed.sh as a hook
set 26 15:43:23 ruben-alves-dell husarnet-daemon[16676]: 2023-09-26_15:43:23 INFO     running hooks under path /var/lib/husarnet/hook.rw_request.d
set 26 15:43:23 ruben-alves-dell husarnet-daemon[16680]: 2023-09-26_15:43:23 INFO     running /var/lib/husarnet/hook.rw_request.d/rw_request.sh as a hook
set 26 15:43:23 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:23 INFO     saving settings for ConfigStorage
set 26 15:43:24 ruben-alves-dell husarnet-daemon[16680]: 2023-09-26_15:43:24 INFO     running hooks under path /var/lib/husarnet/hook.rw_release.d
set 26 15:43:24 ruben-alves-dell husarnet-daemon[16687]: 2023-09-26_15:43:24 INFO     running /var/lib/husarnet/hook.rw_release.d/rw_release.sh as a hook
set 26 15:43:24 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:24 INFO     remote command: host-add, arguments: fc94:1f7b:3324:da1e:50d6:516c:5a0c:8a17 ruben-alves-dell
set 26 15:43:24 ruben-alves-dell husarnet-daemon[16687]: 2023-09-26_15:43:24 INFO     running hooks under path /var/lib/husarnet/hook.whitelist_changed.d
set 26 15:43:24 ruben-alves-dell husarnet-daemon[16694]: 2023-09-26_15:43:24 INFO     running /var/lib/husarnet/hook.whitelist_changed.d/whitelist_changed.sh as a hook
set 26 15:43:24 ruben-alves-dell husarnet-daemon[16694]: 2023-09-26_15:43:24 INFO     running hooks under path /var/lib/husarnet/hook.rw_request.d
set 26 15:43:24 ruben-alves-dell husarnet-daemon[16697]: 2023-09-26_15:43:24 INFO     running /var/lib/husarnet/hook.rw_request.d/rw_request.sh as a hook
set 26 15:43:24 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:24 INFO     saving settings for ConfigStorage
set 26 15:43:25 ruben-alves-dell husarnet-daemon[16697]: 2023-09-26_15:43:25 INFO     running hooks under path /var/lib/husarnet/hook.rw_release.d
set 26 15:43:25 ruben-alves-dell husarnet-daemon[16704]: 2023-09-26_15:43:25 INFO     running /var/lib/husarnet/hook.rw_release.d/rw_release.sh as a hook
set 26 15:43:25 ruben-alves-dell husarnet-daemon[16704]: 2023-09-26_15:43:25 INFO     running hooks under path /var/lib/husarnet/hook.rw_request.d
set 26 15:43:25 ruben-alves-dell husarnet-daemon[16709]: 2023-09-26_15:43:25 INFO     running /var/lib/husarnet/hook.rw_request.d/rw_request.sh as a hook
set 26 15:43:26 ruben-alves-dell husarnet-daemon[16709]: 2023-09-26_15:43:26 INFO     running hooks under path /var/lib/husarnet/hook.rw_release.d
set 26 15:43:26 ruben-alves-dell husarnet-daemon[16738]: 2023-09-26_15:43:26 INFO     running /var/lib/husarnet/hook.rw_release.d/rw_release.sh as a hook
set 26 15:43:26 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:26 INFO     remote command: whitelist-add, arguments: fc941f7b3324da1e50d6516c5a0c8a17
set 26 15:43:26 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:26 INFO     remote command: whitelist-add, arguments: fc941f7b3324da1e50d6516c5a0c8a17
set 26 15:43:26 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:26 INFO     remote command: host-add, arguments: fc94:1f7b:3324:da1e:50d6:516c:5a0c:8a17 ruben-alves-dell
set 26 15:43:26 ruben-alves-dell husarnet-daemon[16738]: 2023-09-26_15:43:26 INFO     running hooks under path /var/lib/husarnet/hook.hosttable_changed.d
set 26 15:43:26 ruben-alves-dell husarnet-daemon[16744]: 2023-09-26_15:43:26 INFO     running /var/lib/husarnet/hook.hosttable_changed.d/hosttable_changed.sh as a hook
set 26 15:43:26 ruben-alves-dell husarnet-daemon[16744]: 2023-09-26_15:43:26 INFO     running hooks under path /var/lib/husarnet/hook.rw_request.d
set 26 15:43:26 ruben-alves-dell husarnet-daemon[16747]: 2023-09-26_15:43:26 INFO     running /var/lib/husarnet/hook.rw_request.d/rw_request.sh as a hook
set 26 15:43:26 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:26 INFO     saving settings for ConfigStorage
set 26 15:43:27 ruben-alves-dell husarnet-daemon[16747]: 2023-09-26_15:43:27 INFO     running hooks under path /var/lib/husarnet/hook.rw_release.d
set 26 15:43:27 ruben-alves-dell husarnet-daemon[16755]: 2023-09-26_15:43:27 INFO     running /var/lib/husarnet/hook.rw_release.d/rw_release.sh as a hook
set 26 15:43:27 ruben-alves-dell husarnet-daemon[16755]: 2023-09-26_15:43:27 INFO     running hooks under path /var/lib/husarnet/hook.rw_request.d
set 26 15:43:27 ruben-alves-dell husarnet-daemon[16760]: 2023-09-26_15:43:27 INFO     running /var/lib/husarnet/hook.rw_request.d/rw_request.sh as a hook
set 26 15:43:28 ruben-alves-dell husarnet-daemon[16760]: 2023-09-26_15:43:28 INFO     running hooks under path /var/lib/husarnet/hook.rw_release.d
set 26 15:43:28 ruben-alves-dell husarnet-daemon[16789]: 2023-09-26_15:43:28 INFO     running /var/lib/husarnet/hook.rw_release.d/rw_release.sh as a hook
set 26 15:43:28 ruben-alves-dell husarnet-daemon[11320]: 2023-09-26_15:43:28 INFO     hello 1 from fc9424d5fe1cc8736484db5ecc4b3fc3

After I disconnected from the robot on the rosject, and reconnected again, it worked. But the main reason I put it here is that sometimes people don't know that reconnecting sometimes solves the issue, and I'm not sure how to automatically detect this issue.