Sorry, negative on both counts. I've looked back in the syslog files and I cannot see any problems with the parsing of the interceptor data, or any sign of the value 645138 or 667872. The weewx.sdb file is full of numbers or null. The other thing i can mention is that a restart of weewx did not clear the problem, it needed a sudo reboot to get back to normal.
Mike On Sunday, 28 April 2019 12:26:02 UTC+1, mwall wrote: > > On Sunday, April 28, 2019 at 2:29:41 AM UTC-4, Redanman wrote: >> >> I had Debug=1 when it crashed. I've gone back into the syslog archives >> and pulled out the section starting roughly 5 minutes before the last >> crash. At that point everything seems to be running fine. See attached. >> > > i do not see the value 645138 anywhere in that log snippet. could you see > if it is anywhere in the log prior to the exception you posted at the > beginning of this discussion? > > we're looking for it in one of the 'raw packet' lines > > also, you might want to query your database to see if there are any > strings in there. if you find one, then the timestamp of the record with > the string should give you some idea of when in the logs to look > > m > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
