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

20050419: unidata2 ldm woes?

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: 20050419: unidata2 ldm woes?
  • Date: Tue, 19 Apr 2005 16:50:22 -0600
>From: address@hidden (Pete Pokrandt)
>Organization: U Wisconsin
>Keywords: 200504192140.j3JLeOv2025149 IDD request pathological regular 
>expression

Pete,

re:
>We haven't received any data from unidata2 since 13:55 local time
>(18:55 UTC). I have failed over to idd.unidata.ucar.edu for now.
>
>Any idea what is up?

It appears that the problem is a strange interaction between your request
pattern:

UNIWISC|HDS|DDPLUS  ".*|!^SDUS5.*"

and a code modification in LDM 6.3.0 that tries to "fix" incorrect
patterns on the server side (the LDM on unidata2 was upgraded from a
very old distribution (6.0.14) to the current release (6.3.0) by me
today).  Since I saw no 'Denying' connection messages in the
~ldm/logs/ldmd.log file, and since I verified that data was flowing to
UPC machines feeding from unidata2, I expected that everyone was
getting data OK.  Apparently you are the only downstream that saw any
effect.

Your feed request is apparently trying to get everything except
products whose headers start with SDUS5.  Since products with headers
of SDUS5 are NEXRAD Level III products, and since your request line
does not include NNEXRAD data, the simplest fix is for you change your
request line:

request UNIWISC|HDS|IDS|DDPLUS  ".*"    unidata2.ssec.wisc.edu

 -- or --

request UNIWISC|WMO     ".*"    unidata2.ssec.wisc.edu

 -- or --

request UNIDATA ".*"    unidata2.ssec.wisc.edu

Please correct your ldmd.conf request line; fail back to unidata2; and
let us know that you are once again getting the data you want.

Cheers,

Tom Yoksas
--
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.

>From address@hidden  Tue Apr 19 20:32:59 2005

Tom,

I think that was in there from long ago when the IDD ingest switched over to
NOAAport from the original satellite feed. At any rate, I've changed it to
just UNIDATA ".*" and data seems to be flowing just fine.

Thanks,

Pete
--
+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
^ Systems Programmer               V Madison,         WI     53706    ^
^                                  V      address@hidden       ^
^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+