I'm sorry, but I didn't understand in which way the clock is related to this problem
Il giorno giovedì 17 ottobre 2019 13:59:09 UTC+2, Andrew Milner ha scritto: > > regardless I would recommend that all Rpis controlling weather stations > have an RTC installed to avoid temporal issues as much as possible. > > > > On Thursday, 17 October 2019 14:26:18 UTC+3, Andrea Cecilia wrote: >> >> I've never seen this section of the User's Guide (it might be relatively >> new), but it is exactly about the problem we are discussing here. >> So, the fixing tries they suggest without data loss are two: >> 1) unplug and reboot the console by removing current and batteries for >> about 2 minutes and then plug it again; >> 2) make a /home/weewx/bin/wee_device --dump. >> They also specificate that if these won't work, it is necessary to give a >> --clera-memory as I did, but in this case you lose the data. >> >> As it is suggested in other answers here, it would "fix" the problem >> buying an UPS, but I honestly wolud find a software solution, not coming >> around the problem in this way (which could also be expensive). >> >> So, it remains to try the 2 points up here when the problem will come out >> again. Did anyone try? >> >> >> Il giorno mercoledì 16 ottobre 2019 13:40:59 UTC+2, Thomas Keffer ha >> scritto: >>> >>> This is likely a case of memory corruption, brought on by time not being >>> synced during the reboot, due to the lack of an on-board clock. It was not >>> a problem with Weatherlink because you were not running it on an RPi. >>> >>> See the section *WeeWX generated HTML pages, but does not update them >>> <http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated>* in >>> the User's Guide. >>> >>> But, as Andrew suggested, we would have to see the log from startup to >>> be sure. >>> >>> -tk >>> >>> On Wed, Oct 16, 2019 at 4:04 AM Andrew Milner <andrew....@gmail.com> >>> wrote: >>> >>>> what came just before the log you posted? why is weewx attempting to >>>> do a catchup? had weewx just been started? had communications been lost >>>> for some reason? We need to know what is causing weewx to attempt a >>>> catchup >>>> in the first place. You can never post too much log!!!! >>>> >>>> >>>> >>>> >>>> On Wednesday, 16 October 2019 13:52:51 UTC+3, Andrea Cecilia wrote: >>>>> >>>>> here it is. As you can see, there is no "added record [...] to >>>>> weewx.sdb" line, which indicates that it is not downloading data from the >>>>> datalogger, and the reson (I think) is explained in the highlighted line. >>>>> >>>>> Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Getting archive >>>>> packets since 2019-10-16 09:05:00 CEST (1571209500) >>>>> Oct 16 10:30:14 raspberrypi weewx-vp2[511]: vantage: Gentle wake up >>>>> of console successful >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Retrieving 5 page >>>>> (s); starting index= 4 >>>>> *Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: DMPAFT complete: >>>>> page timestamp 2019-10-15 13:20:00 CEST (1571138400) less than final >>>>> timestamp 2019-10-16 09:05:00 CEST (1571209500)* >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Catch up complete >>>>> . >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running >>>>> reports for latest time in the database. >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Requesting 200 >>>>> LOOP packets. >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Running >>>>> report 'StandardReport' >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: vantage: Gentle wake up >>>>> of console successful >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: reportengine: Found >>>>> configuration file /home/weewx/skins/Standard/skin.conf for report >>>>> 'StandardReport' >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: cheetahgenerator: using >>>>> search list ['weewx.cheetahgenerator.Almanac', >>>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', ' >>>>> weewx.ch >>>>> eetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', >>>>> 'weewx.cheetahgenerator.Extras'] >>>>> Oct 16 10:30:15 raspberrypi weewx-vp2[511]: manager: Daily summary >>>>> version is 2.0 >>>>> Oct 16 10:30:17 raspberrypi weewx-vp2[511]: cheetahgenerator: >>>>> Generated 16 files for report StandardReport in 2.31 seconds >>>>> Oct 16 10:30:17 raspberrypi weewx-vp2[511]: manager: Daily summary >>>>> version is 2.0 >>>>> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: imagegenerator: Generated >>>>> 15 images for StandardReport in 1.36 seconds >>>>> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: copygenerator: copied 0 >>>>> files to /home/weewx/public_html/vp2 >>>>> Oct 16 10:30:18 raspberrypi weewx-vp2[511]: reportengine: Running >>>>> report 'FTP' >>>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: reportengine: Found >>>>> configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP' >>>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Attempting >>>>> connection to ftp.meteoregionelazio.it >>>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Connected to >>>>> ftp.meteoregionelazio.it >>>>> Oct 16 10:30:19 raspberrypi weewx-vp2[511]: ftpupload: Uploaded file / >>>>> www.meteoregionelazio.it/stazioni/soriano/weewx/vp2/daypond.png >>>>> >>>>> >>>>> -- >>>> 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 weewx...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/33dfe43a-f6d8-4131-b7d3-b5d4e8415b4d%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/33dfe43a-f6d8-4131-b7d3-b5d4e8415b4d%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/5fdcaf30-fb68-4e07-a683-95e258fa875b%40googlegroups.com.
