2 Feb
2023
2 Feb
'23
10:23 p.m.
On Wed, Feb 01, 2023 at 01:13:21PM -0800, Jake via sudo-sys wrote:
what does this mean?
On Wed, 1 Feb 2023, Cron Daemon via sudo-sys wrote:
> ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty)
> Traceback (most recent call last):
> File
"/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py",
line 40, in runjobs
> job().execute()
> File
"/usr/lib/python3/dist-packages/hyperkitty/jobs/update_and_clean_index.py", line
37, in execute
> run_with_lock(update_index, remove=True)
> File "/usr/lib/python3/dist-packages/hyperkitty/lib/utils.py", line 181,
in run_with_lock
> log.exception("Failed to update the fulltext index: %s", e)
> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 447,
in __exit__
> self.unlock()
> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 398,
in unlock
> raise NotLockedError('Already unlocked')
> flufl.lock._lockfile.NotLockedError: Already unlocked
Putting my "janky python debugger" hat on, looks like a concurrency bug.
This "lock" is just a temporary file that seems to have an expiration
time (15 sec), after which some other process can "acquire" the same
"lock", stomping the first "lock". That's my guess as to what
happened:
something took longer than 15 seconds to complete.
Let's see if it happens again on the next monthly run.
--Sean