Segmentation Fault During Analysis

[MrRogers1987]

I have been trying to debug a model that has been giving me some issues for the past couple days and so far have not come up with any solutions. The model is reasonably large (~400-500 MB) and involves some fairly complicated connections between components in order to release specific DOF at certain interface locations. Currently I have the model broken down into essentially three distinct components: the main body, the secondary body, and the fittings used to connect the two. All runs have been done in NX Nastran 9.0.

When I try to run the full model the run just stops after the boundary conditions and loads are applied (this step finishes). After this he log file shows "forrtl: severe (174): SIGSEGV, segmentation fault occurred". When I run each component individually there are no issues. As soon as I try to connect two of them the analysis fatals with the same error. I tried running with ILP and specifying more memory, thinking that it was just a resource issue on the solver, but no help there.

I have checked the connections multiple times now and am fairly certain that is not the source of the issue. I'm not sure what else would be causing this though since it only happens when all the models are connected and run together. Has anyone else run into this error and determined the root cause?

 

[BlasMolero]

Dear MrRogers,
Take a look to the *.F06 file, there you will see the reason of the error, search for FATAL word. Or post here your *.LOG, *.F04 and *.F06 files and we can take a look to them.
Best regards,
Blas.

~~~~~~~~~~~~~~~~~~~~~~
Blas Molero Hidalgo
Ingeniero Industrial
Director

IBERISA
48004 BILBAO (SPAIN)
WEB:

http://www.iberisa.com

Blog de FEMAP & NX Nastran:

http://iberisa.wordpress.com/

 

[MrRogers1987]

Blas,

There had been nothing useful in the .f06 other than a similar error message about segmentation error. The thing that ended up resolving the issue was running the analysis in NX Nastran 8.5 ILP instead of 9.0. I'm still not entirely sure what the issue was, but this seemed to do the trick. Just wanted to close the loop on this in case it helps someone else down the line!