When I read more on that issue, he is saying exactly the issue:

I should add that I am able to replicate this using the mitct02/weewx Docker image. v5.4.0-5 is Belchertown-new beta3 and 5.4.0-6 is Belchertown-new 2.0. If I merely swap in the 5.4.0-6 image, the report cycle completes in well under the archive interval and this issue does not surface, though I do suspect it would in the event of a huge database.

So, we know why the db was locked.  The issue to be investigated is why the long report cycles.  Since he swap in different betchlertown versions and produce the long report cycles (keeping all other extensions the same), we kind of know what enervation to look at, no?

John

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


My bad. I forgot that OP said two threads, not two weewx instances.

Sorry about that!
---
pablo

On August 3, 2026 19:58:26 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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/650a2beb-76c1-4058-b0d1-5c1123b780c2n%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/19fca31d010.2848.44b74f35a7a433c111dbfaee4cca1c2d%40hillsandlakes.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/4AD2749D-617A-4BE1-B2E6-3210E9E469A0%40johnkline.com.

Reply via email to