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.
Art, We're running the LDM here on a very similar RH installation. We're up-to-date on patches as well, but have a different hardware architecture. I'm still intrigued by a potential timimg similarity and request that you make the following configuration change to time bracket the system hang; vi /etc/sysconfig/syslog 6c6 < SYSLOGD_OPTIONS="-m 0" --- > SYSLOGD_OPTIONS="-m 10" then run /etc/init.d/syslog restart Let's keep an eye out to see if this happens again. mike On Oct 12, 3:09pm, Arthur A. Person wrote: > Subject: Re: 20041011: rpc.ldmd signal 11s > Steve, > > On Tue, 12 Oct 2004, Steve Emmerson wrote: > > > Mike, > > > >> Date: Tue, 12 Oct 2004 12:50:43 -0600 > >> From: "Mike Schmidt" <address@hidden> > >> To: Steve Emmerson <address@hidden> > >> Subject: Re: 20041011: rpc.ldmd signal 11s > >> Keywords: 200408311254.i7VCsh8E018445 > > > > The above message contained the following: > > > >> The system is running RedHat's rhnsd which keeps patches up-to-date. > > > > Well then, that leaves the possibility of a software bug in the RPC or > > networking libraries, or a bug in the kernel, or a hardware bug. > > I guess that pretty much narrows it down :) > > Since I've seen this crash on another "unrelated" system running the same > OS, I guess I would conclude a hardware problem is unlikely (assuming it's > the same type of crash). That brings us down to the RedHat EL > environment. Maybe it's "over"-patched... :o > > Art.