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.
On Fri, 29 Oct 1999, Unidata Support wrote: > > ------- Forwarded Message > > >To: address@hidden > >From: Phil Mieczynski <address@hidden> > >Subject: ldm ingest on HP-UX 10.20 > >Organization: . > >Keywords: 199910292019.OAA20540 > > > Thanks for your help on my last question. I'm getting closer to having things > up > and running but have hit a snag, > > I'm testing my ldm connection with another ldm box out at the anchorage fo. I > can see by looking at the logs that the servers are up on both boxes and that > they can see each other. I'm now trying to send a test ascii file from one box > to the other and am not having much luck. > > I'm pretty sure the problem is a combination of my request line in ldmd.conf, > the pattern file line in pqact.conf, and the ascii file I'm sending. At this > point I'm really confused. > > It might help if I saw an example, which is why I'm emailing you. Will you > please send me an example of how to setup my conf files to send/receive a > simple > ascii text file? > > I tried using an example off the unidata web site for distributing simple > ascii > data using "request EXP TESTFILE barah.anc.nwsar.gov" but, I could never get > the Phil, The downstream machine should have a request line like: request EXP ".*" barah.anc.nwsar.gov The upstream machine should have an allow like: allow EXP deke.arh.nwsar.gov > server's to start after that (it didn't like the request line entry, some sort > of parse error). I had to go back to the default's that came with the binary > distribution of ldm (I modified the default files and changed all reference of > unidata platforms to the aronet platforms I'm testing with) in order to get > the > server started again. The 2 boxes I'm testing on are deke.arh.nwsar.gov & I'm assumming that deke is downstream and barah is the upstream machines, otherwise switch the above entries. > barah.anc.nwsar.gov. > > Thanks for any help you can provide...Phil > > P.S. Another problem I seem to have from time to time is when I start the > servers by running "ldmadmin start". I'll get messages in the ldmd.log that > say: > > pqbinstats: cannot chdir to /usr/local/ldm/logs: No such file or directory > and, > pqact: Couldn't open pattern file "/usr/local/ldm/etc/pqact.conf": No such > file > or directory > > even though "ldmadmin config" shows: > ldmhome: /home/ldm > conf file: /home/ldm/etc/ldmd.conf > log file: /home/ldm/logs/ldmd.log > This is easy to solve, make a link: % ln -s /home/ldm /usr/local/ldm You might have to mkdir /usr/local and be root Back to your original question, use pqinsert on the upstream machine: % pqinsert -vl - -q /home/ldm/data/ldm.pq <filename> Look at the man page for pqinsert: http://www.unidata.ucar.edu/cgi-bin/man-cgi?pqinsert+1 Robb... > This is getting kinda long so I guess this is enough questions for > now...Thanks > > > ------- End of Forwarded Message > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================