Re: New gpsd version with TCP reconnect

[Gary E. Miller]

Yo Nick!

On Thu, 10 Nov 2022 14:21:10 +0000
Nick Taylor <nicktaylor@dataskill.uk> wrote:

> Sadly doesn't seem to have made much difference to me...
> New log attached

gpsd:INFO: Command line: gpsd -nND 10 tcp://192.168.2.53:2948 

-D4 or -D5 is enough, we don't need the nitty gritty cahar by char
decoding.  Message level is good enough.  We get messages, or not.

I see you have a client connected, you never mentioned that:

gpsd:SPIN: client ::1 (0) connect on fd 8
gpsd:CLIENT: => client(0) len 113: 
{"class":"VERSION","release":"3.24.1~dev","rev":"release-3.24-293-ge07d8343f","proto_major":3,"proto_minor":15}

You only waited 119 seeconds for disconnect to be detected:

gpsd:DATA: gpsd_multipoll(7) = 0
gpsd:PROG: gpsd_multipoll(7) DEVICE_UNCHANGED for 119

Then you stopped the log there.  When and how, did you reenable the
connection between the client and server?

The TCP connection will hang around for 2 hours.  I blocked the conenction
this way, on the client host, hof 819 seconds:

# iptables -A INPUT -p tcp --source-port 2948  -j DROP

When I reentabled the connection, this way:

# iptables -D INPUT -p tcp --source-port 2948  -j DROP

The tcp:// picked right up and worked:

So I'm having trouble duplicating your issue.  Are you looking for gpsd
to  force a disconnect at like 60 seconds or 120 seconds?

Why does my TCP session stay up 800+ seconds, but yours does not?

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpEguEfKjYBP.pgp
Description: OpenPGP digital signature