[LDM #DLI-905086]: Can't get logging to work with LDm 6.11.6 on VM's

Gilbert,

%$#@!

Verify that ~ldm/bin/hupsyslog is owned by root and setuid.

Verify that the operating system will honor such a utility on the disk 
partition that contains ~ldm/bin by investigating the attributes of that disk 
partition as revealed by the mount(1) utility (there's a "no root setuid" 
attribute but I don't recall its name).

Verify that the file /var/run/*syslog.pid contains the PID of the system 
logging daemon.

> On Thu, 8 Aug 2013, Unidata LDM Support wrote:
> 
> > Gilbert,
> >
> > Check the following:
> >    1. Get the logging facility that the LDM will use with the command "grep 
> > LOG_LDM ~/src/config.status";
> 
> S["LOG_LDM"]="local0"
> D["LOG_LDM"]=" LOG_LOCAL0"
> 
> >    2. Verify that an entry exists in the system logging daemon's 
> > configuration-file for the facility of step 1;
> 
> From /etc/rsyslog.conf:
> 
> # Unidata LDM:
> local0.*      /home/ldm/logs/ldmd.log
> 
> 
> >    3. Verify that the entry of step 2 logs to an existing directory;
> 
> Yep...
> 
> >    4. Verify that SELINUX is disabled with the command "selinuxenabled || 
> > echo OK".
> 
> Disabled.
> 
> (shrug)
> 
> Gilbert
> 
> *******************************************************************************
> Gilbert Sebenste                                                    ********
> (My opinions only!)                                                  ******
> Staff Meteorologist, Northern Illinois University                      ****
> E-mail: address@hidden                                  ***
> web: http://weather.admin.niu.edu                                      **
> Twitter: http://www.twitter.com/NIU_Weather                            **
> Facebook: http://www.facebook.com/niu.weather                           *
> *******************************************************************************

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: DLI-905086
Department: Support LDM
Priority: Normal
Status: Closed