[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #JLH-115818]: 13.6



Patrick,

> Here is what happened the morning.. the configure and make performed
> beautifully, however when we look at the directory tree and the output
> from make, notice runtime is still referencing the old install...

By design, updating an LDM installation won't "throw the runtime switch".
That step must be done manually as mentioned by the documentation at

    http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/activating.html

Note that it's only necessary to change the "runtime" symbolic-link after an
update. We often execute commands like the following:

    ldmadmin stop && rm runtime && ln -s ldm-6.13.6 runtime && ldmadmin start

> going
> to add our old guard fixes again to repair, but thought you should
> see... box is debian jessie
> 
> Enter root's password (or don't): Password:
> make[4]: Entering directory `/home/ldm/ldm-6.13.6/src'
> chown root /home/ldm/ldm-6.13.6/bin/ldmd
> chmod 4755 /home/ldm/ldm-6.13.6/bin/ldmd
> chown root /home/ldm/ldm-6.13.6/bin/hupsyslog
> chmod 4755 /home/ldm/ldm-6.13.6/bin/hupsyslog
> if test -f /home/ldm/ldm-6.13.6/bin/noaaportIngester; then \
> chown root /home/ldm/ldm-6.13.6/bin/noaaportIngester; \
> chmod 4755 /home/ldm/ldm-6.13.6/bin/noaaportIngester; \
> fi
> if test -f /home/ldm/ldm-6.13.6/bin/fileIngester; then \
> chown root /home/ldm/ldm-6.13.6/bin/fileIngester; \
> chmod 4755 /home/ldm/ldm-6.13.6/bin/fileIngester; \
> fi
> if test -f /home/ldm/ldm-6.13.6/bin/dvbs_multicast; then \
> chown root /home/ldm/ldm-6.13.6/bin/dvbs_multicast; \
> chmod 4755 /home/ldm/ldm-6.13.6/bin/dvbs_multicast; \
> fi
> ./ensureRpcEntry
> ./ensureServicesEntry
> make[4]: Leaving directory `/home/ldm/ldm-6.13.6/src'
> 
> make[3]: Leaving directory `/home/ldm/ldm-6.13.6/src'
> make[2]: Leaving directory `/home/ldm/ldm-6.13.6/src'
> make[1]: Leaving directory `/home/ldm/ldm-6.13.6/src'
> address@hidden:~/ldm-6.13.6/src$ cd
> address@hidden:~$ ls -la
> total 10656
> drwxr-xr-x 10 ldm  ldm     4096 Feb  4 11:34 .
> drwxr-xr-x  4 root root    4096 Oct 20  2014 ..
> -rw-------  1 ldm  ldm     5411 Jan 23 19:00 .bash_history
> -rw-r--r--  1 ldm  ldm      220 Oct 20  2014 .bash_logout
> -rw-r--r--  1 ldm  ldm      123 Oct 20  2014 .bash_profile
> -rw-r--r--  1 ldm  ldm     3392 Oct 20  2014 .bashrc
> lrwxrwxrwx  1 ldm  ldm       11 Oct 20  2014 bin -> runtime/bin
> -rw-r--r--  1 ldm  ldm        0 Dec 20 14:47 cmcs.txt
> drwx------  3 ldm  ldm     4096 Oct 20  2014 .config
> drwxr-xr-x  2 ldm  ldm     4096 Feb  4 11:37 etc
> -rw-r--r--  1 ldm  ldm      152 Dec 20 14:57 fil.txt
> lrwxrwxrwx  1 ldm  ldm       15 Oct 20  2014 include -> runtime/include
> drwxr-xr-x  7 ldm  ldm     4096 Oct 20  2014 ldm-6.12.6
> -rw-r--r--  1 ldm  ldm  4578727 Oct 20  2014 ldm-6.12.6.tar.gz
> drwxr-xr-x  7 ldm  ldm     4096 Feb  4 11:37 ldm-6.13.6
> -rw-r--r--  1 ldm  ldm  6251152 Feb  4 11:33 ldm-6.13.6.tar.gz
> -rw-r--r--  1 ldm  ldm        0 Feb  4 11:34 .ldmadmin.lck
> lrwxrwxrwx  1 ldm  ldm       11 Oct 20  2014 lib -> runtime/lib
> drwxr-xr-x  3 ldm  ldm     4096 Dec 19 12:09 nm
> -rw-r--r--  1 ldm  ldm      675 Oct 20  2014 .profile
> lrwxrwxrwx  1 ldm  ldm       10 Oct 20  2014 runtime -> ldm-6.12.6
> lrwxrwxrwx  1 ldm  ldm       13 Oct 20  2014 share -> runtime/share
> lrwxrwxrwx  1 ldm  ldm       11 Oct 20  2014 src -> runtime/src
> drwx------  2 ldm  ldm     4096 Dec 27 18:48 .ssh
> drwxr-xr-x  6 ldm  ldm     4096 Dec 28 14:27 util
> drwxr-xr-x  5 ldm  ldm     4096 Oct 20  2014 var
> -rw-------  1 ldm  ldm     4979 Jan  3 07:22 .viminfo
> address@hidden:~$

Your listing of the files in the LDM user's home-directory looks good.

> after we repair the soflinks and start up the box everything is ok
> 
> address@hidden:~/var/logs$ cat ldmd.log
> 20170204T174724.818897Z ldmd[25808] NOTE ldmd.c:980:main() Starting Up
> (version: 6.13.6; built: Feb  4 2017 11:37:44)
> 20170204T174724.819164Z ldmd[25808] NOTE ldmd.c:526:create_ldm_tcp_svc()
> Using local address 0.0.0.0:388
> 20170204T174724.879709Z pqact[25810] NOTE pqact.c:420:main() Starting Up
> 20170204T174724.880207Z pqact[25810] NOTE pqact.c:589:main() Starting
> from insertion-time 2017-02-04 17:34:46.405391 UTC
> 20170204T174724.879950Z rtstats[25811] NOTE rtstats.c:361:main()
> Starting Up (25808)
> 
> 
> the other main relay with the tcp error is still in that state however
> 20170204T010054.145078Z ldmd[1497] WARN ldmd.c:547:create_ldm_tcp_svc()
> Can't register TCP service 300029 on port 388

That warning can be safely ignored for the reasons previously given.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JLH-115818
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.



NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.