Discovery "bind: address already in use" on Android in Syncthing v1.8.0

For a few days, I have experienced this problem, but only on Android devices.

I would say that this started with updating Syncthing to v1.8.0, but after I noticed the issue, I tried to downgrade to v1.7.0 and the problem was still there, so I am not sure whether there is any connection here.

I have found Local discovery multiple instances: bind already in use, and following the advice enabled STTRACE=beacon. This is how the output looks like:

2020-08-16 19:20:18 Enabled debug data for "beacon"
2020-08-16 19:20:27 recv 135 bytes from [fe80::f897:3060:a9c6:a3c%wlan0]:61760
2020-08-16 19:20:27 recv 135 bytes from [fe80::f897:3060:a9c6:a3c%wlan0]:61760
2020-08-16 19:20:27 recv 135 bytes from [fe80::f897:3060:a9c6:a3c%wlan0]:61760
2020-08-16 19:20:27 recv 135 bytes from [fe80::f897:3060:a9c6:a3c%wlan0]:61760
2020-08-16 19:20:27 recv 135 bytes from [fe80::f897:3060:a9c6:a3c%wlan0]:61760
2020-08-16 19:20:32 write udp [::]:58092->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 rmnet0
2020-08-16 19:20:32 write udp [::]:58092->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 rmnet1
2020-08-16 19:20:32 write udp [::]:58092->[ff12::8384]:21027: sendmsg: network is unreachable on write to [ff12::8384]:21027 rmnet2
2020-08-16 19:20:32 sent 340 bytes to [ff12::8384]:21027 on p2p0
2020-08-16 19:20:32 addresses: [10.0.0.255]
2020-08-16 19:20:32 sent 340 bytes to 10.0.0.255:21027
2020-08-16 19:20:32 sent 340 bytes to [ff12::8384]:21027 on wlan0
2020-08-16 19:20:32 recv 340 bytes from 10.0.0.6:49513

The rest of the log seems to basically repeat itself, but if you need more information, I can upload the whole thing.

Do you have any idea what the problem could be? What can I do to try to troubleshoot this?

I think if you use the previous version this should not be a problem.

Have you verified the error message for the previous version? Perhaps the downgrade didn’t work, as it definately should not happen on the previous version.

1 Like

You are right. I must have confused the files. I have just re-tested v1.7.0 and discovery is working correctly there.

Is this a known issue?

The error is gone in v1.9.0, so I think that we can call this one resolved :slightly_smiling_face:.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.