Generating same images over and over

[Jens-Jørgen Kjærgaard]

Suddenly, 11 days ago, weewx keeps generating same images over and over. No error in syslog, wee_device says: weewx.WakeupError: Unable to wake up Vantage console.

I tried to unplug the console, no change, even switched to another console, no change.

?

[gjr80]

I suggest we start with the log, you don’t need an error in the log to diagnose a problem

Gary

[Jens-Jørgen Kjærgaard]

Nov 11 07:00:17 jjk-F5RL weewx[10103]: cheetahgenerator: Generated 3 files for report StandardReport in 0.07 seconds

Nov 11 07:00:18 jjk-F5RL weewx[10103]: imagegenerator: Generated 24 images for StandardReport in 1.69 seconds

Nov 11 07:00:18 jjk-F5RL weewx[10103]: copygenerator: copied 14 files to /home/weewx/public_html

Nov 11 07:00:20 jjk-F5RL weewx[10103]: ftpgenerator: ftp'd 41 files in 2.05 seconds

Tried to stop and start weewx, delete all files from public_html - no change.

[gjr80]

Thanks but that log extract is not much use at all. We need to see a log extract showing the WeeWX startup and processing at least a couple of report cycles. I suggest you go to the link in my first post next work through the steps under ‘To get a good, useful log’ and post the resulting log.

Gary

[Jens-Jørgen Kjærgaard]

Debug = 1
Apparently no errors?

[gjr80]

No errors but what is missing is WeeWX is not obtaining any archive records from you console. You have all the symptoms of corrupt station memory. I suggest you refer to the Troubleshooting the Davis Vantage station wiki page and work through the steps in the Corrupt station memory section.

Gary

[Jens-Jørgen Kjærgaard]

wee_device --clear-memory:

...

raise weewx.WeeWxIOError("Unable to read hardware type")

weewx.WeeWxIOError: Unable to read hardware type

I don't understand why this happens. I even tried to use another console, same problem.

Then, as sugested option, I used:

[StdArchive]

    ...

    record_generation = software

- and this worked, thanks.

[gjr80]

Setting record_generation to hardware does not cure the corrupt station memory, rather it mitigates the symptoms. The underlying problem is still there, though it will now largely have no day to day effect on WeeWX operation. However, you should be aware that while the corrupt station memory remains you will no longer have the ability to backfill missing archive records from your station should WeeWX go offline for some reason.

Gary

[Jens-Jørgen Kjærgaard]

But then I don't get what the underlying problem is. Two diffrent consoles, same problem?

[gjr80]

Did you use the same logger in the different consoles? The memory is in the logger.

Gary

[Jens-Jørgen Kjærgaard]

No, different loggers as well

[gjr80]

I don’t know. It’s possible both loggers have corrupt station memory. It’s not as unlikely as you may think, corrupt station memory is frequently caused by power supply interruptions. If you are not reading archive records from the logger you would never know you have the problem; the console still works fine and any software that uses loop packets from the console will also work fine. WeeWX is one of the few PWS applications that use hardware archive records from the Davis logger/console and since the vantage driver default is to use hardware records WeeWX at times suffers the consequences of corrupt station memory.

One thing is certain; there is an issue with your logger. If the second console/logger is doing the same it has an issue too.

Gary