Barton I suspect you are correct. All those "Unused index" comments suggest nothing is getting logged. However, it is worth trying to reseat the logger before concluding it's bad.
You can certainly set record_generation to software to bypass the logger. That should work. However, it doesn't prove that there's anything wrong with the logger. The best proof is all those "Unused index" comments. The actual insert statement is in class Manager, function _addSingleRecord <https://github.com/weewx/weewx/blob/master/bin/weewx/manager.py#L278>. You're not going to find it by searching for the table name ('archive'), because that is a settable parameter, which gets plugged in at runtime. And, Fran, if you're still having problems, start a new thread rather than hijack this one. Too confusing to follow otherwise. -tk On Mon, Dec 12, 2016 at 10:56 AM, Barton Phillips <[email protected]> wrote: > I am starting to think that the data-logger module has gone bad. I have > placed a couple of debug statements into the python code using > syslog.syslog() functions and I don't see any information from the logger. > I am not sure that the debug statements are in the right places but I think > so. I placed one in the genLoggerSumary() function and then ran 'wee_device > --logger-summary=file'. All I got were 'None' records. It looks like the > data-logger isn't working. > > Can I set the config file to use 'software' and use the raw data that is > displayed when I run 'weewxd' standalone. I see that every 2 seconds the > entire dataset is displayed. The timestamps are correct and the data looks > realistic. > > If I can prove that the data-logger is bad I will order another one from > Davis, I just want to make sure. Where would I put a debug statement in the > 'weewxd' code to look at the return from the data-logger. > > Also I still would like to understand how the 'archive' database is > updated. I just don't see 'INSERT' or 'REPLACE' statements with %s being > 'archive'. All of the 'REPLACE' statements have %s_day_... > > Really need help. > > On Saturday, December 10, 2016 at 8:48:52 AM UTC-8, Barton Phillips wrote: > >> I may not have posted this right the first time so here goes again. >> >> My weather station has been working for years but a couple of days ago >> it started to freeze after running several hours. When I looked at the >> database the last entry was not updating. I was running 3.1.2 so I upgraded >> to 3.6.2 but the same thing happens. I tried changing from sqlite to mysql >> but still no help. What can I do to debug this problem? Do you think it >> might be something wrong with the console? When I do 'wee_device >> --clear-memory' it starts working again but within a day it freezes. The >> 'Weewx >> uptime: ' changes every 5 minutes so I know that the files are being >> updated but the image times don't change and the date and time at the top >> is frozen. >> Any help would be appreciated. >> >> When I run weewxd from the command line I see the dateTime updating every >> 2 seconds but if I look at the logfile the "Getting archive packets since >> 2016-12-09 09:15:00 PST (1481303700)" does not change. In this case it is >> stuck at 09:15:00 PST. >> >> I can't think of anything I might have done to cause the change from >> running OK to freeze. >> >> -- >> Sent From my Good Old Desktop PC. >> >> Barton Phillips >> Granby Rotary Club >> http://www.granbyrotary.org >> Applitec Inc. >> http://www.applitec.com >> Personal >> http://www.bartonphillips.com >> > -- > 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. > -- 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.
