This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Gilbert, > It barely stayed up for minutes before it crashed. You should be figuring > out what is causing this now. :-) I've been trying. Unfortunately, everything looks good. The pqact(1) processes are receiving a SIGSEGV when they call the regexec(3) function to match a product-identifier against a compiled regular-expression and there doesn't appear to be anything wrong with either. I also ran pqact(1) under valgrind(1) and there were no invalid memory accesses or relevant memory leaks. At this point and given the following: 1. Weather3 appears to be the only system on which this happens; 2. Nothing appears to be wrong with the code; 3. It appears to be happening with increasing frequency; and 4. Weather3 had a panic attack; I'm beginning to suspect a hardware problem; specifically, bad memory. Can the memory be checked? > ******************************************************************************* > Gilbert Sebenste ******** > (My opinions only!) ****** > Staff Meteorologist, Northern Illinois University **** > E-mail: address@hidden *** > web: http://weather.admin.niu.edu ** > Twitter: http://www.twitter.com/NIU_Weather ** > Facebook: http://www.facebook.com/niu.weather * > ******************************************************************************* Regards, Steve Emmerson Ticket Details =================== Ticket ID: KXP-405917 Department: Support LDM Priority: Normal Status: Closed