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.
>To: address@hidden >From: Gilbert Sebenste <address@hidden> >Subject: Re: 20000817: Upgrade to 5.1.2 non-beta blew up... >Organization: Northern Illinois University Gilbert, > I could have done something wrong, and I'm looking into it right now, but > ldm-5.1.2 non-beta crashed and burned on my Linux Redhat box. It started, > but then killed itself seconds after starting; an ldmadmin watch resulted > in nothing but a segmentation fault. Will stay with the beta version until > the official version gets fixed. Boy, does that sound weird... You may have found a bug. Do you still have the core file from the segmentation fault? If so, do you know how to use a debugger to get a traceback, so we can find out where pqutil (which is what ldmadmin watch invokes) was when it got the segmentation fault? If you can send me a traceback, I'd appreciate it. Or, if you can describe exactly how to reproduce the problem, that would help. This may be a bug that depends on when ldmadmin watch is started relative to when the first product arrives, but that's just speculation. ... Thanks for the bug report. --Russ