RE: [Pympi-users] pyMPI interactively
Status: Alpha
Brought to you by:
patmiller
From: Julian C. <rjc...@cs...> - 2005-09-26 04:12:52
|
I had this problem with pyMPI-2.0b0, at which point I was directed to use the CVS version, but the fix should be in b4. The other missing piece is the compile options, in that configure needs to be run: ./configure --prefix=/usr --with-isatty Obviously --prefix=/usr depends on where the ultimate install will be, but --with-isatty makes sure that the interactive console will work. There are some posts in November 2004 (see Julian cook, Mike Steder) that discuss a similar problem. There is another configure option with regard to Newlines, but normally that is not needed. Otherwise on Monday Pat Miller should be able to give better advice. Julian -----Original Message----- From: pym...@li... [mailto:pym...@li...]On Behalf Of db...@br... Sent: Sunday, September 25, 2005 11:41 PM To: rjc...@cs... Cc: db...@br...; pym...@li... Subject: RE: [Pympi-users] pyMPI interactively Thanks for some assistance. Details below. > Does pyMPI run correctly when you startup interactively without running > sum.py? > > i.e. in your case you should get: > > $ mpirun -np 3 pyMPI > > Python 2.4 (pyMPI 2.1b4) on sunos5 > Type "help", "copyright", "credits" or "license" for more information. > Python 2.4 (pyMPI 2.1b4) on sunos5 > Type "help", "copyright", "credits" or "license" for more information. > Python 2.4 (pyMPI 2.1b4) on sunos5 > Type "help", "copyright", "credits" or "license" for more information. > >>>> No, I can never get a prompt. Every time Python gets to where it should give the prompt, it either hangs till I control+c and gives the following error, or just gives the error immediately: pyMPI aborting on untrapped fatal signal 11 (SIGSEGV) on rank 0 Fatal Python error: PyThreadState_Get: no current thread ---------------------------------------------------------------------------- - One of the processes started by mpirun has exited with a nonzero exit code. This typically indicates that the process finished in error. If your process did not finish in error, be sure to include a "return 0" or "exit(0)" in your C code before exiting the application. PID 944 failed on node n0 (10.0.0.1) due to signal 6. ---------------------------------------------------------------------------- - I thought I'd try the unittests. I had to change line 231 in PyMPITest.py to: cart = mpi.cart_create((1,int(mpi.procs)), (1,1), 0) and then they all ran without errors. So whatever is causing the crash, the unittests are testing for it. > Obviously my copy is a later version and on Solaris, but b3 should work > correctly as well. Also, what is inside sum.py? It doesn't really matter, as this happens with any python program, including an empty one, and the fractal.py example program. It must be that the Pythons are talking to each other correctly... if anyone has any ideas of other things to test/try please let me know. Thanks! -Doug > Julian Cook > -----Original Message----- > From: pym...@li... > [mailto:pym...@li...]On Behalf Of > db...@br... > Sent: Sunday, September 25, 2005 4:55 PM > To: pym...@li... > Subject: [Pympi-users] pyMPI interactively > > > Greetings pyMPI-users, > > I'm working on some major upgrades, moving from pyMPI-1.3a1 running on > RedHat 9 to pyMPI-2.4b3 running Fedore Core 4. I'm running > lam-7.1.1-7.FC4. I'm using rsh on a private network. Once I got the proper > version of rsh running on the machines (had to remove kerberos "rpm -e > krb5-workstation"), most things generally work the same as before. For > example: > > [dblank@bw40 mpi]$ mpirun -np 3 pyMPI sum.py > 24499996500000 > > But, I used to be able to also run Python interactively. If I try with the > -i flag, I get an error, or it hangs: > > [dblank@bw40 mpi]$ mpirun -np 3 pyMPI -i sum.py >>>> > 24499996500000 > pyMPI aborting on untrapped fatal signal 11 (SIGSEGV) on rank 0 > Fatal Python error: PyThreadState_Get: no current thread > -------------------------------------------------------------------------- -- > - > One of the processes started by mpirun has exited with a nonzero exit > code. This typically indicates that the process finished in error. > If your process did not finish in error, be sure to include a "return > 0" or "exit(0)" in your C code before exiting the application. > > PID 28595 failed on node n0 (10.0.0.40) due to signal 6. > -------------------------------------------------------------------------- -- > - > > Has something changed that prevents me from running interactively that > way? I looked through the archives but didn't see anything. Maybe I have > something configure incorrectly? > > Thanks for any hints, > > -Doug > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Pympi-users mailing list > Pym...@li... > https://lists.sourceforge.net/lists/listinfo/pympi-users > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Pympi-users mailing list > Pym...@li... > https://lists.sourceforge.net/lists/listinfo/pympi-users > ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Pympi-users mailing list Pym...@li... https://lists.sourceforge.net/lists/listinfo/pympi-users |