Sigh.  Usual thoughts.

set debug=1 and provide the logs that result the next time it happens
or if you already had debug=1, provide the logs you have up to when it went 
bad

We can't read minds.

On Saturday, December 16, 2023 at 8:29:23 AM UTC-8 Chris Alemany wrote:

> Hi all,
>
> Stumped here:  Yesterday at 4:10PM weewx v5.0b15 (pip install on Debian) 
> stopped updating the archive.sdb. It turns out that an hour before that, it 
> stopped updating the forecast.sdb file. Some other reports are still 
> running (purple, Wundergound, divumWX/Weather34) but anything that depends 
> on info from the archive is stuck at 4:10PM. As I mentioned, there are no 
> errors reported. It is simply silent when the 5min archive time comes and 
> it runs through reports with the old data while the loop packets update 
> independantly.  Are there any additional logging options I can turn on that 
> deal with archive generation?
>
> I decided to try updating to b17 just to see if it would kickstart 
> anything but I have the same behaviour.
>
> I’m using a Davis Vantage Pro 2 with serial data logger -> ethernet bridge.
>
> I double checked the Davis side, restarted the bridge with no change.
>
> All Debian 11 packages are up to date.
>
> Any thoughts welcome.
> https://alberniweather.ca
>
> Thanks
> Chris
>
>
>
> Chris Alemany
> 3854 6th Avenue
> Port Alberni, BC
> V9Y4M2
> On Stolen Traditional Territory of c̓išaaʔath and hupačasatḥ 
> First Nations.
> 250-731-7930 <(250)%20731-7930>
> Web: https://chrisalemany,ca
> Social: https://mstdn.chrisalemany.ca/@chris
>
> Other Blogs and Socials:
> https://alberniweather.ca
> https://mstdn.ca/@alberniweather.ca
> https://vibyrail.ca
> https://mstdn.ca/@vibyrail
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" 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-development/46f1ab56-7544-4ca2-bb7e-667ea8cd9ccan%40googlegroups.com.

Reply via email to