[LDM #BBO-672523]: LDM at NOAA

Russ,

> We are having an issue where we are getting error messages starting LDM
> on our RHEL6 server and LDM will not start.
> 
> LDM has been running fine forever, and we rebooted the system with a new
> kernel.  We rebooted back to the old kernel but still getting the same
> error.

It odd that reverting to the previous kernel didn't fix the problem. Were there 
latent patches to the previous kernel that the LDM didn't see until the system 
was rebooted with that kernel?

> ldm@geoprod4t) $ ldmadmin start
> 
> The product-queue is OK.
> Checking pqact(1) configuration file(s)...
>          /home/ldm/pqact.conf: syntactically correct
> hupsyslog: couldn't open /var/run/syslog.pid
> new_log(): Couldn't notify system logging daemon
> start_ldm(): Couldn't rotate log files

The error messages indicate that the start-up procedure for the LDM failed 
because
    1. it couldn't rotate its log files (i.e., rename them and create a new 
empty one); because
    2. it couldn't get the process-ID (PID) of the system logging daemon; 
because
    3. hupsyslog(1) couldn't open the file that should have contained that PID 
(/var/run/syslog.pid).

Does the file "/var/run/syslog.pid" exist? If so, what are its protections?

Is the hupsyslog(1) LDM utility owned by root and is it setuid?

Is the same system logging daemon as before being used (e.g., "syslogd", 
"rsyslogd")?

Was the system logging daemon running when the attempt to start the LDM was 
made?

Is the PID of the system logging daemon put into the file "/var/run/syslog.pid"?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: BBO-672523
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.