Re: [ldm-users] LDM Logging Problems

• To: LDM-USERS <ldm-users@xxxxxxxxxxxxxxxx>
• Subject: Re: [ldm-users] LDM Logging Problems
• From: Steve Emmerson <steve@xxxxxxxxxxxxxxxx>
• Date: Thu, 21 Jul 2011 14:02:35 -0600

Phil,

The value of the SELINUX parameter in the file /etc/selinux/config must
be "disabled" in order for LDM logging to work.

Regards,
Steve

On 07/21/2011 01:45 PM, Phil Birnie wrote:
> We're still unable to get LDM logging running on our new box - thought
> we'd run some stuff by the group to see where we might be going wrong.
> 
> The LDM (6.9.8) is running fine, but we can't seem to get any kind of
> logging. 
> 
> We're running Red Hat Enterprise Linux Server release 6.1, using rsyslog
> for our logging dameon. 
> 
> In rsyslog.conf, we have the following entry: 
> 
> local0.debug                                          
>  /home/ldm/var/logs/ldmd.log
> 
> and I verified that an appropriate entry (e.g. ldm 300029 ldmd)  was
> appended to the /etc/rpc file. 
> 
> *When I start the LDM for the first time, *ldmd.log is created in
> $HOME/var/logs, but it remains empty.  If I delete it, a log file is
> created once I start the LDM again, but it's empty.
> 
> I'm assuming when one builds from source you no longer have to specify a
> home directory if it is different than /usr/local/ldm (we use /home/ldm). 
> 
> In /var/log/messages we receive the following every time we start the LDM:
> 
> Jul 21 11:11:25 twister2 rsyslogd: [origin software="rsyslogd"
> swVersion="4.6.2" x-pid="9035" x-info="http://www.rsyslog.com";] rsyslogd
> was HUPed, type 'restart'.
> Jul 21 11:11:25 twister2 kernel: Kernel logging (proc) stopped.
> Jul 21 11:11:25 twister2 kernel: imklog 4.6.2, log source = /proc/kmsg
> started.
> Jul 21 11:11:25 twister2 rsyslogd: [origin software="rsyslogd"
> swVersion="4.6.2" x-pid="9035" x-info="http://www.rsyslog.com";] (re)start
> 
> 
> I have tried  building the LDM both with and without supplying the root
> password when configuring, but it doesn't seem to make any difference --
> hupsyslog is owned by root. I'm fairly certain this is fine, but here's
> our configure directive when we build. 
> 
> [ldm@twister2 src]$ ./configure --enable-logging=local0 CC=/usr/bin/gcc
>>configure.log 2>&1
> 
> Thanks for any insight -- If I can provide any other helpful info,
> please let me know. 
> 
> - Phil
> 
> 
> 
> _______________________________________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit: 
> http://www.unidata.ucar.edu/mailing_lists/ 

• References:
  • [ldm-users] LDM Logging Problems
    • From: Phil Birnie