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

[LDM #VLH-822247]: TDWR Product


Tom's AFK untill tomorrow -- so I'll try to help. Unfortunately, I'm sick at 
home and it's hard to think.

> I searched through my inbox and found that I sent a support request first, 
> and after a while (as you pointed out it was never answered) I sent a request 
> to the gembud mailing list. Michael James responded with the following:
> "I can confirm TDWR is fubar in GEMPAK right now.  I'm looking at it."
> Not long after everything started working, but after a couple of weeks the 
> velocity products began returning the 'unsupported format' error again. I 
> suppose it was only my assumption that it was an upstream error since I 
> didn't change anything on my end. I received no further correspondence from 
> Michael on the issue.
> I remade the queue and there has been no immediate change in the latest 
> products.

Sorry, but does "no immediate change" mean that it's working or not?

> Our queue size is 500MB, should we be allocating more space?

The size that the product queue should be depends on what you're receiving. 
Generally, we like to have queues be large enough so that they always hold at 
least the last hour's worth of data. You can use the pqmon(1) utility to 
determinate the age of the oldest product in the queue:

    $pqmon -vl-
    Apr 08 16:02:00 pqmon[12494] NOTE: Starting Up (12477)
    Apr 08 16:02:00 pqmon[12494] NOTE: nprods nfree  nempty      nbytes  
maxprods  maxfree  minempty    maxext  age
    Apr 08 16:02:00 pqmon[12494] NOTE:  33145     4  276434  1499234624     
83487      703    226095     63304 250
    Apr 08 16:02:00 pqmon[12494] NOTE: Exiting

The last field is the relevant parameter (250 seconds in this bad example).

> External IP:
> Output of 'ldmadmin config' :
> hostname:              reg-10-17-160-133.uncc.edu
> os:                    Linux
> release:               3.10.0-123.4.4.el7.x86_64
> ldmhome:               /home/ldm
> LDM version:           6.12.3
> PATH:                  
> /home/ldm/ldm-6.12.3/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/gempak/GEMPAK7/os/linux64/bin:/home/gempak/GEMPAK7/bin:/home/ldm/.local/bin:/home/ldm/bin
> LDM conf file:         /home/ldm/etc/ldmd.conf
> pqact(1) conf file:    /home/ldm/etc/pqact.conf
> scour(1) conf file:    /home/ldm/etc/scour.conf
> product queue:         /home/ldm/var/queues/ldm.pq
> queue size:            500M bytes
> queue slots:           default
> reconciliation mode:   decrease-latency
> pqsurf(1) path:        /home/ldm/var/queues/pqsurf.pq
> pqsurf(1) size:        2M
> IP address:  
> port:                  388
> PID file:              /home/ldm/ldmd.pid
> Lock file:             /home/ldm/.ldmadmin.lck
> maximum clients:       256
> maximum latency:       7
> time offset:           7
> log file:              /home/ldm/var/logs/ldmd.log
> numlogs:               7
> log_rotate:            1
> netstat:               /bin/netstat -A inet -t -n
> top:                   /usr/bin/top -b -n 1
> metrics file:          /home/ldm/var/logs/metrics.txt
> metrics files:         /home/ldm/var/logs/metrics.txt*
> num_metrics:           4
> check time:            1
> delete info files:     0
> ntpdate(1):            /usr/sbin/ntpdate
> ntpdate(1) timeout:    5
> time servers:          ntp.ucsd.edu ntp1.cs.wisc.edu ntppub.tamu.edu 
> otc1.psu.edu timeserver.unidata.ucar.edu
> time-offset limit:     10
> On an unrelated note, has support-gempak been discontinued? I recall sending 
> a couple of support requests recently but never getting a ticket number back.

AFAIK, <address@hidden> is still active. I'll ask, though.

> Thanks again,
> -Warren
> Warren Pettee
> Undergraduate - Meteorology
> Department of Geography and Earth Sciences
> University of North Carolina at Charlotte
> 9201 University City Blvd, Charlotte, NC 28223
> address@hidden | 336.257.9239

Steve Emmerson

Ticket Details
Ticket ID: VLH-822247
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.