[GRASS-user] Running GRASS with modules
Luís Moreira de Sousa
luis.de.sousa at protonmail.ch
Tue Feb 5 02:48:36 PST 2019
Dear all,
I am using GRASS in an HPC platform where libraries are managed with modules [0]. Recently I made GRASS 7.6 available as a shared module. This involved copying the compiled folder to a shared location and then creating a modulefile [1] (which essentially sets the correct PATH environment variable). I am able to load the GRASS module and run it; however, when other users try to do the same they get this error:
$ grass76
Cleaning up temporary files...
Traceback (most recent call last):
File "/cm/shared/apps/WUR/ESG/modules/grass/bin/grass76", line 2209, in <module>
main()
File "/cm/shared/apps/WUR/ESG/modules/grass/bin/grass76", line 2087, in main
clean_temp()
File "/cm/shared/apps/WUR/ESG/modules/grass/bin/grass76", line 1784, in clean_temp
call([gpath("etc", "clean_temp")], stdout=nul)
File "/cm/shared/apps/WUR/ESG/modules/grass/bin/grass76", line 247, in call
return subprocess.call(cmd, **kwargs)
File "/usr/lib64/python2.7/subprocess.py", line 524, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 13] Permission denied
Naturally, GRASS is unable to access some asset it needs, the question is what? All users have read and execute permissions on the shared module folders and files. When it is launched, is GRASS trying to write somewhere? Which other assets GRASS needs to read when it is launched?
Thank you.
[0] http://modules.sourceforge.net/
[1] https://modules.readthedocs.io/en/latest/modulefile.html
--
Luís Moreira de Sousa
RingID: ring:7ca91d83f4f9dec82fec9f1144b8e5c1ef2a110c
URL: https://ldesousa.github.io
Sent with [ProtonMail](https://protonmail.com) Secure Email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190205/00e2493c/attachment.html>
More information about the grass-user
mailing list