semaphore handling could use improvement
Bug #1877014 reported by
Paul Collins
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Repository Cache Charm |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
If the sync is killed, it can end up in the following state:
2020-05-05 20:02:01,240 - Can't acquire semaphore: /tmp/metadata-
This file should at least be a pid file, with a check that the pid exists and is a python3 process, or suchlike, and if not, then we force the lock.
However, we already wrap the cron invocation in run-one, so this seems spurious.
Revision history for this message
| Haw Loeung (hloeung) wrote | #1 |
| Changed in ubuntu-repository-cache: | |
| status: | New → Confirmed |
To post a comment you must log in.
This is probably not needed since the cron job to fire the sync is wrapped by run-one.