[Datastream #IZJ-689237]: Additional Datafeeds

Hi Jeff,

re:
> Here's a copy of ls -alt and ps -eaf
> Syslog is running.

Thanks.

Since 'syslogd' is running, there should be a /var/run/syslogd.pid file
that contains its process ID (pid).  'hupsyslog' reads that file to get the
process ID so it can send a HUP signal that tells 'syslogd' to close all open
file descriptors; reread its configuration file (/etc/syslog.conf); and then
open the various files it is configured to write to.  This mechanism is what
allows LDM log files to be "rotated" (ldmd.log.2 -> ldmd.log.3; ldmd.log.1 -> 
ldmd.log.2;
ldmd.log -> ldmd.log.1; etc.).  In order for 'hupsyslog' to send 'syslogd' a
HUP signal, it needs 'root' privilege.  Your long listing of the ~ldm/bin 
directory
shows that neither 'hupsyslog' nor 'rpc.ldmd' has setid root privilege:

-rwxrwxr-x 1 ldm mcdata 117826 Oct 14 17:39 bin/feedme
-rwxrwxr-x 1 ldm mcdata  26604 Oct 14 17:39 bin/ldmadmin
-rwxrwxr-x 1 ldm mcdata  23611 Oct 14 17:39 bin/ldmcheck
-rwxrwxr-x 1 ldm mcdata   7533 Oct 14 17:39 bin/ldmfail
-rwxrwxr-x 1 ldm mcdata 115758 Oct 14 17:39 bin/ldmping
-rwxrwxr-x 1 ldm mcdata  86832 Oct 14 17:39 bin/ldmsend
-rwxrwxr-x 1 ldm mcdata   9002 Oct 14 17:39 bin/netcheck
-rwxrwxr-x 1 ldm mcdata 117584 Oct 14 17:39 bin/notifyme
-rwxrwxr-x 1 ldm mcdata 134335 Oct 14 17:39 bin/pqact
-rwxrwxr-x 1 ldm mcdata 121598 Oct 14 17:39 bin/pqsurf
-rwxrwxr-x 1 ldm mcdata   8661 Oct 14 17:39 bin/regex
-rwxrwxr-x 1 ldm mcdata 244370 Oct 14 17:39 bin/rpc.ldmd        <- NB: no 
setuid root bit is set
-rwxrwxr-x 1 ldm mcdata 139510 Oct 14 17:39 bin/rtstats
-rwxrwxr-x 1 ldm mcdata   4208 Oct 14 17:39 bin/scour
-rwxr-xr-x 1 ldm mcdata   2158 Oct 14 17:39 bin/scriptconfig
-rwxrwxr-x 1 ldm mcdata   7389 Oct 14 17:39 bin/syscheck
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/afos -> pqing
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/ddplus -> pqing
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/dds -> pqing
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/feedtest -> pqing
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/hds -> pqing
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/hrs -> pqing
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/ids -> pqing
lrwxrwxrwx 1 ldm mcdata      5 Oct 14 17:39 bin/pps -> pqing
-rwxrwxr-x 1 ldm mcdata 102490 Oct 14 17:39 bin/pqcat
-rwxrwxr-x 1 ldm mcdata  94222 Oct 14 17:39 bin/pqcheck
-rwxrwxr-x 1 ldm mcdata  93427 Oct 14 17:39 bin/pqcreate
-rwxrwxr-x 1 ldm mcdata  97732 Oct 14 17:39 bin/pqexpire
-rwxrwxr-x 1 ldm mcdata 144891 Oct 14 17:39 bin/pqing
-rwxrwxr-x 1 ldm mcdata 107965 Oct 14 17:39 bin/pqinsert
-rwxrwxr-x 1 ldm mcdata  97659 Oct 14 17:39 bin/pqmon
-rwxrwxr-x 1 ldm mcdata 160117 Oct 14 17:39 bin/pqsend
-rwxrwxr-x 1 ldm mcdata 123572 Oct 14 17:39 bin/pqutil
-rwxrwxr-x 1 ldm mcdata   7731 Oct 14 17:39 bin/hupsyslog         <- NB: no 
setuid root bit is set
-rwxr-xr-x 1 ldm mcdata    910 Oct 14 17:39 bin/newlog

And yet, you note that you did run the 'make install_setuid' as 'root' after
the 'make install' step of the LDM 6.7.0 installation:

"I did the install_setuids, but I had to change from ldm to myself to do sudo - 
I
 don't have the actual root account password.  Does that affect it?"

The only instance that I know of where the setuid bit will not get set even
when 'root' runs the 'make install_setuids' is when the HOME directory of the
LDM is on an NFS-mounted file system.

Question:

- is the ~ldm/bin directory on a local or NFS-mounted file system

Alternatively, try the following:

<as yourself because you have sudo privilege>
sudo su -           <- become 'root'
cd ~ldm/ldm-6.7.0/src
make install_setuids

<as 'ldm'>
cd ~ldm
ls -alt bin/hupsyslog bin/rpc.ldmd

This listing should look something like:

/local/ldm% ls -alt bin/hupsyslog bin/rpc.ldmd
-rwsr-xr-x 1 root ustaff 244257 2008-10-10 10:31 bin/rpc.ldmd*
-rwsr-xr-x 1 root ustaff   7693 2008-10-10 10:31 bin/hupsyslog*

Note that the 's' bit is set for both of these programs.

By the way, in all of the above and my comments in previous emails I have 
assumed
that your 'syslogd' configuration file has been setup correctly for LDM logging.
I assumed this because you sent a ~ldm/logs/ldmd.log file in a previous email.

Questions just to make sure we are both on the same page:

- did you setup /etc/syslog.conf for LDM logging?  This would have had to been
  done by 'root'

- is there a /var/run/syslogd.pid file?  If yes, what are its read/write 
permissions?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: IZJ-689237
Department: Support Datastream
Priority: Normal
Status: Closed