PDA

View Full Version : F17 -> F18 beta, openmpi issue



artu72
10th December 2012, 11:28 AM
I have succesfully updated from F17 to F18 beta via fedup. Everything works fine apart openmpi. When I try to load the module, it gives the following error.



$ module load openmpi
ModuleCmd_Load.c(204):ERROR:105: Unable to locate a modulefile for 'openmpi'


Googling didn't helped me. Any suggestion?

mtk
10th December 2012, 05:29 PM
not an answer to your problem but a request for unrelated info - care to describe the fedup upgrade process in detail?

AdamW
10th December 2012, 09:23 PM
mtk: https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F

what actually *happens* while you do it is really pretty dull. The pre-reboot part tells you what packages it's downloading. The post-reboot part tells you basically nothing at all: you just sit at the plymouth screen until it's done, at which point it reboots into your hopefully-working upgraded system. If you Esc the plymouth screen it looks like nothing is happening, but it is, just wait for the automated reboot. If you reboot manually you'll stuff it up.

artu72
11th December 2012, 01:47 PM
not an answer to your problem but a request for unrelated info - care to describe the fedup upgrade process in detail?

I have followed the fedup guide at

https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F

and steps from 5 to end in

http://fedorasolved.org/Members/fenris02/post_upgrade_cleanup

The system works fine, except openmpi modules...

AdamW
12th December 2012, 11:51 PM
I'm not sure about the openmpi issue, sorry :( Check Bugzilla? Maybe someone's come across it before? 10 to 1 it's just an issue that happens when upgrading openmpi, not to do with fedup.

artu72
13th December 2012, 10:55 AM
Solved. I have found the issue, instead of


module load openmpi-x86_64

one should issue


module load mpi/openmpi-x86_64

Of course, one should issue


module avail

in order to see available modules. I have this loading module instruction in the .bashrc file, that obviously has not been updated to new format.