# Lmod has detected the following error: The following module(s) are unknown

**URL:** <https://discourse.openondemand.org/t/lmod-has-detected-the-following-error-the-following-module-s-are-unknown/1333>\
**Category:** Get Help\
**Created:** [February 19, 2021, 9:20pm UTC](https://discourse.openondemand.org/t/lmod-has-detected-the-following-error-the-following-module-s-are-unknown/1333 "2021-02-19T21:20:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rgas20](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/rgas20/32/309_2.png) [@rgas20](https://discourse.openondemand.org/u/rgas20)\
**Post date:** [February 19, 2021, 9:20pm UTC](https://discourse.openondemand.org/t/lmod-has-detected-the-following-error-the-following-module-s-are-unknown/1333/1 "2021-02-19T21:20:37Z")

</div>

All,

Having one more issue with loading modules on a new instance of Open OnDemand.

When I load a Jupyter notebook for instance:

Script starting…  
Waiting for Jupyter Notebook server to open port 38242…  
TIMING - Starting wait at: Fri Feb 19 15:04:51 CST 2021  
TIMING - Starting main script at: Fri Feb 19 15:04:51 CST 2021  
Lmod has detected the following error: The following module(s) are unknown:  
“python/3.7”

Please check the spelling or version number. Also try “module spider …”  
It is also possible your cache file is out-of-date; it may help to try:  
$ module --ignore-cache load “python/3.7”

Also make sure that all modulefiles written in TCL start with the string  
#%Module

This application template has been taken from a working instance of OOD and copied over to a fresh setup of OOD, looking through the docs I seem to have all the bases covered. In the form.yml we are asking it to load the python/3.7 module. I’ve also verified that the reverse proxy is working correctly from the new instance and tested it as a prerequisite to setting up the apps. When I check the submit node on our cluster, I can see the job starting in the queue (then failing) so it doesn’t seem to be a limitation in that regard. I’m not sure what to check next however or what else may be missing. Any help is appreciated.

---

<div class="post-metadata">

**Author:** ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)\
**Post date:** [February 19, 2021, 9:46pm UTC](https://discourse.openondemand.org/t/lmod-has-detected-the-following-error-the-following-module-s-are-unknown/1333/2 "2021-02-19T21:46:43Z")

</div>

Does that module, `python/3.7` actually exist on the compute node? There’s not much too this issue, proxies and all that. It’s an issue confined to the job itself. I’d hop on a compute node and verify that that module does indeed exist (through `module load` or `module spider` commands)

It seems like the module doesn’t in fact exist on the compute node. When you say you’re spinning a new OOD instance, is this new instance also interacting with new compute infrastructure?

I just ran this on our Slurm infrastructure to sort of replicate the issue and triage. This would create a job and just spit out all the modules.

```auto
sbatch --export=NONE --wrap 'module spider'

```

I’m guessing that you won’t see `python/3.7` even if you submit this very simple job. Though if you can infact see it there and not through OOD - let me know because that would be very strange and indeed we’d have to look more at it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/osc/original/2X/b/bae70bd0ed39a3ae769c2108155f4cb3e9da8385.png) [@system](https://discourse.openondemand.org/u/system)\
**Post date:** [March 14, 2022, 6:45pm UTC](https://discourse.openondemand.org/t/lmod-has-detected-the-following-error-the-following-module-s-are-unknown/1333/3 "2022-03-14T18:45:14Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.