Justin, Would you be willing to rebild the LDM with support for debugging and then obtain a core-file from the hung downstream LDM by sending it a SIGABRT the next time it happens? If so, then 1. Go to the top-level source-directory of the LDM package as the LDM user. 2. Execute the command "make distclean". 3. Ensure that the environment variable CFLAGS contains the string "-g". 4. Execute the configure(1) script. Simultaneously redirect the standard output and standard error streams to the file "configure.log". 5. Execute the command "make". Simultaneously redirect the standard output and standard error streams to the file "make.log". 6. Ensure that core-files may be created. This is user-shell dependent. The ulimit(1) utility is the standard way of testing and setting this. 7. Execute the command "ldmadmin stop". 8. Become root, execute the command "make install_setuids", and then become the LDM user. 9. Execute the command "ldmadmin start". 10. Keep an eye on the downstream LDM that's receiving NEXRAD2 data. When it hangs, send it a SIGABRT via the kill(1) utility. A core-file should be created in the top-level directory of the LDM user. Use the dbx(1) utility to obtain a stack-trace and send it to me. Regards, Steve Emmerson
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.