[petsc-users] SAWs does not work in parallel on my laptop

[Barry Smith]

 -saws_options doesn't work in parallel. Doing this right is really hard because different options may be checked on different communicators

-ts_monitor_saws -snes_monitor_saws etc work in parallel but probably only if the communicator is over all processes

-stack_view works in parallel but only shows the stack on process 0.

  The SAWs browser only communicates with process 0 and SAWs itself does not do any MPI in the application code. 

> On Nov 10, 2016, at 2:21 PM, Tobin Isaac <tisaac at uchicago.edu> wrote:
> 
> 
> I tried running the first example with SAWs, and it works with one
> process, but not in parallel.  This is a minimal install using the
> downloaded mpich version.  Any suggestions?
> 
> /home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/bin/mpicc -o ex1.o -c -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fvisibility=hidden -g3   -I/home/tisaac/Projects/petsc/include -I/home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/include    `pwd`/ex1.c
> /home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/bin/mpicc -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fvisibility=hidden -g3  -o ex1 ex1.o  -Wl,-rpath,/home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/lib -L/home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/lib  -lpetsc -llapack -lblas -lX11 -lssl -lcrypto -Wl,-rpath,/home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/lib -lSAWs -lpthread -lm -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/4.6 -L/usr/lib/gcc/x86_64-linux-gnu/4.6 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -lmpifort -lgfortran -lm -lgfortran -lm -lquadmath -lm -lmpicxx -lstdc++ -Wl,-rpath,/home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/lib -L/home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/lib -Wl,-rpath,/usr/lib/gcc/x86_64-linux-gnu/4.6 -L/usr/lib/gcc/x86_64-linux-gnu/4.6 -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -Wl,-rpath,/lib/x86_64-linux-gnu -L/lib/x86_64-linux-gnu -Wl,-rpath,/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -ldl -Wl,-rpath,/home/tisaac/Projects/petsc/arch-linux2-c-debug-mpich/lib -lmpi -lgcc_s -ldl 
> /bin/rm -f -f ex1.o
> [0] PetscGetHostName(): Rejecting domainname, likely is NIS alembic.(none)
> [0] PetscGetFileStat(): System call stat() succeeded on file /home/tisaac/Projects/petsc/share/petsc/saws/js
> [0] PetscTestOwnership(): System call access() succeeded on file /home/tisaac/Projects/petsc/share/petsc/saws/js
> [0] PetscInitialize(): PETSc successfully started: number of processors = 2
> [0] PetscGetHostName(): Rejecting domainname, likely is NIS alembic.(none)
> [0] PetscInitialize(): Running on machine: alembic
> [1]PETSC ERROR: #1 PetscLogInitialize() line 229 in /home/tisaac/Projects/petsc/src/sys/logging/plog.c
> [1]PETSC ERROR: #2 PetscInitialize() line 891 in /home/tisaac/Projects/petsc/src/sys/objects/pinit.c
> [0] PetscSAWsBlock(): Blocking on SAWs
> 
> ===================================================================================
> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
> =   PID 21665 RUNNING AT alembic
> =   EXIT CODE: 14
> =   CLEANING UP REMAINING PROCESSES
> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
> ===================================================================================
> <configure.log>