I am using the python-based spack package manager to manage different versions of packages on my system. I am using a NFS mount system where the users always log into the same [/nethome] directory on different workstations. According to the result of nfsstat -m the NFS version is v3.
After having no problems for over two weeks, I suddenly started receiving the error [Errno 37] No locks available whenever I try to perform any action using this package manager.
I did not change anything about the spack setup during that time and also tried reinstalling this package manager multiple times, with no success.
The [Errno 37] No locks available error is raised by the systemcall fcntl, which modifies file descriptors, so we assume it's a permission error related to our NFS mount system. Since a regular user only has rwx privileges in his own home directory, a permission error would occur if he tried to write or execute a file that is located somewhere outside of there. Unfortunately this error does not specify what file this package manager is trying to modify.
Is there a way to backtrace where this error might be coming from? My biggest problem is that it's not reliably reproducible and stopped occuring again today, so I am not sure how to get to the root of this issue.
My system has had the following specs when the error occurred and also when it disappeared again:
- Spack: 0.17.1-1181-76489eb213
- Python: 3.6.9
- Platform: linux-ubuntu18.04-nehalem
- Concretizer: clingo
