NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Disregard...I just saw my own ridiculous typo... Imagine my embarrassment. On Sun, Jul 14, 2013 at 3:37 AM, Blair Trosper < blair.trosper@xxxxxxxxxxxxxxxxxxx> wrote: > Alright, I'm stumped. We use this same config on four other servers, and > tonight, using LDM 6.11.6 and Debian 6, it's failing. > > From pqact.conf: > >> NEXRAD2 ^L2-BZIP2/(....)/([0-9]{8})([0-9]{4})[0-9]{2}/([0-9]{1,4}).*/[SI] >> FILE data/nexrad2/\1/\1_\2-\3.part >> (snip) > > > From ldmd.conf: > >> REQUEST NEXRAD2 ".*" bigbird.tamu.edu >> REQUEST NEXRAD2 ".*" idd.tamu.edu > > > Here is the error we get when trying to use "ldmadmin start": > >> ldm@chicago-il-1:~$ ldmadmin start >> The product-queue is OK. >> Checking pqact(1) configuration-file(s)... >> /mnt/data/ldm/etc/pqact.conf: has problems: >> Jul 14 08:36:23 pqact[12933] NOTE: Starting Up >> *Jul 14 08:36:23 pqact[12933] ERROR: feedtype error at line 4: >> unknown feed name in feedtype expression*: "NEXRAD2 >> ^L2-BZIP2/(....)/([0-9]{8})([0-9]{4})[0-9]{2}/([0-9]{1,4}).*/E" >> Jul 14 08:36:23 pqact[12933] ERROR: Error in configuration-file >> "/mnt/data/ldm/etc/pqact.conf" >> Jul 14 08:36:23 pqact[12933] NOTE: Exiting > > > We have another LDM 6.11.6 server on Debian 7 with these *exact*settings, and > it has no errors and correctly fetches the L2 data. What on > earth am I missing...NEXRAD2 isn't a valid feed type all of a sudden? > > Disclaimer: I've been at this for 3 hours...so I'm probably overlooking > something stupid. > > -- > Blair Trosper > Weather Data / Updraft Networks > blair.trosper@xxxxxxxxxxxxxxxxxxx <blair.trosper@xxxxxxxxxx> > NOC: 512-666-0536 > -- Blair Trosper Weather Data / Updraft Networks blair.trosper@xxxxxxxxxxxxxxxxxxx <blair.trosper@xxxxxxxxxx> NOC: 512-666-0536
ldm-users
archives: