<html>
<body>
<br>
Hi Berk,<br><br>
I have more info on the signal 11 problem. I have done some more
experiments. <br>
First of all I can read the dem file using paraview on my workstation.
The workstation<br>
arch is the same as the cluster node arch. That is 32 bit dual Xeon
running Fedora<br>
core 2.0. Reading the file with paraview on my windows box ( Dell laptop
with <br>
windows xp and 2gig of ram etc ) crashes paraview. Reading the file on
the cluster<br>
with pvserver running on a single node and pvclient running in my office
crashes<br>
both pvserver and pvclient. The pvserver does not signal 11 on the node
it just exits<br>
and you get a message "All remote MPI processes have exited"
from the verbose <br>
version of mpirun. It segfaults the pvclient. One other interesting
behavior is that when<br>
I read the file on my workstation with paraview I get an error after I
close paraview. <br>
The error is:<br>
glibc detected *** free(): invalid pointer: 0xf18dd008<br><br>
<br><br>
If I convert the .dem file to a .pvd file on my workstation things are
different. All the<br>
above tests work. I can read the file on the workstation and laptop with
paraview and<br>
I can read the file with the cluster running pvserver and my workstation
as the <br>
pvclient. No errors no problems. <br><br>
I got the dem file from a guy down the hall. He<br>
does a lot of GIS work and monkeys with the dem files a lot. He told me
that a true<br>
USGS dem file is supposed to be square. It is supposed to have the same
number of<br>
points in each direction. The file he gave me is not square. I dont know
if the dem files<br>
are really supposed to be square or not. But that would help to explain
the reason <br>
why the dem reader might not work quite right if it expected a square
file and got<br>
a rectangular one instead. It might not be mallocing enough memory and
seg faulting<br>
once it tries to write the rectangular data into the square space. I will
try to get a <br>
square dem of roughly the same size as the one that fails and see if that
makes<br>
a difference. <br><br>
Dave<br>
At 10:27 AM 6/27/2006, Berk Geveci wrote:<br>
<blockquote type=cite class=cite cite="">Hi Dave,<br><br>
Have you tried with fewer nodes? 2 for example. You should be able to
attach a debugger to each node if you can reproduce the problem in a more
controlled environment. Also, have you tried converting the file to
another format (VTK for example) and reading it that way? <br><br>
-Berk<br><br>
<br>
On 6/26/06, <b>Dave Semeraro</b>
<<a href="mailto:semeraro@ncsa.uiuc.edu">semeraro@ncsa.uiuc.edu</a>
> wrote:<br>
<dl><br>
<dd>Hello,<br><br>
<dd>I am running paraview 2.4 on a linux cluster ( 32 bit, myrinet
connectivity<br>
<dd>). I am<br>
<dd>having problems reading a dem file on the cluster. The file is
about<br>
<dd>30Mbytes in<br>
<dd>size so it isnt overly large. I can read it on a a single paraview
instance <br>
<dd>on my<br>
<dd>local workstation. When I try to read it on the cluster using 4 nodes
I get a<br>
<dd>series of errors that look like this:<br><br>
<dd>1: signal 11 received, exiting..<br>
<dd>1: Signal sent from unknown source.<br><br>
<dd>I get this message from instance 1, 2, and 3 and paraview dies on
those nodes. <br>
<dd>Has anyone else seen this kind of behavior? I dont know if this is an
MPI<br>
<dd>thing or<br>
<dd>a paraview thing. Any ideas on how to trace the cause of this error
down? I<br>
<dd>know<br>
<dd>these questions are rather vague and I am sorry for that. I have
tested <br>
<dd>this cluster<br>
<dd>set up on a small ( 50^3) hdf dataset and things behave fine.
Since I can<br>
<dd>read the<br>
<dd>dem data on a single node I assume the reader isnt the problem. So
any pointers<br>
<dd>on where to look next would be a big help. Thanks. <br><br>
<dd>Regards,<br>
<dd>Dave Semeraro<br><br>
<br>
<dd>_______________________________________________<br>
<dd>ParaView mailing list<br>
<dd><a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
<dd>
<a href="http://www.paraview.org/mailman/listinfo/paraview" eudora="autourl">
http://www.paraview.org/mailman/listinfo/paraview</a><br><br>
</dl></blockquote></body>
</html>