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.
Stonie, > Steve - odd, indeed. > > I have the exact same calls on a machine running the same 6.10.1 on a SD > State machine in Brookings, and there are no indications in the logs of > any segfaults. Interestingly enough, the pqinserts on this machine that > cause the segfault are ultimately successful, as the data does get > pushed onto the queue - so the segfault occurs after the actual insert. > > The one difference between the SD State machine and ours - they are on > CentOS 5.7, and we are on CentOS 6.3. > > I will play around some more with it - had no idea that it was happening > until my tripwire sessions sent me an email when I started inserting > data on that particular machine. > > In your shoes, I wouldn't worry about it. It does not appear to be a > show stopper, and may be an OS conflict that will go away with the next > libc update. Curiouser and curiouser. It does sound like an O/S thing. Please keep me posted. > > Stonie > > -- > Stonie Cooper, Systems Manager > High Plains Regional Climate Center > School of Natural Resources > University of Nebraska - Lincoln > 704 Hardin Hall > 3310 Holdrege Street > Lincoln, NE 68583-0997 U.S.A > "There's nothing wrong with Quiet"-Jeremiah Johnson > phone: 402.472.9180 > fax: 402.472.8763 > address@hidden > www.hprcc.unl.edu > www.rcc-acis.org > snr.unl.edu Regards, Steve Emmerson Ticket Details =================== Ticket ID: RGW-234589 Department: Support LDM Priority: Normal Status: Closed