Data not getting written to database after hardware change

[Jim Wilkerson]

Using a Vantage Pro2 console.

Had been using a Meteobridge NanoSD, but it has failed, possible a wireless issue.

I switched back to my previous solution, a TP Link MR3020, which came right up as it had been running some time back (new license applied).

Weather uploads work, but I am not seeing an records written to the database now.

I see:

INFO weewx.reportengine: Copied 5 files to /var/www/html/weewx
INFO weewx.imagegenerator: Generated 45 images for report SeasonsReport in 1.20 seconds
INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 0.65 seconds

but no records written, i.e. expect to see

INFO weewx.manager: Added record 2024-12-12 00:30:00 EST (1733981400) to database 'weewx.sdb'
NFO weewx.manager: Added record 2024-12-12 00:30:00 EST (1733981400) to daily summary in 'weewx.sdb'

 

[Tom Keffer]

We need to see more of the log. In particular, set debug=1, then restart. Let it run through the first reporting cycle. Then post the log from startup.

[Jim Wilkerson]

I attached the log from when I restarted with debug=1 until this most recent cycle at 09:30 EST.

Thanks.

[Jim Wilkerson]

Here are the messages from my Linux system as well.

[Tom Keffer]

Classic case of corrupted memory in the logger. See the wiki article Corrupt station memory.

[Francisco Alonso]

I guess you are now using an old datalogger attached to the console.

The final record in the memory is old, with a date which is previous to the last record in the DB: 15/12/2024 at 18:00 h:

DMPAFT complete: page timestamp 2021-06-14 01:30:00 EDT (1623648600) less than final timestamp 2024-12-15 18:00:00 EST
Try deleting the memory of the datalogger and restart weewx.

[Jim Wilkerson]

Thanks so much, that process worked to clear the logger.

I attached the log out put for reference after restarting weewx.

Is there any way to get the records that did not write to the database added to show in the web GUI reporting?

[Jim Wilkerson]

Actually, upon closer examination, it looks like it did write the previous records that the logger had collected when  I restarted it  last night.

Thanks again!