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.
Karen, > > Were the two servers also feeding from each other? > > No, they do not feed from each other. > They are virtually identical -- hardware, version, OS, patch levels, > etc. But they are also identical to 2 other servers I have with the > exception of their data feeds, and those did not have a problem. > > My original thought was that they both got some kind of bad/garbled > packet since the first problem was simultaneous. But the second > instance where they were separated by several hours made that seem > unlikely. The several hour separation between the two segfaults does make it unlikely to be caused by a particular data-product. > I suppose they could have bad memory, since they were ordered together > it would likely have come out of the same lot -- but I haven't done any > memory tests as yet. > > I can say that according to my monitoring system the statistics on cpu > load, memory usage, etc were all stable prior to the segfaults. No > spikes in memory, no swapping, nothing abnormal. Do you have the disk space to put the LDM into verbose logging mode? Is there anything relevant in the LDM log files? May we log onto the systems in question as the LDM user? > -- > ------------------------------------------- > > There are 2 kinds of people in the world: > > 1) Those who can extrapolate from incomplete data. > > ------------------------------------------- > address@hidden > > Phone: 405-325-6982 > Cell: 405-834-8559 > INDUS Corporation > National Severe Storms Laboratory Regards, Steve Emmerson Ticket Details =================== Ticket ID: VXR-367622 Department: Support LDM Priority: Normal Status: Closed