20030908: Assistance requested with LDM upgrade strategy

Allan,

> Date: Mon, 08 Sep 2003 16:15:52 -0400
> From: "Allan.Darling" <address@hidden>
> Organization: DOC/NOAA/NWS - National Weather Service
> To: address@hidden
> CC: Graham Stork <address@hidden>,
>       Andy Edman <address@hidden>, Kirby Cook <address@hidden>,
>       Jeff Walker <address@hidden>
> Subject: Assistance requested with LDM upgrade strategy

The above message contained the following:

> We are in the process of upgrading upstream and downstream systems
> running LDM 5.x to LDM 6.  We thought it best to leave the upstream
> site unchanged while upgrading the downstream sites.

LDM 6 was designed so that the upstream or downstream LDM-s could be
independently upgraded.  It doesn't matter which one is first; except
that the downstream LDM-s won't see any advantage until the upstream LDM
is upgraded.

> When one of the downstream sites upgraded they encountered some
> unexpected log messages.  Are these a cause for concern or can they be
> safely ignored?

The notice about the LDM version can be safely ignored; the other messages
are more serious, however.

> BTW, if there is a more appropriate target of opportunity than 
> yourself for LDM questions, please don't hesitate to adjust my aim 
> toward them!

Well... I'm (Steve Emmerson) the LDM developer.  Is that good enough?

> Graham Stork wrote:
...

> > I ran LDM v6.0.14 for a brief time earlier today.  Radar data was
> > passing from the TOC LDM servers to our server and on to WR destination
> > www pages.  But, ....  I saw some stuff in the log files on the LDM
> > v6.0.14 box that concerned me so I have retreated to LDM v5.1.4.
> >
> > Some of the log file entries that concerned me are included.
> >
> >  From /var/log/messages   on 198.177.182.49 (radmaul)
> >
> > Sep 08 18:42:42 radmaul 205.156.51.12[4776]: NOTICE: requester6.c:454_ 
> > ldm_clnt.c:285: nullproc_6 failure to 205.156.51.12_ ldm_clnt.c:142: RPC: 
> > Program/version mismatch_ low version = 4, high version = 5
> > Sep 08 18:42:42 radmaul 205.156.51.13[4777]: NOTICE: requester6.c:454_ 
> > ldm_clnt.c:285: nullproc_6 failure to 205.156.51.13_ ldm_clnt.c:142: RPC: 
> > Program/version mismatch_ low version = 4, high version = 5
> > Sep 08 18:42:42 radmaul 205.156.51.12[4778]: NOTICE: requester6.c:454_ 
> > ldm_clnt.c:285: nullproc_6 failure to 205.156.51.12_ ldm_clnt.c:142: RPC: 
> > Program/version mismatch_ low version = 4, high version = 5
> > Sep 08 18:42:42 radmaul 205.156.51.13[4779]: NOTICE: requester6.c:454_ 
> > ldm_clnt.c:285: nullproc_6 failure to 205.156.51.13_ ldm_clnt.c:142: RPC: 
> > Program/version mismatch_ low version = 4, high version = 5

The above can be safely ignored.  They result from the upstream LDM
being at version 5 rather than version 6.

> >  From the  ldmd.log files on 198.177.182.49 (radmaul)
> >
> > Sep 08 19:06:19 radmaul rpc.ldmd[9449]: Starting Up (version: 6.0.14; 
> > built: Sep  8 2003 16:19:53)
> > Sep 08 19:06:19 radmaul rpc.ldmd[9449]: Version 6 LDM already running on 
> > local host
> > Sep 08 19:06:19 radmaul rpc.ldmd[4772]: Denying connection from radmaul
> > Sep 08 19:06:19 radmaul rpc.ldmd[9449]: Version 5 LDM already running on 
> > local host
> > Sep 08 19:06:19 radmaul rpc.ldmd[9449]: Terminating process group

The above indicates that an LDM 6 was already registered with the RPC layer 
when a new LDM 6 was started.  This shouldn't happen.

Was the previously-running LDM 6 properly shut-down (there should be
some entries in the logfile indicating as much)?

> > Not exactly sure what the above messages mean. Maybe they are not cause
> > for concern.....The LDM boxes did establish a connection and pass data.
> >   But, I was concerned enough that I thought it best to retreat and
> > maybe try to get some information.

Please feel completely free to contact me for any questions you might
have.

> > Graham Stork
> > Information Technology Specialist/AWIPS Systems Analyst
> > National Weather Service -- Western Region
> > Salt Lake City, UT
> > 801-524-5120 x286
> > address@hidden

Regards,
Steve Emmerson
LDM Developer