Rob, I agree with what Dave Love says. The distro packaged OpenMPI packages should set things up OK for you. I guess that is true on the head node, but from what you say maybe the cluster compute nodes are being installed some other way.
On HPC clusters, when you are managing alternate packages - and you do! - then the common method is to use the 'Modules' environment to set those paths and library include paths. http://modules.sourceforge.net/ May I ask though - what is the purpose of your cluster? If you are using Ubunutu, have you looked at Qlustar? https://www.qlustar.com/ Might save you a whole lot of heartache! On 26 April 2016 at 17:28, Dave Love <d.l...@liverpool.ac.uk> wrote: > "Rob Malpass" <l...@getiton.myzen.co.uk> writes: > > > Hi > > > > > > > > Sorry if this isn't 100% relevant to this list but I'm at my wits end. > > > > > > > > After a lot of hacking, I've finally configured openmpi on my Ubuntu > > cluster. I had been having awful problems with not being able to find > the > > libraries on the remote nodes but apparently the workaround is to use > > ld.conf.so.d/*.conf > > That shouldn't be necessary with Debian/Ubuntu packages; there's a > default MPI set through alternatives. If that isn't working, make an > Ubuntu bug report, but it seems OK in Debian stable. > > If you're not using a packaged version (why?), the usual way to set the > environment is with environment modules (the environment-modules > package). > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/04/29036.php >
