You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I previously added a comment to #732 (comment), but I opened a new issue as the error message is different.
Running juliaup or julialauncher results in a crash. I think it is due to file locking not working on the filesystem (NFSv3 at the university, NLM seems to have stopped working). This is on Linux. I think something on our network config was changed by the admins, resulting in NLM not working anymore, which results in file locking failing on the NFS mounted dirs (where I have installed julia/juliaup).
A possible workaround would be to allow an environment var to change the lock file location as described in #844 .
I used this little python program to confirm that file locking doesn't work on the NFS mounted home dir:
#!/usr/bin/env python3importargparseimportfcntlimportsysimporttimedeftest_lock(file_path):
withopen(file_path, 'w') asf:
print(f"Attempting to lock the file: {file_path}")
try:
fcntl.flock(f, fcntl.LOCK_EX|fcntl.LOCK_NB)
print("Lock acquired. Holding for 5 seconds...")
time.sleep(5)
print("Releasing lock.")
fcntl.flock(f, fcntl.LOCK_UN)
exceptIOErrorase:
print(f"Error: Unable to acquire the lock on {file_path}. Error: {e}")
return1return0defmain(argv):
parser=argparse.ArgumentParser(description='Test file locking')
parser.add_argument('file_path', type=str, help='Path to the file for locking test.')
args=parser.parse_args(argv[1:]) # skip the script name in argv[0]returntest_lock(args.file_path)
if__name__=='__main__':
sys.exit(main(sys.argv))
It works on /tmp:
$ ~/bin/locktest.py /tmp/foo
Attempting to lock the file: /tmp/foo
Lock acquired. Holding for 5 seconds...
Releasing lock.
But fails on the home dir (mounted via NFS):
$ ~/bin/locktest.py ~/foo
Attempting to lock the file: ~/foo
Error: Unable to acquire the lock on ~/foo. Error: [Errno 37] No locks available
The text was updated successfully, but these errors were encountered:
I previously added a comment to #732 (comment), but I opened a new issue as the error message is different.
Running
juliaup
orjulialauncher
results in a crash. I think it is due to file locking not working on the filesystem (NFSv3 at the university, NLM seems to have stopped working). This is on Linux. I think something on our network config was changed by the admins, resulting in NLM not working anymore, which results in file locking failing on the NFS mounted dirs (where I have installed julia/juliaup).A possible workaround would be to allow an environment var to change the lock file location as described in #844 .
I used this little python program to confirm that file locking doesn't work on the NFS mounted home dir:
It works on
/tmp
:But fails on the home dir (mounted via NFS):
The text was updated successfully, but these errors were encountered: