Hi Alec, Quite possibly the same issue again. When the console suffers from corrupted memory it is usually just archive records from the console that are affected; loop data is usually unaffected (not sure if this is always the case though). If you do indeed have corrupted console memory then this would explain why you continue to see the RTG data updating. The RTG service uses loop data to generate its output and is thus unaffected by the corrupted memory. However, the traditional html pages are generated during the report cycle based upon archive records from the console (assuming you have record_generation = hardware in weewx.conf), your system is not receiving any archive records so data (other than date-time) in the generated reports doesn't change.
Having some sort of cron job to clear the memory is a bit of a kludge, worthwhile trying to sort out the issue, consoles should not suffer from corrupted memory on a regular basis unless something is wrong. Gary On Sunday, 16 July 2017 14:22:14 UTC+10, Alec Bennett wrote: > > My Vantage Pro2 is stuck uploading week old data again. What's odd is > that the "real time gauge" (RTG) data is working just fine, so > communication between weewx and the Davis console receiver appears to be > working. > > Unfortunately I can't be onsite to fix it for a couple of days, but any > idea what might be causing this issue? Some details: > > - Davis Vantage Pro2 > > - data is frozen at a week old > > - the fact that the rtg data is still working makes me suspect it wasn't > the reboot? > > - this is the second time this happened > > - last time I fixed it by rebooting the Davis console receiver, and > running "wee_device --clear-memory". I'm not sure which step fixed things > but everything worked again after that > > I suppose I could make a script that checks the age of the data as seen by > the generation time and then runs wee_device --clear-memory? But of course > I'd rather figure out what's causing the issue in the first place. > > > > > > > On Wed, Jun 28, 2017 at 11:03 AM Alec Bennett <[email protected] > <javascript:>> wrote: > >> Thanks for the phenomenal help, working perfectly again. For anyone else >> who comes down this path, I rebooted (pulled batteries) the Vantage Pro2 >> console and ran "wee_device --clear-memory". Not sure if that second step >> was necessary. >> >> What's odd is that the interface on the console itself was working well >> (displaying the correct data) even though the USB interface was apparently >> dead for a week. And if weewx was throwing an error, I didn't see it. The >> only symptom of the error I could find was that all the data was old. >> >> To detect this in the future I'm thinking about making a cronjob that >> checks the connection once a day and fires off an email if it's broken. >> Since wee_device returned an error when the connection was down, I'm >> thinking just a call to wee_device with no params would work to detect the >> error state. Or maybe there's a better way? Thoughts? >> >> >> >> >> On Tue, Jun 27, 2017 at 5:26 PM, gjr80 <[email protected] <javascript:>> >> wrote: >> >>> The rtgd error is known (issue 6 >>> <https://github.com/gjr80/weewx-realtime_gauge-data/issues/6>) and was >>> fixed in v0.2.13 released 7 May. I believe the issue will go away after the >>> first archive record is saved after startup. Clearly there are some other >>> issues in the log, you might want to temporarily disable rtgd by commenting >>> out user.rtgd.RealtimeGaugeData in the report_services setting under >>> [Engine] [[Services]] in weewx.conf - one less issue to muddy the >>> waters. If you are getting no data from the station then no reports will be >>> run and the old ones from 20 June will remain. Once you do get things >>> sorted I suggest you upgrade rtgd to v0.2.13. >>> >>> >>> Gary >>> >>> >>> On Wednesday, 28 June 2017 10:08:09 UTC+10, Alec Bennett wrote: >>> >>>> Oops sorry about that, should have mentioned, it's a Davis Vantage Pro2. >>>> >>>> Thanks for the troubleshooting tips. I rebooted the console since >>>> "wee_device --clear-memory" wasn't getting any response. Now I'm getting >>>> the following errors, hopefully it just needs to run for awhile? >>>> >>>> Jun 27 17:05:36 weather weewx[2079]: engine: Starting up weewx version >>>> 3.6.2 >>>> Jun 27 17:05:36 weather weewx[2079]: engine: Clock error is -0.05 >>>> seconds (positive is fast) >>>> Jun 27 17:05:36 weather weewx[2079]: engine: Starting main packet loop. >>>> Jun 27 17:05:36 weather weewx[2079]: rtgdthread: **** Traceback (most >>>> recent call last): >>>> Jun 27 17:05:36 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 882, in process_packet >>>> Jun 27 17:05:36 weather weewx[2079]: rtgdthread: **** data = >>>> self.calculate(cached_packet) >>>> Jun 27 17:05:36 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 1466, in calculate >>>> Jun 27 17:05:36 weather weewx[2079]: rtgdthread: **** fromBearing = >>>> max((self.windDirAvg-d) if ((d-self.windDirAvg) < 0 and s > 0) else None >>>> for x,y,s,d,t in self.buffer.wind_dir_list) >>>> Jun 27 17:05:36 weather weewx[2079]: rtgdthread: **** ValueError: max() >>>> arg is an empty sequence >>>> Jun 27 17:05:40 weather weewx[2079]: vantage: LOOP try #1; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jun 27 17:05:40 weather weewx[2079]: rtgdthread: **** Traceback (most >>>> recent call last): >>>> Jun 27 17:05:40 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 882, in process_packet >>>> Jun 27 17:05:40 weather weewx[2079]: rtgdthread: **** data = >>>> self.calculate(cached_packet) >>>> Jun 27 17:05:40 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 1466, in calculate >>>> Jun 27 17:05:40 weather weewx[2079]: rtgdthread: **** fromBearing = >>>> max((self.windDirAvg-d) if ((d-self.windDirAvg) < 0 and s > 0) else None >>>> for x,y,s,d,t in self.buffer.wind_dir_list) >>>> Jun 27 17:05:40 weather weewx[2079]: rtgdthread: **** ValueError: max() >>>> arg is an empty sequence >>>> Jun 27 17:05:44 weather weewx[2079]: vantage: LOOP try #2; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jun 27 17:05:44 weather weewx[2079]: rtgdthread: **** Traceback (most >>>> recent call last): >>>> Jun 27 17:05:44 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 882, in process_packet >>>> Jun 27 17:05:44 weather weewx[2079]: rtgdthread: **** data = >>>> self.calculate(cached_packet) >>>> Jun 27 17:05:44 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 1466, in calculate >>>> Jun 27 17:05:44 weather weewx[2079]: rtgdthread: **** fromBearing = >>>> max((self.windDirAvg-d) if ((d-self.windDirAvg) < 0 and s > 0) else None >>>> for x,y,s,d,t in self.buffer.wind_dir_list) >>>> Jun 27 17:05:44 weather weewx[2079]: rtgdthread: **** ValueError: max() >>>> arg is an empty sequence >>>> Jun 27 17:05:48 weather weewx[2079]: vantage: LOOP try #3; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jun 27 17:05:48 weather weewx[2079]: rtgdthread: **** Traceback (most >>>> recent call last): >>>> Jun 27 17:05:48 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 882, in process_packet >>>> Jun 27 17:05:48 weather weewx[2079]: rtgdthread: **** data = >>>> self.calculate(cached_packet) >>>> Jun 27 17:05:48 weather weewx[2079]: rtgdthread: **** File >>>> "/home/weewx/bin/user/rtgd.py", line 1466, in calculate >>>> Jun 27 17:05:48 weather weewx[2079]: rtgdthread: **** fromBearing = >>>> max((self.windDirAvg-d) if ((d-self.windDirAvg) < 0 and s > 0) else None >>>> for x,y,s,d,t in self.buffer.wind_dir_list) >>>> Jun 27 17:05:48 weather weewx[2079]: rtgdthread: **** ValueError: max() >>>> arg is an empty sequence >>>> Jun 27 17:05:52 weather weewx[2079]: vantage: LOOP try #4; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jun 27 17:05:52 weather weewx[2079]: vantage: LOOP max tries (4) >>>> exceeded. >>>> Jun 27 17:05:52 weather weewx[2079]: engine: Caught WeeWxIOError: Max >>>> tries exceeded while getting LOOP data. >>>> Jun 27 17:05:52 weather weewx[2079]: **** Waiting 60 seconds then >>>> retrying... >>>> >>>> >>>> >>>> >>>> On Tue, Jun 27, 2017 at 4:37 PM, Thomas Keffer <[email protected]> >>>> wrote: >>>> >>>>> You're giving us almost nothing to go on. No log >>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>, no >>>>> weather station type, etc. >>>>> >>>>> On the off chance you have a Vantage, did you see the section *WeeWX >>>>> generates HTML pages, but it does not update them >>>>> <http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated>* >>>>> ? >>>>> >>>>> -tk >>>>> >>>>> >>>>> >>>>> On Tue, Jun 27, 2017 at 4:16 PM, Alec Bennett <[email protected]> >>>>> wrote: >>>>> >>>>>> My weather station is still building reports, but it's stuck on the >>>>>> date June 20 (5 weeks ago). However the data in the real time gauge data >>>>>> is >>>>>> correct. >>>>>> >>>>>> I don't see anything interesting in /var/log/syslog. >>>>>> >>>>>> Any advice on how to troubleshoot this? >>>>>> >>>>>> >>>>>> -- >>>>>> 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 a topic in the >>>>> Google Groups "weewx-user" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/weewx-user/P4Rc4V4_dRU/unsubscribe. >>>>> To unsubscribe from this group and all its topics, 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 a topic in the >>> Google Groups "weewx-user" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/weewx-user/P4Rc4V4_dRU/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected] <javascript:>. >>> 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.
