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

Re: ldm won't start

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: ldm won't start
  • Date: Tue, 13 Sep 2005 14:36:14 -0600
Gabe,

>Date: Tue, 13 Sep 2005 16:28:39 -0400 (EDT)
>From: Gabe Langbauer <address@hidden>
>Organization: Ohio State University
>To: Steve Emmerson <address@hidden>
>Subject: Re: ldm won't start 

The above message contained the following:

> [ldm@polarmet12 ldm]$  ldmadmin delqueue && ldmadmin mkqueue -f && 
> ldmadmin start
> The product-queue is OK.
> /home/ldm/etc/pqact.conf is syntactically correct
> Starting the LDM server...
> [ldm@polarmet12 ldm]$ ldmadmin watch
> Sep 13 20:31:16 UTC polarmet12.mps.ohio-state.edu : There is no LDM server 
> running
> [ldm@polarmet12 ldm]$ ldmadmin stop
> Flushing the LDM product-queue to disk...
> Stopping the LDM server...
> kill 30896: No such process
> 
> Log file indicates the same problem as before:
> [ldm@polarmet12 logs]$ more ldmd.log
> Sep 13 20:31:11 polarmet12 rpc.ldmd[30896] NOTE: Starting Up (version: 
> 6.4.1; built: Sep 13 2005 14:31:11)
> Sep 13 20:31:11 polarmet12 rpc.ldmd[30896] ERROR: pq_open failed: 
> /home/ldm/data/ldm.pq: Permission denied
> Sep 13 20:31:11 polarmet12 rpc.ldmd[30896] NOTE: Terminating process group
> Sep 13 20:31:16 polarmet12 ldmping[30904] ERROR: SVC_UNAVAIL   0.000621 
> 0   localhost    RPC: Program not registered
> Sep 13 20:31:24 polarmet12 ldmping[30913] ERROR: SVC_UNAVAIL   0.001814 
> 0   localhost    RPC: Program not registered

Very bizarre, indeed!

What does the following command now show

    ls -l ls -l /home/ldm/data/ldm.pq

May I log onto polarmet12 as the LDM user in order to diagnose this
problem?

Regards,
Steve Emmerson