So a quick update. I took a copy of the database and checked the archive table. I seem to have acquired these two rows at the top. I have removed them and copied the database back and I get a new error but believe I am getting somewhere:
*Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: Caught unrecoverable exception:* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** lastUpdate(2112-04-20 11:47:00 GMT (4490596020)) > lastRecord(2021-06-16 20:16:00 BST (1623870960))* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** Traceback (most recent call last):* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** File "/home/weewx/bin/weewxd", line 154, in main* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** engine.run()* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** File "/home/weewx/bin/weewx/engine.py", line 158, in run* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** self.dispatchEvent(weewx.Event(weewx.STARTUP))* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** File "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** callback(event)* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** File "/home/weewx/bin/weewx/engine.py", line 522, in startup* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** _nrecs, _ndays = dbmanager.backfill_day_summary()* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** File "/home/weewx/bin/weewx/manager.py", line 1012, in backfill_day_summary* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** timestamp_to_string(lastRecord)))* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** weewx.ViolatedPrecondition: lastUpdate(2112-04-20 11:47:00 GMT (4490596020)) > lastRecord(2021-06-16 20:16:00 BST (1623870960))* *Jun 17 08:11:01 pecan-ubuntu weewx[2098] CRITICAL __main__: **** Exiting.* So, my next question is where in the database will I find referrences to this exceptional date? Thanks again Chris [image: Capture.PNG] On Thursday, June 17, 2021 at 7:56:53 AM UTC+1 Chris Davies-Barnard wrote: > Morning Gary, > > Thanks for replying. I hope its not a faulty unit as that could be the > death of the weather station for now. She is over 10 years old now and I > replaced one of the sensor modules only last year. If she does die I > think I would build my own open source kit maybe? Anyway getting ahead of > myself. > > *1) Stop Weewx* > *It seems at some point in my wisdom I set up weewx as a Daemon so I have > removed weewx from /etc/init.d and restarted the server (Its ubuntu running > on QNAP's Virtualisation Station).* > > *2) Checking for remaining processes* > *auser@pecan-ubuntu:/home/weewx$ ps aux | grep -i weewx* > *auser** 1238 0.0 0.0 14428 1032 pts/0 S+ 07:34 0:00 grep > --color=auto -i weewx* > *auser**@pecan-ubuntu**:/home/weewx$ pidof weewx* > *auser**@pecan-ubuntu**:/home/weewx$ * > > *3) sudo ./bin/wee_device --clear-memory * > *Using configuration file /home/weewx/weewx.conf* > *Using Vantage driver version 3.2.1 (weewx.drivers.vantage)* > *Proceeding will erase all archive records.* > *Are you sure you wish to proceed (y/n)? y* > *Erasing all archive records ...* > *Archive records erased.* > > *4) set debug = 1 in weewx.conf and restart WeeWX with sudo ./bin/weewxd* > syslog output is in attached file but run terminal output is like: > > > *LOOP: 2021-06-17 07:40:57 BST (1623912057) altimeter: > 29.86448769405689, appTemp: 54.776612632572494, barometer: 29.855, > beaufort: 0, cloudbase: 1583.4599268474649, consBatteryVoltage: 4.48, > dateTime: 1623912057, dayET: 0.0, dayRain: 0.0, dewpoint: > 50.709576321871154, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, > extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, > extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 54.5, > humidex: 57.13247206192764, inDewpoint: 55.93846853316417, inHumidity: > 59.0, insideAlarm: 0, inTemp: 71.0, leafWet4: 0.0, maxSolarRad: > 363.4009700897632, monthET: 0.0, monthRain: 0.0, outHumidity: 87.0, > outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 54.5, pressure: 29.09* > > The loop date is correct so the question I have here is where has > 2112-04-20 come from below? > > * DEBUG weewx.drivers.vantage: Getting archive packets since 2112-04-20 > 11:47:00 GMT (4490596020)* > > *Jun 17 07:41:14 pecan-ubuntu weewx[1372] DEBUG weewx.drivers.vantage: > Gentle wake up of console successfulJun 17 07:41:14 pecan-ubuntu > weewx[1372] DEBUG weewx.drivers.vantage: Retrieving 513 page(s); starting > index= 3Jun 17 07:41:15 pecan-ubuntu weewx[1372] ERROR weewx.engine: > Internal error detected. Catchup abandonedJun 17 07:41:15 pecan-ubuntu > weewx[1372] ERROR weewx.engine: **** Unknown archive type = 0x37* > I think my next step is going to be grabbing a copy of the database and > seeing if I can see any problems but if you have any thoughts or solutions > in mind I'd be grateful. > > Thanks > > Chris > On Thursday, June 17, 2021 at 12:15:48 AM UTC+1 gjr80 wrote: > >> The few times this error seems to have come up the solution seems to be >> clearing the logger memory or failing that contacting Davis due to a faulty >> logger. >> >> I would not expect wee_device --dump to do anything different, it >> essentially is doing the same as the startup catchup just for all records >> in the logger memory. You say wee_device --clear-memory 'seems to >> succeed', what does that mean, the --clear-memory command gives >> appropriate output but subsequent restarting WeeWX causes the same output? >> or does it mean that everything cleared up but the problem came back later? >> >> What does 'clear the logger using its own functions' mean? I thought the >> only way to clear the logger was to use some suitable/capable software? And >> do you still have a phantom WeeWX process running? >> >> How about trying this: >> 1. stop WeeWX >> 2. check for any remaining WeeWX processes and if any exist kill them >> manually >> 3. run wee_device --clear-memory and post the command used and the >> resulting output >> 4. set debug = 1 in weewx.conf and restart WeeWX, post the WeeWX log >> output from startup through until an error occurs or data is obtained >> successfully from the station >> >> Gary >> >> On Thursday, 17 June 2021 at 06:25:02 UTC+10 Chris Davies-Barnard wrote: >> >>> Evening all, >>> >>> So I had to move the logger and ubuntu box today and upon reconnecting >>> and restarting I have encountered the following error. >>> >>> J*un 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: >>> Getting archive packets since 2112-04-20 11:47:00 GMT (4490596020)* >>> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: >>> Gentle wake up of console successful* >>> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: >>> Retrieving 513 page(s); starting index= 2* >>> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: Internal >>> error detected. Catchup abandoned* >>> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] ERROR weewx.engine: **** >>> Unknown archive type = 0xae* >>> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.reportengine: >>> Running reports for latest time in the database.* >>> *Jun 16 21:00:16 pecan-ubuntu weewx[1823] DEBUG weewx.drivers.vantage: >>> Requesting 200 LOOP packets.* >>> >>> I have tried >>> >>> 1) sudo ./bin/wee_device --dump which ends in same/similar error >>> 2) sudo ./bin/wee_device --clear-memory which seems to succeed. >>> >>> I have also cleared the logger using its own functions but thee >>> situation is the same.. >>> >>> What's interesting is that stopping weewx seems to cause a lock and it >>> never completes. >>> >>> If anyone could help me solve the problem I would be very grateful. >>> >>> Thanks >>> >>> Chris >>> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/59de4399-84ae-4983-9dfa-ed94b3f6e309n%40googlegroups.com.
