[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20051121:Strange LDM 6.4.3 problem ldmadmin stop

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.

  • Subject: Re: 20051121:Strange LDM 6.4.3 problem ldmadmin stop
  • Date: Mon, 21 Nov 2005 13:06:30 -0700
Hi Harry,

> To: address@hidden
> From: Harry Edmon <address@hidden>
> Subject: Strange LDM 6.4.3 problem
> Organization: UCAR/Unidata
> Keywords: 200511211924.jALJO17s000656

The above message contained the following:

> I did a "ldmadmin stop" on my Linux system running LDM 6.4.3, and none 
> of the processes stopped.  I did a trace on the main rpc.ldmd process, 
> and it never reacted to the kill signal.  I did a "kill -9" on the main 
> rpc.ldmd process, it died but none of the children died.  I finally had 
> to do "killall rpc.ldmd", "killall pqact" and "killall rtstats" to get 
> everything to go away.  I have not seen this problem with 6.4.2.

Anything useful in the log file?  Was there any indication that the
top-level LDM server received the initial SIGTERM?

Regards,
Steve Emmerson

> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.