NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Steve and Co., We here at JSC have both a 6.6.5 and a 6.11.6 installation. The 6.11.6 went down (no core, sorry) and the 6.6.5 stayed up (in spite of massive amounts of 'Gap in SBN' messages that we get routinely on that system). The errors that were reported on missing parameters have been happening here for several weeks if not longer, but I hadn't had the time to try to figure out why. Those errors were reported here when our LDM failed as well. Brice Brice Biggerstaff Johnson Space Center Weather Decision Support System MIDDS Software Support Lead 281-853-3011 (w) 713-764-2601 (p) 7137642601@xxxxxxxxxxxxxxx<mailto:7137642601@xxxxxxxxxxxxxxx> (alpha pager for text and email) Res Confacti Erimus "We Get Things Done!" From: noaaport-bounces@xxxxxxxxxxxxxxxx [mailto:noaaport-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Steven Emmerson Sent: Tuesday, February 25, 2014 11:51 AM To: Patrick L. Francis Cc: noaaport@xxxxxxxxxxxxxxxx Subject: EXTERNAL: Re: [noaaport] [ldm-users] LDM crashed this morning on satelliteingesters Patrick, What would help is a stack trace of the core file of the crashed program. I try to install the LDM systems here with support for debugging. The one that crashed here has debugging enabled but the LDM user had a core file size limit of 0 -- so no core file was produced (I've since corrected that situation). If anyone out there has a stack trace of the core file produced by the crash, then please send it to me. --Steve On Tue, Feb 25, 2014 at 10:39 AM, Patrick L. Francis <wxprofessor@xxxxxxxxx<mailto:wxprofessor@xxxxxxxxx>> wrote: Interestingly, our Solaris ingest systems were unaffected -- probably due to a different layout of the program's memory. steve... if it might help both my systems are debian
noaaport
archives: