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><div><span class="gmail_quote">On 6/26/06, <b class="gmail_sendername">Dave Semeraro</b> <<a href="mailto:semeraro@ncsa.uiuc.edu">semeraro@ncsa.uiuc.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Hello,<br><br>I am running paraview 2.4 on a linux cluster ( 32 bit, myrinet connectivity<br>). I am<br>having problems reading a dem file on the cluster. The file is about<br>30Mbytes in<br>size so it isnt overly large. I can read it on a a single paraview instance
<br>on my<br>local workstation. When I try to read it on the cluster using 4 nodes I get a<br>series of errors that look like this:<br><br>1: signal 11 received, exiting..<br>1: Signal sent from unknown source.<br><br>I get this message from instance 1, 2, and 3 and paraview dies on those nodes.
<br>Has anyone else seen this kind of behavior? I dont know if this is an MPI<br>thing or<br>a paraview thing. Any ideas on how to trace the cause of this error down? I<br>know<br>these questions are rather vague and I am sorry for that. I have tested
<br>this cluster<br>set up on a small ( 50^3) hdf dataset and things behave fine. Since I can<br>read the<br>dem data on a single node I assume the reader isnt the problem. So any pointers<br>on where to look next would be a big help. Thanks.
<br><br>Regards,<br>Dave Semeraro<br><br><br>_______________________________________________<br>ParaView mailing list<br><a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br><a href="http://www.paraview.org/mailman/listinfo/paraview">
http://www.paraview.org/mailman/listinfo/paraview</a><br></blockquote></div><br>