[INSTRM-787] pfsinstall failed (lock dir issue) Created: 01/Oct/19 Updated: 29/Jun/20 Resolved: 05/Dec/19 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | fmadec | Assignee: | cloomis |
| Resolution: | Done | Votes: | 0 |
| Labels: | SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | SM1-2019 O | ||||||||
| Description |
|
I've got this error when I try to update an actor using pfsinstall Unable to take exclusive lock on /software/mhs/products: locks are held by [user=pfs, pid=8180]; retrying eups declare: Unable to take exclusive lock on /software/mhs/products: locks are held by [user=pfs, pid=8180] [user=pfs, pid=15946] I removed the file by hand, but this not a good way to proceed, so what is the procedure for that ? btw what the purpose of the lockdir ?
|
| Comments |
| Comment by cloomis [ 02/Oct/19 ] |
|
rhl – what should PFS do about EUPS locks? At JHU I have hooks.config.site.lockDirectoryBase = None in /software/mhs/products/site/startup.py. Is that right or wrong? |
| Comment by rhl [ 03/Oct/19 ] |
|
The command eups startup should tell you where this file is located; if it doesn't, use eups startup -v. |
| Comment by cloomis [ 03/Oct/19 ] |
|
At LAM: pfs@pfs-mhs:~$ eups startup -v [/software/mhs/products/eups/2.1.4/site/startup.py] /software/mhs/products/site/startup.py [/home/pfs/.eups/site/startup.py] [/home/pfs/.eups/startup.py] pfs@pfs-mhs:~$ cat /software/mhs/products/site/startup.py Of those, I would use the second (global, but not version-specific); the change is yours to make. FWIW the fix is already in place at Subaru: I must have run into the problem during an MCS run. |
| Comment by hassan [ 05/Dec/19 ] |
|
Closed as fix already in place at Subaru. |