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

[LDM #VVJ-331218]: LDM 6.11.7 Errors - exit LDM Not starting



Russ,

> I am trying to start LDM on an LINUX RHEL6 server and getting:
> 
> address@hidden ~]$ ldmadmin start
> The product-queue is OK.
> Checking pqact(1) configuration-file(s)...
> /home/ldm/etc/pqact.conf: syntactically correct
> hupsyslog: couldn't open /var/run/syslogd.pid
> new_log(): Couldn't notify system logging daemon
> start_ldm(): Couldn't rotate log files
> 
> The /home/ldm/ldmd.pid fiel is not being created and LDM is not starting...
> 
> From the unidata archives, I see that some files need SETUID bit on...I
> have them set correctly I believe.  Any help would be appreciated.
> 
> Thanks
> Russ
> _________________________________________________________________________________
> 
> address@hidden ~]$ ls -l /var/run/syslogd.pid
> -rw------- 1 root root 6 Sep 17 15:42 /var/run/syslogd.pid
> 
> address@hidden ~]$ ls -l bin/hupsyslog
> -rwsr-xr-x 1 root ops 11199 Jun 12 20:01 bin/hupsyslog
> 
> address@hidden ~]$ ls -l bin/ldmd
> -rwsr-xr-x 1 root ops 110780 Jun 12 20:01 bin/ldmd

The ownership and file-modes of hupsyslog(1) and ldmd(1) look OK.

Perhaps your operating system doesn't honor the setuid bit for programs owned 
by root in that partition. What is the output of the mount(1) command?

> address@hidden bin]$ ls -l bin/rpc.ldmd
> -rwsr-xr-x 1 root ops 244984 Apr 29 20:31 rpc.ldmd

The file "/home/ldm/bin/rpc.ldmd" shouldn't exist. Have you done something 
unusual with the installation?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VVJ-331218
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.