HPCE/gitea-pages
0
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Activity

Add fix for /etc/bashrc not being sourced.

Browse Source
This commit is contained in:
Spencer Bliven
2023-09-14 11:25:47 +02:00
parent 05ef348dc3
commit dbb3336a83
2 changed files with 25 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
pages/merlin6/99-support/faq.md
View File

@ -46,3 +46,7 @@ conda create --name myenv python==3.9 ...
conda activate myenv
```
## Something doesn't work
Check the list of [known problems](/merlin6/known-problems.html) to see if a solution is known.
If not, please [contact the admins](/merlin6/contact.html).

23
pages/merlin6/99-support/known-problems.md
View File

@ -1,7 +1,7 @@
---
title: Known Problems
#tags:
keywords: known problems, troubleshooting, illegal instructions, paraview, ansys, shell, opengl, mesa
keywords: known problems, troubleshooting, illegal instructions, paraview, ansys, shell, opengl, mesa, vglrun, module: command not found, error
last_updated: 07 September 2022
#summary: ""
sidebar: merlin6_sidebar
@ -91,7 +91,7 @@ In this example, by setting an environment variable SRUN_CPUS_PER_TASK
In general, **`/bin/bash` is the recommended default user's SHELL** when working in Merlin.
Some users might notice that BASH is not the default SHELL when login to Merlin systems, or they might need to run a different SHELL.
Some users might notice that BASH is not the default SHELL when logging in to Merlin systems, or they might need to run a different SHELL.
This is probably because when the PSI account was requested, no SHELL description was specified or a different one was requested explicitly by the requestor.
Users can check which is the default SHELL specified in the PSI account with the following command:
@ -159,3 +159,22 @@ fluent -driver x11
For running Paraview, one can run it with Mesa support or OpenGL support. Please refer to [OpenGL vs Mesa](/merlin6/known-problems.html#opengl-vs-mesa) for
further information about how to run it.
### Module command not found
In some circumstances the module command may not be initialized properly. For instance, you may see the following error upon logon:
```
bash: module: command not found
```
The most common cause for this is a custom `.bashrc` file which fails to source the global `/etc/bashrc` responsible for setting up PModules in some OS versions. To fix this, add the following to `$HOME/.bashrc`:
```bash
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
```
It can also be fixed temporarily in an existing terminal by running `. /etc/bashrc` manually.