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.
On Mon, 22 Nov 1999, McIDAS wrote: > Rob, > thanks for the tip. Executing the command yielded some pretty > interesting output: > > --------------------------------------------------------------------- > ldm@breeze 1% bin/rpc.ldmd -vl - etc/ldmd.conf > Nov 22 19:59:03 rpc.ldmd[21390]: Starting Up (built: Aug 22 1997 > 12:07:40) > Nov 22 19:59:03 aqua[21329]: run_requester: Starting Up: > aqua.atmos.uah.edu > Nov 22 19:59:03 striker[21395]: run_requester: Starting Up: > striker.atmos.albany.edu > Nov 22 19:59:04 udp.ldmd[21382]: Starting Up > Nov 22 19:59:30 aqua[21329]: pq_sequence: xdr_prod_info() failed > Nov 22 19:59:30 striker[21395]: pq_sequence: xdr_prod_info() failed > Nov 22 19:59:30 aqua[21329]: pq_last: seq:I/O error (errno = 5) > Nov 22 19:59:30 aqua[21329]: run_requester: 19991122185903.945 TS_ENDT > {{UNIDATA, ".*"},{FSL2|MCIDAS, ".*"}} > Nov 22 19:59:30 striker[21395]: pq_last: seq:I/O error (errno = 5) > Nov 22 19:59:30 striker[21395]: run_requester: 19991122185903.951 > TS_ENDT {{NLDN, ".*"}} Karla, The first thing to check is that your machine time is correct. Also, comment out the "exec pqact ...." line in your ldmd.conf file. I would also comment out the other request lines in the ldmd.conf until it runs correctly. What type of machine is this? What's the output of top? Robb... > Nov 22 19:59:36 rpc.ldmd[21390]: child 21416 terminated by signal 6 > Nov 22 19:59:36 rpc.ldmd[21390]: Killing (SIGINT) process group > Nov 22 19:59:36 rpc.ldmd[21390]: Interrupt > Nov 22 19:59:36 rpc.ldmd[21390]: Exiting > Nov 22 19:59:36 striker[21395]: Interrupt > Nov 22 19:59:36 striker[21395]: Exiting > Nov 22 19:59:36 aqua[21329]: Interrupt > Nov 22 19:59:36 aqua[21329]: Exiting > Nov 22 19:59:36 udp.ldmd[21382]: Interrupt > Nov 22 19:59:36 udp.ldmd[21382]: Exiting > Nov 22 19:59:36 rpc.ldmd[21390]: Terminating process group > ldm@breeze 2% > > --------------------------------------------------------------------- > I got this output in less that a minute. My guess is that the data > stream is failing (but this wouldn't cause it to die) or something is > externally killng it. > Karli > > Robb Kambic wrote: > > > > Karli, > > > > Run the ldm from home on the command line with the messages to the > > screen, ie. > > > > % bin/rpc.ldmd -vl - etc/ldmd.conf > > > > This should give us a clue of the problem. > > > > Robb... > > > > On Fri, 19 Nov 1999, Karli Lopez wrote: > > > > > Rob, > > > > > > Hello again, I tried deleting the queue but unfortunately that wasn't > > > the problem. So I tried getting it into verbose mode by typing : > > > kill -USR2 `cat ldmd.pid` > > > but I got a "can't find pid" error. Thinking at the moment that -USR2 > > > stood for the username I typed: > > > kill -ldm `cat ldmd.pid` > > > which apparently worked though I got a list of what seemed to me some > > > unix commands in uppercase (or perhaps verbose information?) but when I > > > checked the pid's the process wasn't running. > > > Now, whenever I start ldm, it runs for a few seconds but immeadetly > > > after, it crashes. However the ldmd.log file is completely empty, so is > > > the ldm-mcidas.log file, after the run. So I don't have a chance to get > > > it back to the original mode. > > > So I am completely confused as to what the problem might be. Thanks > > > > > > Karli Lopez > > > > > > > Received: from wcfields.unidata.ucar.edu > > > > (wcfields.unidata.ucar.edu [128.117.140.8]) > > > > by breeze.uprm.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) > > > > via ESMTP id QAA18258 for ; Mon, > > > > 08 Nov 1999 16:39:02 +0000 (GMT) > > > > Received: from localhost (rkambic@localhost) by > > > > wcfields.unidata.ucar.edu > > > > (UCAR/Unidata) with ESMTP id JAA26249; Mon, 08 Nov 1999 09:38:37 -0700 > > > > (MST) > > > > Date: Mon, 08 Nov 1999 09:38:37 -0700 (MST) > > > > From: Robb Kambic > > > > Subject: Re: 19991108: I need some assistance > > > > In-reply-to: <address@hidden> > > > > To: McIDAS > > > > Cc: support-ldm , > > > > Anne Wilson > > > > Message-id: > > > > MIME-version: 1.0 > > > > Content-type: TEXT/PLAIN; charset=US-ASCII > > > > Content-transfer-encoding: 7BIT > > > > X-Authentication-warning: wcfields.unidata.ucar.edu: rkambic owned > > > > process > > > > doing -bs > > > > > > > > On Mon, 8 Nov 1999, Unidata Support wrote: > > > > > > > > > >To: address@hidden > > > > > >From: McIDAS > > > > > >Subject: I need some assistance > > > > > >Organization: McIDAS proyect > > > > > >Keywords: 199911061941.MAA06721 > > > > > > > > > > I'm sorry that this message may be too informal (and perhaps vague), > > > > > but > > > > > I am short on time at the moment. For the past couple of months we've > > > > > been having a weird problem with LDM where it shuts down for no > > > > > apparent > > > > > reason and if you start it, will shut itself down the next day. Now, > > > > > I > > > > > haven't had the opportunity to get into it since It has been very hard > > > > > lately to access this computer until now. I have no idea what it could > > > > > be. Any assistance would be gladly appreciated. > > > > > > > > Karli, > > > > > > > > It may be a corrupt queue causing the problem. I would do: > > > > > > > > % ldmadmin stop > > > > % ldmadmin delqueue > > > > % ldmadmin mkqueue > > > > % ldmadmin start > > > > > > > > If this doesn't solve the problem, run the ldm in verbose mode. Look in > > > > the HOME directory for file ldmd.pid, then do: > > > > > > > > % kill -USR2 `cat ldmd.pid` > > > > > > > > This will put the ldm in verbose mode, do it again and it puts the ldm > > > > into debug mode. Do it once more, returns the ldm to silent mode. A > > > > word > > > > of caution, your log files will be much larger because every ldm action > > > > is > > > > written to the ldm file. So when the ldm dies, you should be able to > > > > find > > > > out the problem. > > > > > > > > Robb... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Karli Lopez > > > > > > > > > > -- > > > > > > > > > > ==================================================================== > > > > > Amos Winter address@hidden > > > > > Director > > > > > Puerto Rico Climatology Center > > > > > P.O. Box 9013 > > > > > Department of Marine Sciences phone: (787) 265-5416 > > > > > University of Puerto Rico - Mayaguez fax: (787) 265-2195 > > > > > Mayaguez, PR 00681-9013 > > > > > > > > > > > > > =============================================================================== > > > > Robb Kambic Unidata Program Center > > > > Software Engineer III Univ. Corp for Atmospheric > > > > Research > > > > address@hidden WWW: http://www.unidata.ucar.edu/ > > > > =============================================================================== > > > > > > > > > > > > > > > =============================================================================== > > Robb Kambic Unidata Program Center > > Software Engineer III Univ. Corp for Atmospheric > > Research > > address@hidden WWW: http://www.unidata.ucar.edu/ > > =============================================================================== > > -- > > ==================================================================== > Amos Winter address@hidden > Director > Puerto Rico Climatology Center > P.O. Box 9013 > Department of Marine Sciences phone: (787) 265-5416 > University of Puerto Rico - Mayaguez fax: (787) 265-2195 > Mayaguez, PR 00681-9013 > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================