Re: New gpsd version with TCP reconnect

[Nick Taylor]

Yo Gary

On 01/11/2022 19:53, Gary E. Miller wrote:
> > I have run new test using the blackhole route that you suggested some
> > time ago:
> I found it even easier just to kill the socat sender.
I have tried that and as you say gpsd then recovers gracefully

root@TSB-1650:~# ps aux|grep socat
root     15461  0.0  0.1   4304  1916 pts/0    S    08:55   0:00 socat 
EXEC:gpspipe -B -r TCP-LISTEN:2948,reu
seaddr,fork
root     18470  0.2  0.1   4304  1496 pts/0    S    09:08   0:00 socat 
EXEC:gpspipe -B -r TCP-LISTEN:2948,reu
seaddr,fork
root     18537  0.0  0.1   2092  1288 pts/0    S+   09:08   0:00 grep socat
root@TSB-1650:~# kill -9 18470
root@TSB-1650:~# 2022/11/02 09:18:18 socat[21765] E write(7, 0x7f63bda8, 
50): Broken pipe

My fail case is only when I use blackhole and wait around 15 mins for 
socat to timeout. In this case gpsd doesn't seem to realise that the 
connection has failed...

root@TSB-1650:~# ip route add blackhole 192.168.2.52
root@TSB-1650:~# date
Wed Nov  2 09:22:48 UTC 2022
root@TSB-1650:~# 2022/11/02 09:40:16 socat[22339] E write(7, 0x7f63bda8, 
366): Connection timed out
date
Wed Nov  2 09:41:27 UTC 2022
root@TSB-1650:~# ip route del 192.168.2.52

I'm attaching 2 new logs of these 2 different cases

I haven't yet asked my guy for details of gcc & libc as I suspect you 
should see same fail if you replicate my test with blackhole

Best regards

Nick

gpsd-20221102-killsocat.log.xz
Description: application/xz

gpsd-20221102-blackhole.log.xz
Description: application/xz