From: William S. <wg...@ch...> - 2005-11-16 15:19:47
|
Hi Malcolm: It turns out with a separate build of lammpi it all works as advertised, so the problem is with the package that currently exists in the fink package management system. I've got the maintainer working on the problem too, so it should be sorted out. The good news is that there is NOT a problem on the apbs side of things. For some reason, if lamd is built against dynamic rather than static libraries, it gives this error, and this is apparently a known issue (thanks to your google suggestion, it is now known to me, too). (Passwordless ssh works fine, and I was also having the problem with just localhost.) Many thanks, and also, sorry to bother you with a problem that it turns out had nothing to do with apbs. Bill On Nov 16, 2005, at 7:14 AM, Malcolm Tobias wrote: > On Tuesday 15 November 2005 04:20 pm, William Scott wrote: > >>> Maybe there's a configuration problem and when you invoke lamboot >>> it's exiting right away? Is there a flag to start lamboot with >>> verbose >>> output? >> >> -d >> >> http://www.chemistry.ucsc.edu/~wgscott/temp/verbose_output > > I'm kind of guessing here, but it looks like the problem might be > that you > can't ssh into the machine without a password. When you run > mpirun, it will > try to open a new shell for each process. It used to use rsh, but > can also > use ssh. It looks like your LAM was configured for ssh: > > n-1<12384> ssi:boot:rsh:agent: /usr/bin/ssh -x > > You can test whether your machine allows you to ssh without a > password by > running: > > ssh your_machine_name "hostname" > > It should echo back the hostname without asking for a password. If > it does > ask for a password, see: > > http://www.lam-mpi.org/faq/category4.php3#question15 > > Good luck ;-) > > Malcolm > > -- > Malcolm Tobias > 314.362.1594 |