David, can you do these two things? 1) from the shell on the local machine, ssh to one node of the remote machine and execute a command without supplying a password (ie you have ssh authentication set up) ex. kargad> ssh amber1 uname -a Linux amber1 2.6.18-6-amd64 #1 SMP Tue Aug 19 04:30:56 UTC 2008 x86_64 GNU/Linux
2) log on the first node of the remote machine, set up a machine file listing the nodes in the remote, then run mpirun to start a parallel job on all of the server nodes kargad> ssh amber1 amber1> cat > ~/mymachinefile.txt amber1 amber2 Ctrl-D amber1> mpirun -m ~/mymachinefile.txt -np 2 /bin/uname -a Linux amber1 2.6.18-6-amd64 #1 SMP Tue Aug 19 04:30:56 UTC 2008 x86_64 GNU/Linux Linux amber2 2.6.18-6-amd64 #1 SMP Tue Aug 19 04:30:56 UTC 2008 x86_64 GNU/Linux If you can do those two things, then your command should be ssh remotemachine mpirun -np N pvserver David E DeMarle Kitware, Inc. R&D Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Thu, Jul 23, 2009 at 12:18 PM, pat marion<pat.mar...@kitware.com> wrote: > Hmm, maybe I'm misunderstanding you, but it sounds like you are giving > paraview a command to start the server and expecting paraview to log into > the remote machine to execute the command? The command will be run on your > client machine. So you need to write a shell script that will take care of > launching pvserver on the remote machine. If you are using mpi you can do > this with mpirun, and use a machinefile that lists the remote machines. > > Pat > > On Thu, Jul 23, 2009 at 12:03 PM, David Doria <daviddo...@gmail.com> wrote: >> >> On Wed, Jul 22, 2009 at 11:12 AM, Utkarsh >> Ayachit<utkarsh.ayac...@kitware.com> wrote: >> > Some other processes is already listening on the port (default 11111 >> > for pvserver), hence you are getting the error. >> > >> > Utkarsh >> > >> >> Hm, but if I run pvserver and then connect with 'manual' it works >> fine. If I try to send the 'pvserver' command, it fails with that >> socket error. I also tried it on a different port (11113) and sending >> command 'pvserver --server-port=11113' which I checked with netstat to >> ensure nothing was using it. It's the same story on this port. I can >> connect if I start the pvserver manually and use 'manual', but the >> same socket error occurs if I try to start it with the command. >> >> Thanks, >> >> David >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview