Surely, the fatal error is weewx not being able to get a write lock to write
the archive record. It says just that.
Let’s find out what is stuck in the report cycle.
I’m not a Docker guy, so I’ve had to Google the following. Please chime in
with docker corrections as needed:
Install py-spy on the machine running Docker (not inside the container) and run:
docker top <container> — to get the host PID for weewxd
sudo py-spy dump --pid <host-pid>
Run the py-spy every 30 seconds or so starting when the report cycle begins.
Repeated samples landing in the same frame will show where it’s stuck.
John
> On Aug 3, 2026, at 7:36 PM, John Kline <[email protected]> wrote:
>
> 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?
--
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/E1847B7C-0718-43D4-9C00-C9BA1AF23B5B%40johnkline.com.
