[IDD #MWQ-760671]: Test Feed

Hi Ziv,

re:
> I realized that I did not add ~ldm/bin to my PATH. After doing so I was
> able to run the "notifyme" command

Very good.  That likely indicates that your LDM installation follows the
instructions on our LDM web pages ** at least ** up to a point.  See below.

> and got the following output:
> 
> Dec 16 16:19:20 notifyme[18630] NOTE: Starting Up: idd.unidata.ucar.edu: 
> 20151216161920.391 TS_ENDT {{NEXRAD2, ".*"}}
> Dec 16 16:19:20 notifyme[18630] NOTE: LDM-5 desired product-class: 
> 20151216161920.391 TS_ENDT {{NEXRAD2, ".*"}}
> Dec 16 16:19:20 notifyme[18630] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.084622 seconds
> Dec 16 16:20:10 notifyme[18630] NOTE: LDM-5 desired product-class: 
> 20151216161920.391 TS_ENDT {{NEXRAD2, ".*"}}
> Dec 16 16:20:10 notifyme[18630] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.000828 seconds
> Dec 16 16:21:00 notifyme[18630] NOTE: LDM-5 desired product-class: 
> 20151216161920.391 TS_ENDT {{NEXRAD2, ".*"}}
> Dec 16 16:21:00 notifyme[18630] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.001036 seconds
> Dec 16 16:21:50 notifyme[18630] NOTE: LDM-5 desired product-class: 
> 20151216161920.391 TS_ENDT {{NEXRAD2, ".*"}}
> Dec 16 16:21:50 notifyme[18630] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.000638 seconds
> 
> What does that mean?

It indicates that your LDM is not contacting the LDM on our top level IDD relay
cluster idd.unidata.ucar.edu.  See below for additional input that I need...

re:
> If you still want the other output, here it is:
> 
> *"ls -alt" output:*
> 
> total 14272
> drwxrwxr-x  2 ldm  ldm      4096 Dec 16 14:35 etc
> -rw-------  1 ldm  ldm      4151 Dec 15 23:03 .bash_history
> drwxr-xr-x  9 ldm  ldm      4096 Dec 15 20:37 .
> -rw-------  1 ldm  ldm      2674 Dec 15 20:37 .viminfo
> drwxrwxr-x  2 ldm  ldm      4096 Dec 15 20:17 bin
> drwxrwxr-x  2 ldm  ldm      4096 Dec 15 20:17 lib
> drwxrwxr-x  3 ldm  ldm      4096 Dec 15 20:17 include
> drwxr-xr-x 48 ldm  ldm      4096 Dec 15 20:12 ldm-6.12.14
> drwxr-xr-x  6 root root     4096 Dec 15 20:09 ..
> drwxrwxr-x  5 ldm  ldm      4096 Dec 15 19:56 var
> lrwxrwxrwx  1 ldm  ldm        11 Dec 15 19:56 runtime -> ldm-6.12.14
> lrwxrwxrwx  1 ldm  ldm        11 Dec 15 19:56 src -> runtime/src
> drwxrwxr-x  4 ldm  ldm      4096 Dec 15 19:56 share
> -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 does not look correct.  The 'bin', 'lib', 'include' and share
directories should be links through the 'runtime' link.  Why your
'src' directory' is such a link and the others are not is a
big mystery to me, but I think that it indicates that your LDM
installation is not correct.

re:
> *"env | grep PATH" output:*
> 
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/ldm/bin

This looks good.

re:
> *"ps -eaf | grep syslog" output:*
> 
> syslog    1043     1  0 Dec10 ?        00:00:01 rsyslogd
> ldm      18618 18587  0 16:14 pts/0    00:00:00 grep --color=auto syslog

OK, your OS us using 'rsyslogd'... This is needed for LDM logging.

re:
> *"~ldm/bin/ldmadmin config" output:*
> 
> The LDM-hostname is not fully-qualified.  Execute the command "regutil
> -s <hostname> /hostname" to set the fully-qualified name of the host.

OK, this is another indication that things are left to be done.

Based on my guess that your LDM installation is not quite right, I recommend
that you do the following:

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

cd ldm-6.12.14/src
make distclean

./configure && make install

NB: a couple of steps in the LDM installation requires 'root' privilege.  First,
the 'configure' process will ask for the 'root' password, and if that is not
given (the user hits Enter at the prompt), the password for 'ldm' is asked
for ** assuming that 'ldm' as sudo capability **.  If you do not have the
'root' password and 'ldm' does not have sudo capability, you will need to
get your system administrator involved in the installation of the LDM.

If you do have 'root' the 'root' password, then supply it when prompted
during the './configure && make install' invocations.  If you do not
have the 'root' password, and if 'ldm' has sudo privilege, then simply
hit the Enter key when prompted for the 'root' password and then supply
the 'ldm' password when prompted for the sudo credentials.  If neither
condition is met, then get your system administrator to run the
following after the LDM has been installed:

<as 'root'>
cd /home/ldm/ldm-6.12.14/src
make root-actions

After this is done, please send me the output of the following:

<as 'ldm'>
cd ~ldm
ls -alt

ls -alt bin/*

uname -a

cat /etc/*-rel*

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