[IDD #MWQ-760671]: Test Feed

Hi Ziv,

re:
> OK, was able to run "make root-actions" as root and successfully run the
> "configure" and "make" commands.
> 
> *output "ls -alt":*
> 
> drwxrwxr-x  2 ldm  ldm      4096 Dec 16 17:54 bin
> drwxrwxr-x  2 ldm  ldm      4096 Dec 16 17:54 lib
> drwxrwxr-x  3 ldm  ldm      4096 Dec 16 17:53 include
> drwxr-xr-x 48 ldm  ldm      4096 Dec 16 17:53 ldm-6.12.14
> drwxrwxr-x  4 ldm  ldm      4096 Dec 16 17:19 share
> drwxr-xr-x  9 ldm  ldm      4096 Dec 16 17:12 .
> drwxrwxr-x  2 ldm  ldm      4096 Dec 16 14:35 etc
> -rw-------  1 ldm  ldm      4151 Dec 15 23:03 .bash_history
> -rw-------  1 ldm  ldm      2674 Dec 15 20:37 .viminfo
> drwxr-xr-x  6 root root     4096 Dec 15 20:09 ..
> drwxrwxr-x  5 ldm  ldm      4096 Dec 15 19:56 var
> -rw-r--r--  1 ldm  ldm  14551040 Nov 13 16:22 ldm-6.12.14.tar
> -rw-r--r--  1 ldm  ldm       220 Nov 13 15:46 .bash_logout
> -rw-r--r--  1 ldm  ldm      3637 Nov 13 15:46 .bashrc
> -rw-r--r--  1 ldm  ldm       675 Nov 13 15:46 .profile

This indicates that your LDM installation is still not done according
to our _strong_ recommendations.  And, I think I know why your setup
is non-standard:

- the LDM installation from source web page instructs the user to
  gunzip the LDM compressed tarball and pipe the output to the *nix
  utility 'pax'

  The fact that you did not find a src directory under ~ldm/ldm-6.12.14
  says that 'pax' is not installed on your system OR you did not run
  the uncompression as per LDM web page instuctions which are:

http://www.unidata.ucar.edu/software/ldm/ldm-6.12.14/basics/source-install-steps.html

gunzip -c ldm-6.12.14.tar.gz | pax -r '-s:/:/src/:'

  This invocation will unpack the LDM distribution into subdirectories of
  the release directory, ~ldm/ldm-6.12.14.

  See below for my recommendation for what to do now.

re:
> *output "ls -alt bin/*"*
> 
> -rwxr-xr-x 1 root root    619 Dec 16 17:54 bin/ensureLdmhomeLinks
> -rwxr-xr-x 1 root root    156 Dec 16 17:54 bin/ensureRpcEntry
> -rwxr-xr-x 1 root root    173 Dec 16 17:54 bin/ensureServicesEntry
> -rwxr-xr-x 1 root root   1676 Dec 16 17:54 bin/ensureSyslogEntry
> -rwxr-xr-x 1 root root    612 Dec 16 17:54 bin/ensureVar
> -rwxr-xr-x 1 root root   1958 Dec 16 17:54 bin/rpmUserActions
> -rwxr-xr-x 1 root root    910 Dec 16 17:54 bin/newlog
> -rwxr-xr-x 1 root root  24014 Dec 16 17:54 bin/ulogger
> -rwxr-xr-x 1 root root  23204 Dec 16 17:54 bin/uldbutil
> -rwxr-xr-x 1 root root  57176 Dec 16 17:54 bin/ldmadmin
> -rwxr-xr-x 1 root root   7390 Dec 16 17:54 bin/ldmfail
> -rwxr-xr-x 1 root root   8993 Dec 16 17:54 bin/netcheck
> -rwxr-xr-x 1 root root   5743 Dec 16 17:54 bin/plotMetrics
> -rwxr-xr-x 1 root root   7380 Dec 16 17:54 bin/syscheck
> -rwxr-xr-x 1 root root   1029 Dec 16 17:54 bin/wasReceived
> -rwxr-xr-x 1 root root   4293 Dec 16 17:54 bin/scour
> -rwxr-xr-x 1 root root  87324 Dec 16 17:54 bin/rtstats
> -rwxr-xr-x 1 root root  15823 Dec 16 17:54 bin/regex
> -rwxr-xr-x 1 root root  95366 Dec 16 17:54 bin/pqutil
> -rwxr-xr-x 1 root root  81943 Dec 16 17:54 bin/pqsurf
> -rwxr-xr-x 1 root root  47376 Dec 16 17:54 bin/pqsend
> -rwxr-xr-x 1 root root  34055 Dec 16 17:54 bin/pqmon
> -rwxr-xr-x 1 root root  34352 Dec 16 17:54 bin/pq_test_insert
> -rwxr-xr-x 1 root root  35135 Dec 16 17:54 bin/pqinsert
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/afos -> pqing
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/feedtest -> pqing
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/ddplus -> pqing
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/hrs -> pqing
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/hds -> pqing
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/ids -> pqing
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/pps -> pqing
> lrwxrwxrwx 1 root root      5 Dec 16 17:54 bin/dds -> pqing
> -rwxr-xr-x 1 root root 147488 Dec 16 17:54 bin/pqing
> -rwxr-xr-x 1 root root  34771 Dec 16 17:54 bin/pqexpire
> -rwxr-xr-x 1 root root  21218 Dec 16 17:54 bin/pqcreate
> -rwxr-xr-x 1 root root  32427 Dec 16 17:54 bin/pqcopy
> -rwxr-xr-x 1 root root  22106 Dec 16 17:54 bin/pqcheck
> -rwxr-xr-x 1 root root  36616 Dec 16 17:54 bin/pqcat
> -rwxr-xr-x 1 root root 199200 Dec 16 17:54 bin/pqact
> -rwxr-xr-x 1 root root  36250 Dec 16 17:54 bin/notifyme
> -rwxr-xr-x 1 root root  38078 Dec 16 17:54 bin/ldmsend
> -rwxr-xr-x 1 root root  26896 Dec 16 17:54 bin/ldmping
> -rwsr-xr-x 1 root root 134967 Dec 16 17:54 bin/ldmd
> -rwsr-xr-x 1 root root  13009 Dec 16 17:54 bin/hupsyslog
> -rwxr-xr-x 1 root root  39861 Dec 16 17:54 bin/feedme
> -rwxr-xr-x 1 root root  36357 Dec 16 17:54 bin/regutil

The fact that all LDM programs are owned as 'root' indicates that
the installation is not correct.

re:
> * output **"uname -a":*
> 
> Linux ldm-downstream 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> 
> *output **"cat /etc/*-rel*" :*
> 
> Linux ldm-downstream 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> ldm@ldm-downstream:~$ cat /etc/*-rel*
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=14.04
> DISTRIB_CODENAME=trusty
> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
> NAME="Ubuntu"
> VERSION="14.04.2 LTS, Trusty Tahr"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 14.04.2 LTS"
> VERSION_ID="14.04"
> HOME_URL="http://www.ubuntu.com/";
> SUPPORT_URL="http://help.ubuntu.com/";
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

OK, now I know that you are running Ubuntu.  Some non-standard things
are needed to be done under Ubuntu to get LDM logging to work correctly.
I will address what needs to be done after there is a viable LDM
installation.

re:
> Look any better?

Unfortunately, no.

Here is what I recommend you do:

<as 'ldm'>
cd ~ldm
rm -rf bin lib include share ldm-6.12.14

gzip ldm-6.12.14     <- put the LDM back into the compressed tarball exactly
                        as it was originally downloaded

OR

rm ldm-6.12.14.tar
wget ftp://ftp.unidata.ucar.edu/pub/ldm/ldm-6.12.14.tar.gz

which pax            <- check to see if 'pax' exists.  If it does not exist,
                        get your system administrator to install it:

                        apt-get install pax

gunzip -c ldm-6.12.14.tar.gz | pax -r '-s:/:/src/:'

cd ldm-6.12.14/src

./configure && make install  <- again, two steps will need 'root' privilege

NB: the LDM should _never_ be installed as 'root'!!!!!

The result of the steps above should look more-or-less like:

cd ~ldm
ls -alt
drwxr-xr-x 9 ldm  ldm     4096 Dec 14 11:46 .
drwxrwxr-x 2 ldm  ldm     4096 Dec 14 11:46 etc
drwxrwxr-x 3 ldm  ldm     4096 Dec 12 22:28 ldm-mcidas
-rw-rw-r-- 1 ldm  ldm  2440721 Dec 12 22:14 ldm-mcidas-2012.tar.gz
-rw-r--r-- 1 ldm  ldm      735 Dec 12 22:02 .profile
drwxrwxr-x 5 ldm  ldm     4096 Dec 12 21:06 var
lrwxrwxrwx 1 ldm  ldm       11 Dec 12 21:06 runtime -> ldm-6.12.14
lrwxrwxrwx 1 ldm  ldm       15 Dec 12 21:06 include -> runtime/include
lrwxrwxrwx 1 ldm  ldm       11 Dec 12 21:06 lib -> runtime/lib
lrwxrwxrwx 1 ldm  ldm       13 Dec 12 21:06 share -> runtime/share
lrwxrwxrwx 1 ldm  ldm       11 Dec 12 21:06 bin -> runtime/bin
lrwxrwxrwx 1 ldm  ldm       11 Dec 12 21:06 src -> runtime/src
drwxr-xr-x 7 ldm  ldm     4096 Dec 12 21:05 ldm-6.12.14
-rw-r--r-- 1 ldm  ldm  4771998 Dec 12 20:51 ldm-6.12.14.tar.gz
drwxr-xr-x 6 root root    4096 Dec 12 20:35 ..
-rw-r--r-- 1 ldm  ldm      220 Dec 12 20:34 .bash_logout
-rw-r--r-- 1 ldm  ldm     3637 Dec 12 20:34 .bashrc

ls -alt bin/
mcidas@odroid:/home/ldm$ ls -alt bin/
total 1252
drwxrwxr-x 2 ldm  ldm   4096 Dec 12 22:06 .
-rwxr-xr-x 1 ldm  ldm  57215 Dec 12 22:06 ldmadmin
-rwxr-xr-x 1 ldm  ldm    619 Dec 12 21:06 ensureLdmhomeLinks
-rwxr-xr-x 1 ldm  ldm    156 Dec 12 21:06 ensureRpcEntry
-rwxr-xr-x 1 ldm  ldm    173 Dec 12 21:06 ensureServicesEntry
-rwxr-xr-x 1 ldm  ldm   1676 Dec 12 21:06 ensureSyslogEntry
-rwxr-xr-x 1 ldm  ldm    612 Dec 12 21:06 ensureVar
-rwxr-xr-x 1 ldm  ldm   1958 Dec 12 21:06 rpmUserActions
-rwxr-xr-x 1 ldm  ldm    910 Dec 12 21:06 newlog
-rwxr-xr-x 1 ldm  ldm  21871 Dec 12 21:06 ulogger
-rwxr-xr-x 1 ldm  ldm  21774 Dec 12 21:06 uldbutil
-rwxr-xr-x 1 ldm  ldm   7362 Dec 12 21:06 ldmfail
-rwxr-xr-x 1 ldm  ldm   8997 Dec 12 21:06 netcheck
-rwxr-xr-x 1 ldm  ldm   5743 Dec 12 21:06 plotMetrics
-rwxr-xr-x 1 ldm  ldm   7384 Dec 12 21:06 syscheck
-rwxr-xr-x 1 ldm  ldm   1029 Dec 12 21:06 wasReceived
-rwxr-xr-x 1 ldm  ldm   4305 Dec 12 21:06 scour
-rwxr-xr-x 1 ldm  ldm  71961 Dec 12 21:06 rtstats
-rwxr-xr-x 1 ldm  ldm  14839 Dec 12 21:06 regex
-rwxr-xr-x 1 ldm  ldm  77286 Dec 12 21:06 pqutil
-rwxr-xr-x 1 ldm  ldm  69707 Dec 12 21:06 pqsurf
-rwxr-xr-x 1 ldm  ldm  40278 Dec 12 21:06 pqsend
-rwxr-xr-x 1 ldm  ldm  27676 Dec 12 21:06 pqmon
-rwxr-xr-x 1 ldm  ldm  27683 Dec 12 21:06 pq_test_insert
-rwxr-xr-x 1 ldm  ldm  28437 Dec 12 21:06 pqinsert
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 afos -> pqing
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 feedtest -> pqing
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 ddplus -> pqing
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 hrs -> pqing
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 hds -> pqing
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 ids -> pqing
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 pps -> pqing
lrwxrwxrwx 1 ldm  ldm      5 Dec 12 21:06 dds -> pqing
-rwxr-xr-x 1 ldm  ldm 121271 Dec 12 21:06 pqing
-rwxr-xr-x 1 ldm  ldm  33125 Dec 12 21:06 pqexpire
-rwxr-xr-x 1 ldm  ldm  19727 Dec 12 21:06 pqcreate
-rwxr-xr-x 1 ldm  ldm  26535 Dec 12 21:06 pqcopy
-rwxr-xr-x 1 ldm  ldm  21003 Dec 12 21:06 pqcheck
-rwxr-xr-x 1 ldm  ldm  34250 Dec 12 21:06 pqcat
-rwxr-xr-x 1 ldm  ldm 155479 Dec 12 21:06 pqact
-rwxr-xr-x 1 ldm  ldm  30586 Dec 12 21:06 notifyme
-rwxr-xr-x 1 ldm  ldm  30840 Dec 12 21:06 ldmsend
-rwxr-xr-x 1 ldm  ldm  25115 Dec 12 21:06 ldmping
-rwsr-xr-x 1 root ldm 108515 Dec 12 21:06 ldmd
-rwsr-xr-x 1 root ldm  12412 Dec 12 21:06 hupsyslog
-rwxr-xr-x 1 ldm  ldm  33402 Dec 12 21:05 feedme
-rwxr-xr-x 1 ldm  ldm  32916 Dec 12 21:05 regutil
drwxr-xr-x 7 ldm  ldm   4096 Dec 12 21:05 ..

Note:

- the permissions on the LDM utilities

  In particular note that that the only routines owned by 'root' and
  that have 'setuid root' privilege are 'ldmd' and 'hupsyslog'.

  This is important!

- that 'bin', 'lib', 'include', 'share' and 'src' are symbolic links
  through the 'runtime' link

  The 'runtime' link setup allows for very easy intallation of a new
  version of the LDM even while an existing version is running.

Once your installation looks like my listings above, I will walk you
(or your system administrator) through the steps needed to get LDM
logging working correctly under Ubuntu Linux.

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: MWQ-760671
Department: Support IDD
Priority: Normal
Status: Closed