Re: [weewx-user] catching the 'why' of engine.py exiting

Mon, 03 Aug 2026 19:36:58 -0700

My what twists and turns this is taking for people, including me, who are jumping into the discussion without reading everthing.

Do I have it right that you are not interested in why the reporting cycle is taking too long and spilling into the next archive cycle?

What are you interested in?  The fact that weewx couldn’t get a write lock on the next archive cycle?

On Aug 3, 2026, at 7:17 PM, [email protected] <[email protected]> wrote:

OP here, lol. As I said in the issue discussion, this deployment is a reference implementation for poor performance. I think the important issue is that in this instance, when the report cycle exceeded the archive interval, weewx didn't tell me that since another report was running, it would abort this cycle. It just tried to run a new cycle while the other one was still running. I get that it's not optimal for instances to take that long to run a report cycle, but it happens and weewx is designed and built to handle it. For some reason, it just plows ahead with another run which starts the crud happening.

The beta4 fixes get my instance under the threshold so it runs, but it's a ticking time bomb I think.

On Monday, August 3, 2026 at 7:04:21 PM UTC-7 Vince Skahan wrote:
I suggested trying to bisect the commits by trying versions between what worked and what doesn’t to try to pin down which commit was the one that triggered the issue, but that’s a lot of work.

John did you run the simulator or vs a davis station ?  I can try to test on a rebuilt pi4 tomorrow or even build my own docker image pretty easily vs a very big db but only vs the sim. Don’t want to break my prod pi :-)

On Monday, August 3, 2026 at 5:43:18 PM UTC-7 Rich Bell wrote:
Sounds like the new version is hitting the database “hard”. Should be easy enough for the extension writer to know what SQL queries were introduced and possibly create a “debug version” to see what is going on.
Disclaimer: I have not followed the link, only following this discussion.
rich
On Mon, Aug 3, 2026 at 7:58 PM Vince Skahan <[email protected]> wrote:
No it doesn’t say that in anything I’ve read or have been told via email.

https://github.com/uajqq/weewx-belchertown-new/issues/298 has the github issue and more info. Short description is version X works and version Y does not, so it sounds like a version issue to me,

I suppose it is remotely possible there is a hung docker container holding the file open but that’s unlikely. The o.p. is an experienced docker user.

On Monday, August 3, 2026 at 4:34:54 PM UTC-7 John Kline wrote:
> The OP stated (in the original thread) that he had multiple weewx instances running.

If the OP has multiple weewx instances running and writing to the same SQLite db, there is nothing to investigate.  Is that really the case?

On Aug 3, 2026, at 4:11 PM, Pablo Sanchez <[email protected]> wrote:


SQL lite only allows a single writer at the file level. The OP stated (in the original thread) that he had multiple weewx instances running.
---
pablo

On August 3, 2026 18:10:52 Greg Troxel <[email protected]> wrote:

Is there really full locking, vs using transactions?  SERIALIZABLE, or
just READ COMMITTED?

-- 
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].

--
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].

--
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].

--
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 visit https://groups.google.com/d/msgid/weewx-user/084f02e7-129e-4903-a500-2b9b61afd018n%40googlegroups.com.

--
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 visit https://groups.google.com/d/msgid/weewx-user/A11F6604-8067-43A1-B660-56CCA3F4548A%40johnkline.com.

Reply via email to