Welcome to the new DiscussCESM forum!
We are still working on the website migration, so you may experience downtime during this process.

Existing users, please reset your password before logging in here: https://xenforo.cgd.ucar.edu/cesm/index.php?lost-password/

cheyenne error loading module 'tcl2lua'

thoar

New Member
I have downloaded tag release-cesm2.2.0 and am trying to build a 3 member multi-instance (multi-driver) case and am running into the following:


ERROR: module command /glade/u/apps/ch/opt/lmod/7.5.3/lmod/lmod/libexec/lmod python load ncarenv/1.3 cmake intel/19.0.5 esmf_libs mkl failed with message:
/glade/u/apps/ch/opt/lmod/8.1.7/bin/lua: error loading module 'tcl2lua' from file '/glade/u/apps/ch/opt/lmod/7.5.3/lmod/lmod/libexec/../lib/tcl2lua.so':
libimf.so: cannot open shared object file: No such file or directory
stack traceback:
[C]: ?
[C]: in function 'require'
...u/apps/ch/opt/lmod/7.5.3/lmod/lmod/libexec/utils.lua:828: in function 'build_runTCLprog'
...u/apps/ch/opt/lmod/7.5.3/lmod/lmod/libexec/utils.lua:833: in main chunk
[C]: in function 'require'
...pps/ch/opt/lmod/7.5.3/lmod/lmod/libexec/colorize.lua:43: in main chunk
[C]: in function 'require'
...lade/u/apps/ch/opt/lmod/7.5.3/lmod/lmod/libexec/lmod:110: in main chunk
[C]: ?


ERROR: Case could not be set up.

My loaded modules are:


Currently Loaded Modules:
1) ncarenv/1.3 2) intel/19.0.5 3) ncarcompilers/0.5.0 4) mpt/2.22 5) netcdf/4.7.4 6) mkl/2019.0.5

Has anyone run into this? More specifically ... how do I fix it?
 

fischer

CSEG and Liaisons
Staff member
Is this a repeatable error? I was able to build a multi-instance and multi-driver test using release-cesm2.2.0 on cheyenne.

Chris
 

thoar

New Member
VERY repeatable ... what modules do you have loaded ... and what modules is the test using?
Perhaps also ... what shell are you running?
 

fischer

CSEG and Liaisons
Staff member
The cesm scripts purge the user modules, and loads it's own modules that specified in env_mach_specific.xml.
You can see the commands issued in .env_mach_specific.sh for bash or .env_mach_specific.csh for csh/tcsh.
I'm using tcsh, but the shell shouldn't make a difference.

Can you point me to your case on cheyenne, then I can try to repeat your failure.

Thanks
Chris
 

thoar

New Member
Grrrrr .... system configuration change, apparently. In short, something between my .login and my .tcshrc (both of which have worked fine since the dawn of cheyenne) now conflicts. I am tracking it down, but I seem to be on my way. Essentially, I had to remove my .tcshrc and just use the .login. As I say, I am exploring why my previous environment that worked for years is no longer working.

Sorry to bother anyone.
 
Top