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

[LDM #KIY-477049]: Problem getting ldm to run...

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: [LDM #KIY-477049]: Problem getting ldm to run...
  • Date: Tue, 05 Oct 2010 08:25:27 -0600
Gerry,

> We've been suffering the aftermath of some power issues in our Lab and
> I'm now unable to get ldm (v6.8.1) to run.  Attached is the ldmd.log and
> ldmd.conf for perusal.
> 
> The system is dc-ldm2.tamu.edu. I can talk you thru access (dianos is
> down for a NIC failure right now).
> 
> Thanks, gerry
> --
> Gerry Creager -- address@hidden
> Texas Mesonet -- AATLT, Texas A&M University
> Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983
> Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843

The relevant entries in the log file are:

Oct 05 14:04:13 dc-ldm2 rpc.ldmd[17228] NOTE: Starting Up (version: 6.8.1; 
built: Dec  8 2009 05:46:30)
...
Oct 05 14:04:16 dc-ldm2 rpc.ldmd[17228] NOTE: child 17232 terminated by signal 
25: pqact -vf DDPLUS|IDS etc/pqact.metar.conf 
...
Oct 05 14:04:17 dc-ldm2 rpc.ldmd[17228] NOTE: Killing (SIGTERM) process group 

On my Linux system, signal 25 means that the file-size limit was exceeded. I 
suspect, therefore, that a FILE action for metars failed for this reason. I 
would also check the available disk space.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: KIY-477049
Department: Support LDM
Priority: Normal
Status: Closed