Vishnu,
Check that your shell init and dotfiles have the current modules installation and no remnant of a prior one:
grep -rl '\<module' {/etc/,~/.}*{sh*rc,profile*,login}
You could also try a traced shell initialization, best from a clean environment:
\env - \bash -lxc : 2>&1 | grep -Ew '\.|source|unalias|[Mm]odule\w+'
You *should* see that files from /etc/profile.d/ really are being sourced, and you *should not* see a line like "unalias module".
With best regards,
Michael
On Mar 19, 2021, at 06:38, Vishnu V. Krishnan <vis...@gm...> wrote:
After this upgrade, if you start a new shell session, what is the
result of the `module -V` command typed in this shell?
$ module -V
bash: module: command not found
If in a shell session you `source /etc/profile.d/env-modules.sh` then
type `module -V`, what is the output obtained from both commands?
$ module -V
Modules Release 4.7.0 (2021-02-19)
So the issue is that it isn't being sourced. I don't see why though.
|