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

20040719: Howard LDM Feed



Hi Jason,



allow ANY-NLDN-WSI zephyr\.124\.238\.138\.in-addr\.arpa # Howard University
allow ANY-NLDN-WSI drizzle.sytes.net             # Howard University
(second machine)


You are allowed from "atm.geo.nsf.gov"...

Have you give up on the machine "zephyr"?


Please upgrade to LDM 6.0.14, I do not think this is the problem, but it
may be, and it is best to have the latest tested version, we know of bugs
in 6.0.10.


Let me know how things go after upgrading and we will trouble shoot from
there.

To upgrade please visit:

http://gforge.unidata.ucar.edu/projects/ldm/home/index.html

and obtain the source distribution.

Cheers,

Jeff
---------------------------------------------------------------------
Jeff Weber                                    address@hidden        :
Unidata Program Center                        PH:303-497-8676        :
University Corp for Atmospheric Research      3300 Mitchell Ln       :
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000  :
---------------------------------------------------------------------

On Mon, 19 Jul 2004, Unidata Support wrote:

>
> ------- Forwarded Message
>
> >To: address@hidden
> >cc: address@hidden
> >From: "Jason T. Smith" <address@hidden>
> >Subject: Howard LDM feed
> >Organization: UCAR/Unidata
> >Keywords: 200407191752.i6JHqGaW002033
>
> Hello,
>    I am Jason Smith and I am working with Dr. Joseph at Howard Univerisity to
> setup the LDM on a machine locally.  Below is the startup log of when i ran
> ldmadmin start.  Im not sure where its not connecting from should be
> interesting since i think it might be something dealing with the connection
> between drizzle(the local ldm host) and where it is tring to connect. Any 
> ideas
> what is causing this and how to fix it. I got in contact with Kevin Thomas,
> about this, his response is below. Thank you in advance.
>
> Jason Smith
>
>
>
> Jul 11 16:29:42 drizzle rpc.ldmd[29168]: Starting Up (version: 6.0.10; built:
> May  3 2003 23:33:39)
> Jul 11 16:29:42 drizzle pqbinstats[29170]: Starting Up (29168)
> Jul 11 16:29:42 drizzle pqact[29171]: Starting Up
> Jul 11 16:29:42 drizzle rtstats[29172]: Starting Up (29168)
> Jul 11 16:29:42 drizzle atm[29173]: Starting Up(6.0.10):
atm.geo.nsf.gov:
> TS_ZERO TS_ENDT {{NNEXRAD,  "/p...(AMX|ABR|LWX|DOX|AKQ)"}}
> Jul 11 16:29:42 drizzle atm[29173]: Desired product class: 20040711152942.965
> TS_ENDT {{NNEXRAD,  "/p...(AMX|ABR|LWX|DOX|AKQ)"}}
> Jul 11 16:29:42 drizzle atm[29173]: acl.c:703: nullproc_6() failure: RPC:
> Unable to receive; errno = Connection reset by peer
> Jul 11 16:29:43 drizzle atm[29173]: acl.c:703: nullproc_5() failure: RPC:
> Unable to receive; errno = Connection reset by peer
> Jul 11 16:30:13 drizzle atm[29173]: Desired product class: 20040711152942.965
> TS_ENDT {{NNEXRAD,  "/p...(AMX|ABR|LWX|DOX|AKQ)"}}
>
> Hi Jason...
>
> Based on the output in my log files, I *think* the message means that
> "atm.geo.nsf.gov" isn't configured to give you access to the data.  Have you
> requested access?  Unidata people, address@hidden, can help you here.
>
> Before contacting Unidata, I'd recommend upgrading your LDM software.  The
> current version is 6.0.14.  The documentation that I have says that it fixes
> several performance problems, including connection issues.  It probably won't
> fix your problem, however, it wouldn't hurt to make sure you are using the
> software that everyone is using first before trying to get help from Unidata.
>
> Good Luck.
>
> Kevin W. Thomas
> Center for Analysis and Prediction of Storms
> University of Oklahoma
> Norman, Oklahoma
>
>
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
> --
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publically 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.
>
> ------- End of Forwarded Message
>


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.