unhandled exceptions on 6/13

Looks like three events were unhandled exceptions on 6/13.

They are as follows:

06/13/2015 06:45:31 mlat: Unexpected exception on connection to localhost:30005
Traceback (most recent call last):
File “/usr/lib/python3.2/asyncore.py”, line 83, in read
obj.handle_read_event()
File “/usr/lib/python3.2/asyncore.py”, line 449, in handle_read_event
self.handle_read()
File “/usr/lib/fa-mlat-client/lib/python3/dist-packages/mlat/client/receiver.py”, line 128, in handle_read
consumed, messages = self.packetize(moredata, self.last_timestamp)
_modes.ClockResetError: Out of range timestamp seen
06/13/2015 06:45:31 mlat: Lost connection to localhost:30005
06/13/2015 06:45:31 mlat: Reconnecting in 30.0 seconds
06/13/2015 06:46:01 mlat: Input connected to localhost:30005

06/13/2015 10:37:13 mlat: Unexpected exception on connection to localhost:30005
Traceback (most recent call last):
File “/usr/lib/python3.2/asyncore.py”, line 83, in read
obj.handle_read_event()
File “/usr/lib/python3.2/asyncore.py”, line 449, in handle_read_event
self.handle_read()
File “/usr/lib/fa-mlat-client/lib/python3/dist-packages/mlat/client/receiver.py”, line 128, in handle_read
consumed, messages = self.packetize(moredata, self.last_timestamp)
_modes.ClockResetError: Out of range timestamp seen
06/13/2015 10:37:13 mlat: Lost connection to localhost:30005
06/13/2015 10:37:13 mlat: Reconnecting in 30.0 seconds
06/13/2015 10:37:43 mlat: Input connected to localhost:30005

06/13/2015 19:39:22 mlat: Unexpected exception on connection to localhost:30005
Traceback (most recent call last):
File “/usr/lib/python3.2/asyncore.py”, line 83, in read
obj.handle_read_event()
File “/usr/lib/python3.2/asyncore.py”, line 449, in handle_read_event
self.handle_read()
File “/usr/lib/fa-mlat-client/lib/python3/dist-packages/mlat/client/receiver.py”, line 128, in handle_read
consumed, messages = self.packetize(moredata, self.last_timestamp)
_modes.ClockResetError: Out of range timestamp seen
06/13/2015 19:39:22 mlat: Lost connection to localhost:30005
06/13/2015 19:39:22 mlat: Reconnecting in 30.0 seconds
06/13/2015 19:39:25 275990 msgs recv’d from dump1090-mutab (194 in last 5m); 267867 msgs sent to FlightAware
06/13/2015 19:39:53 mlat: Input connected to localhost:30005
06/13/2015 19:40:15 mlat: Unexpected exception on connection to localhost:30005
Traceback (most recent call last):
File “/usr/lib/python3.2/asyncore.py”, line 83, in read
obj.handle_read_event()
File “/usr/lib/python3.2/asyncore.py”, line 449, in handle_read_event
self.handle_read()
File “/usr/lib/fa-mlat-client/lib/python3/dist-packages/mlat/client/receiver.py”, line 128, in handle_read
consumed, messages = self.packetize(moredata, self.last_timestamp)
_modes.ClockResetError: Out of range timestamp seen
06/13/2015 19:40:15 mlat: Lost connection to localhost:30005
06/13/2015 19:40:15 mlat: Reconnecting in 30.0 seconds
06/13/2015 19:40:45 mlat: Input connected to localhost:30005
06/13/2015 19:41:30 mlat: Unexpected exception on connection to localhost:30005
Traceback (most recent call last):
File “/usr/lib/python3.2/asyncore.py”, line 83, in read
obj.handle_read_event()
File “/usr/lib/python3.2/asyncore.py”, line 449, in handle_read_event
self.handle_read()
File “/usr/lib/fa-mlat-client/lib/python3/dist-packages/mlat/client/receiver.py”, line 128, in handle_read
consumed, messages = self.packetize(moredata, self.last_timestamp)
_modes.ClockResetError: Out of range timestamp seen
06/13/2015 19:41:30 mlat: Lost connection to localhost:30005
06/13/2015 19:41:30 mlat: Reconnecting in 30.0 seconds
06/13/2015 19:42:00 mlat: Input connected to localhost:30005

Mike

I’ve seen similar messages with the out of range Timestamp on 2 rpis, one running 2.0.3, the other 2.0.4.

These are purely client-side exceptions that indicate that the stream of messages received by the mlat client do not have selfconsistent timestamps and can’t be used for mlat.

What are you running on port 30005 to provide data, with what options, and if it is forwarding data from elsewhere what is it forwarding?

Thanks for the explanation!

Mike

I was forwarding for a while to virtual Radar server. It looks like when I shut that down it settles back down. Seems like it has something to do with that then.

I forget where to find the 30005 options.