On Saturday, October 8, 2016 at 9:11:21 AM UTC-4, Steve wrote: > > This is probably for Matthew? > > Before updating to 3.6.0 tonight I thought I'd do an apt-get update and > upgrade. MySQL got upgraded. While it was down WeeWX was unable to write to > it and was waiting another 2 minutes. (When I was using a Fine-Offset > WH3080 it was no hassle), but now I'm using the Interceptor driver I have > to manually restart WeeWX as it appears to completely shutdown. > > I'll post a snippet of the log, from when MySQL shutdown for a bit, until > I restarted WeeWX via /etc/init.d/weewx start (there's only a gap of 4.5 > minutes because that's when I hsppened to check the log). >
steve, i'm confused by your posting. changing from fousb to interceptor will not make any difference in how weewx interacts with the mysql database. i'm not sure what you mean by "now I'm using the Interceptor driver I have to manually restart WeeWX" - does that mean weewx is quitting unexpectedly with the interceptor driver, but it was not with fousb? if so, what are the stack traces from the log? how is this related to updating mysql? from the snippet you posted, it looks like the interceptor driver might not be closing the port on which it is listening, but its hard to tell what is happening without more log and without knowing which interceptor configuration you are using. 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.
