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

[LDM #HUD-735823]: LDM 6.13.7 configure issue

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #HUD-735823]: LDM 6.13.7 configure issue
  • Date: Mon, 04 Mar 2019 19:00:27 -0700
Scott,

> 6.13.7 configure log stops at that point and does not continue, when I run 
> the configure on 6.13.8.11 I have additional data after that line, so I have 
> been running 6.13.8.11.

Good. The latest version is 6.13.8.
 
> As of right now, I am only getting data via NOAAPort, and I have 
> EXEC"noaaportIngester -m 224.0.1.1 -I 10.2.1.2" along with 224.0.1.2 and 
> 224.0.1.3 in my ldmd.conf
> 
> My pqact is:
> IDS|DDPLUS ^.*FOUS11 (....) (..)(....) /pLAV
> PIPE-close /home/scripts/lamp/lamp.py
> 
> I also have tried ^FOUS11 KWNO (..)(....) /pLAV
> 
> 
> I have ran this notifyme command:
> notifyme -vxl- -f ANY -p FOUS11
> Also changed the feed type to be IDS|DDPLUS

We're not getting many FOUS11 products here:

~: notifyme -h uni16.unidata.ucar.edu -v -p '^FOUS11' -o 3600
20190304T220536.617101Z              notifyme[4007]                
notifyme.c:main() NOTE  Starting Up: uni16.unidata.ucar.edu: 
20190304210536.616613 TS_ENDT {{ANY, "^FOUS11"}}
20190304T220536.617388Z              notifyme[4007]              
ldm5_clnt.c:forn5() NOTE  LDM-5 desired product-class: 20190304210536.616613 
TS_ENDT {{ANY, "^FOUS11"}}
20190304T220536.619380Z              notifyme[4007]                
error.c:err_log() INFO  Resolving uni16.unidata.ucar.edu to 128.117.140.126 
took 0.001696 seconds
20190304T220536.622980Z              notifyme[4007]        
ldm5_clnt.c:forn_signon() NOTE  NOTIFYME(uni16.unidata.ucar.edu): OK
20190304T220539.277518Z              notifyme[4007]      
notifyme.c:notifymeprog_5() INFO        4295 20190304211826.254753 IDS|DDPLUS 
16368468  FOUS11 KWBC 042118 /pQPFHSD
20190304T220540.867949Z              notifyme[4007]      
notifyme.c:notifymeprog_5() INFO     3394431 20190304213252.956353 IDS|DDPLUS 
16398250  FOUS11 KWNO 042100 /pLAVUSA
^C20190304T220708.569491Z              notifyme[4007]             
notifyme.c:cleanup() NOTE  exiting

Note that only one FOUS11 products had the " /pLAV" suffix.

If all of the FOUS11 products are also LAMP products, then perhaps you should 
remove the " /pLAV" suffix from the pqact(1) pattern.

> Once in a while I do see the LAMP data, but it does not come across every 
> hour. For example today I came in at 1 PM and saw that the lamp had last been 
> completed at 11:33 AM. Yesterday I was watching notifyme, and only saw a 
> handful of LAMP data, not every hour like I had on my old server.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HUD-735823
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.