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

20050509: 20050509: 20050509: Question on ldm-6.3.0: "no stats"?



Celia,

Your LDMHOSTNAME environmental variable is created in your ~ldm/bin/ldmadmin 
script.
The LDMHOSTNAME is created from the $hostname variable defined in 
ldmadmin-pl.conf
unless the script was edited by hand. 

Steve Chiswell
Unidata User Support





>From: Celia Chen <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200505092226.j49MQUP3023189

>Here is the output from running ldmadmin config:
> 
>rasp:/home/ldm:vi ldmd.conf
>rasp:/home/ldm:cd
>rasp:/home/ldm:cd logs
>rasp:/home/ldm:vi pqact.log
>rasp:/home/ldm:ldmadmin config
>
>hostname:      rasp.rap.ucar.edu
>os:            Linux
>release:       2.4.29-dqcd-smp
>ldmhome:       /home/ldm
>bin path:      /home/ldm/bin
>conf file:     /home/ldm/etc/ldmd.conf
>log file:      /home/ldm/logs/ldmd.log
>numlogs:       4
>log_rotate:    1
>data path:     /home/ldm/data
>product queue: /home/ldm/data/ldm.pq
>queue size:    4G bytes
>queue slots:   default
>IP address:    all
>PID file:      /home/ldm/ldmd.pid
>LDMHOSTNAME:   .rap.ucar.edu
>PATH:          /home/ldm/bin:/bin:/usr/bin:/usr/sbin:/sbin:/usr/ucb:/usr/usb:/
> usr/etc:/etc:/home/ldm/bin:/home/ldm/decoders:/home/ldm/util:/home/ldm/man:/u
> sr/local/dcs_woody/bin:/usr/local:/usr/local/ncarg/bin:/usr/local/sbin:/usr/l
> ocal/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:.:.
>
>Looks like LDMHOSTNAME is missing "rasp". Where is it defined?
>
>Thanks.
>
>Celia
>
>
>On Mon, May 09, 2005 at 04:20:11PM -0600, Unidata Support wrote:
>> 
>> Celia,
>> 
>> The statistics I see have a hostname of ".rap.ucar.edu".
>> That is, it doesn't seem to have the "rasp" name.
>> Can you run the command "ldmadmin config"  and see what
>> the output for "hostname" is on the first line? If that is incorrect,
>> then there could be a typo or something unexpected in your ldmadmin-pl.confi
> g
>> file. If so, please send that file so we can look at it.
>> 
>> Steve Chiswell
>> Unidata User Support
>> 
>> 
>> >From: Celia Chen <address@hidden>
>> >Organization: UCAR/Unidata
>> >Keywords: 200505092157.j49LvpP3020022
>> 
>> >This is what I have in rasp's ldmadmin-pl.conf file:
>> >
>> >#
>> >#chop($hostname = `uname -n`);
>> >$hostname = "rasp.rap.ucar.edu";
>> >
>> >Thanks.
>> >
>> >Celia
>> >
>> >On Mon, May 09, 2005 at 03:50:15PM -0600, Unidata Support wrote:
>> >> 
>> >> Celia,
>> >> 
>> >> Most likely, you have a problem with your hostname in the 6.3.0 ~ldm/etc/
> ldm
>> > admin-pl.conf
>> >> file. It may need to be fully qualified. This was moved from the ldmadmin
>  sc
>> > ript
>> >> oiin your 6.1.0 release to a config file for future releases so that you 
> don
>> > 't have to keep
>> >> updating your ~ldm/bin/ldmadmin script.
>> >> 
>> >> Steve Chiswell
>> >> Unidata User Support
>> >> 
>> >> 
>> >> 
>> >> >From: Celia Chen <address@hidden>
>> >> >Organization: UCAR/Unidata
>> >> >Keywords: 200505092137.j49LbpP3017761
>> >> 
>> >> >I upgraded the ldm to ldm-6.3.0 on rasp last thursday. For some reason t
> he 
>> > rea
>> >> > ltime
>> >> >statistic information doesn't get to unidata after the upgrade. See belo
> w: 
>> >  
>> >> >
>> >> >Topology for NEXRAD2 to rasp.rap.ucar.edu
>> >> >
>> >> >      0 rasp.rap.ucar.edu
>> >> >            1 thelma.ucar.edu [no stats] [redundant loop] 
>> >> >
>> >> >But as soon as I switch back to 6.1.0 the stats is online again. 
>> >> >
>> >> >Please advise.  
>> >> >
>> >> >Also, please let me know if you have an answer for my other question
>> >> >below.
>> >> >
>> >> >Celia
>> >> >
>> >> >
>> >> >On Thu, May 05, 2005 at 06:06:33PM -0600, Celia Chen wrote:
>> >> >> Dear Support,
>> >> >> 
>> >> >> I have a question on the time stamps that we see when we do ldmadmin w
> atc
>> > h:
>> >> >> 
>> >> >> May 05 23:07:18 pqutil:    23416 20050505220555.112 NEXRAD2 172007  L2
> -BZ
>> > IP2
>> >> > /KGJX/20050505220505/172/7
>> >> >> May 05 23:07:18 pqutil:     6001 20050505220555.561 NEXRAD2 986005  L2
> -BZ
>> > IP2
>> >> > /KDDC/20050505220444/986/5
>> >> >> May 05 23:07:18 pqutil:    13022 20050505220555.212 NEXRAD2 66012  L2-
> BZI
>> > P2/
>> >> > KAMX/20050505220506/66/12
>> >> >> May 05 23:07:18 pqutil:    29997 20050505220555.128 NEXRAD2 916024  L2
> -BZ
>> > IP2
>> >> > /KGLD/20050505220419/916/24
>> >> >> 
>> >> >> I assume that the time on the left is the data arrival time, the time 
> in 
>> > the
>> >> >  middle is when the file
>> >> >> was sent by the upstream host, and the time on the right is the time w
> hen
>> >  th
>> >> > e file was
>> >> >> generated.
>> >> >> 
>> >> >> Both our LDM hosts rasp and level are getting NEXRAD2 data from thelma
> .  
>> > The
>> >> > y both request the
>> >> >> NEXRAD2 data directly from thelma.  For some reason, there was a huge
>> >> >> (~ 1 hour) latency on rasp this afternoon, as you can see from the abo
> ve 
>> > lis
>> >> > t. But somehow
>> >> >> the same feed on level was very much on time.  Unfortunately I don't h
> ave
>> >  th
>> >> > e watch on for the
>> >> >> same time period on level. 
>> >> >> 
>> >> >> Is my assumption correct about the time stamps? If so, why do we see t
> he 
>> > big
>> >> >  difference on the
>> >> >> time stamps (from thelma) between rasp and level, therefore the data l
> ate
>> > ncy
>> >> >  on rasp but not 
>> >> >> on level?
>> >> >> 
>> >> >> Thanks in advance.
>> >> >> 
>> >> >> Celia.
>> >> >
>> >> --
>> >> *************************************************************************
> ***
>> >> Unidata User Support                                    UCAR Unidata Prog
> ram
>> >> (303)497-8643                                                  P.O. Box 3
> 000
>> >> address@hidden                                   Boulder, CO 80
> 307
>> >> -------------------------------------------------------------------------
> ---
>> >> Unidata WWW Service              http://my.unidata.ucar.edu/content/suppo
> rt 
>> >> -------------------------------------------------------------------------
> ---
>> >> 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.
>> >
>> --
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8643                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service              http://my.unidata.ucar.edu/content/support 
>> ----------------------------------------------------------------------------
>> 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.


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.