Jim Kress
jimkress_35@kressworks.com
It is unreal to me that so many people refuse to use such a simple tool that can resolve so many headaches ...
On Mon Jun 21 '10 5:02pm, Miro Moman wrote
------------------------------------------
>OK. The problem was that both mpirun and mpixec where pointing to the openmpi executables and not to the mpich2 executables.
>After changing the symbolic links via update-alternatives, everything is working now.
>Time for a real example.
>Thanks a million!
>Miro
>
>
>On Mon Jun 21 '10 3:06pm, Alex Granovsky wrote
>----------------------------------------------
>>Hi,
>>Check (using ldd) that Firefly is indeed using mpich2 version of libmpich.so.1.1
>>E.g., on our systems:
>>[root@duath2]# ldd ./firefly
>> linux-gate.so.1 => (0x00370000)
>> libm.so.6 => /lib/libm.so.6 (0x492c2000)
>> libmpich.so.1.1 => /opt/mpich2/lib/libmpich.so.1.1 (0x00111000)
>> libpthread.so.0 => /lib/libpthread.so.0 (0x492f1000)
>> librt.so.1 => /lib/librt.so.1 (0x49465000)
>> libc.so.6 => /lib/libc.so.6 (0x49183000)
>> /lib/ld-linux.so.2 (0x487b4000)
>>Next, check if mpiexec you are running is of mpich2 distribution.
>>Finally, the correct command line (as was already discussed several times) would be something like:
>>mpiexec -np 16 /home/mirix/Downloads/firefly/firefly -r -f -p -stdext -i /home/mirix/jobs/test.inp -o /home/mirix/jobs/test.out -ex /home/mirix/Downloads/firefly -t /disk/scratch/firefly/job1
>>Regards,
>>Alex
>