ntpq parser error: nextvar: no closing quote, stop: 'filtdelay=HR++ 3"��� 0.00 0.00 0.00 0.00 0.00 0.'
There is an issue probably with encoding the data since the data that is associated with the filtdelay
field appears to be binary gibberish and not a list of characters representing a couple of floating points. To analyse it a bit further, I captured the data coming from the ntp server using wireshark and the gibberish is already in the UDP data. So it appears to be related to the server side and not so much the python client. ntpq.pcapng
Looking a bit further on the data it appears that the filtoffset
member also contains binary gibberish at the start of the value. So we might be looking at something related to encoding list of floats in general.
The parser error does not always happen, it depends on what exact binary data is in the gibberish. Sometimes there is a "
character there or a ,
which makes parsing an issue. When that is not the case the values are mostly ignored by ntpq. That does not make it right though.