Stale db locks can't be recovered
Bug #1008353 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
High
|
Gavin Panella | ||
| postgresfixture |
Triaged
|
High
|
Unassigned | ||
Bug Description
ed@beast:
/home/ed/
* 6487 (*unknown*)
ed@beast:
ed 15665 2864 0 16:51 pts/7 00:00:00 grep 6487
ed@beast:
/home/ed/
* 6487 (*unknown*)
| Changed in maas: | |
| assignee: | nobody → Gavin Panella (allenap) |
Revision history for this message
| Gavin Panella (allenap) wrote | #1 |
| Changed in postgresfixture: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| importance: | Medium → High |
| tags: | added: dev-environment |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
As a workaround, when you see (*unknown*), delete the corresponding file in db/locks. For example, if you see:
/home/
* 6487 (*unknown*)
do:
$ rm /home/ed/
The (*unknown*) bit means that it was unable to determine the command line for that process, which 99% of the time means that process is no longer running.