|
From: LAURENT F. <lau...@ev...> - 2023-09-27 13:15:12
|
Ok Xavier. Thanks a lot for your nice support (again 😉) I will investigate more and probably find the solution with your inputs. Bye Laurent From: Xavier Delaruelle <xav...@gm...> Sent: 27 September 2023 14:09 To: LAURENT FIGADERE <lau...@at...> Cc: Environment Modules usage and discussion. <mod...@li...> Subject: Re: [Modules] Question Module Caution: External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. Le mer. 27 sept. 2023 à 13:34, LAURENT FIGADERE <lau...@ev...<mailto:lau...@ev...>> a écrit : Hi Xavier, Ok thanks: I am adding the option set_shell_startup during the installation and cross check if it’s resolving my issue. Concerning the header: you said ‘Modulefiles should start with the #%Module magic cookie string’ But as I told to you my modulefiles start with : ‘#%Module2.0’. Does it mean I have to remove 2.0 ? "2.0" can be kept. Version specification can be set right after #%Module". I suspect that such error comes from .modulerc or .version files inside your modulepaths that do not start with "#%Module". By running the command with --debug, you will be able to spot where this error comes from. Regards, Xavier Regards Laurent From: Xavier Delaruelle <xav...@gm...<mailto:xav...@gm...>> Sent: 27 September 2023 13:23 To: Environment Modules usage and discussion. <mod...@li...<mailto:mod...@li...>>; LAURENT FIGADERE <lau...@at...<mailto:lau...@at...>> Subject: Re: [Modules] Question Module Caution: External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. Hi Laurent, Le mer. 27 sept. 2023 à 13:11, LAURENT FIGADERE via Modules-interest <mod...@li...<mailto:mod...@li...>> a écrit : Hi all, We are using for the moment module version 4.7.0. With this version, I have sometimes this error: Module ERROR: Magic cookie '#%Module' missing Even the modulefiles exist and contains the header: #%Module2.0 First question: do you know this issue root cause? Modulefiles should start with the #%Module magic cookie string. This error is obtained when this magic cookie is not found at the start of the file. You should be seing this error consistently for the same files. Running command in --debug mode would help to see the file with issues. To give more info, we are loading the modulefiles in several jobs in parallel at the same time. I saw in recent release, since 5.1, this documentation: https://modules.readthedocs.io/en/latest/module.html#mconfig-mcookie_check Can MODULES_MCOOKIE_CHECK or MODULES_MCOOKIE_VERSION_CHECK help to resolve these errors? MODULES_MCOOKIE_CHECK would help to disable the magic cookie check. But to use it you must ensure that only modulefiles are inside the modulepath directories. And now, I have another question. To try if it could help us to remove these errors, I tried to use module version 5.3.1. But now, I am faced to another issue: even I source the bash init, I have this eror here after: Like the init was not done properly. Did somebody see this kind of issue? Your test.sh script runs inside a sub-shell. It does not inherit the module shell function unless module was initialized in the upper shell session with the set_shell_startup option enabled (https://modules.readthedocs.io/en/latest/module.html#mconfig-set_shell_startup). Regards, Xavier |
