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

20050412: "Unable to receive" message in logfile



Angelo,

>Date: Tue, 12 Apr 2005 12:08:28 -1000
>From: "Alvarez, Angelo CIV NAVPACMETOCCEN JTWC" <address@hidden>
>Organization: NAVPACMETOCCEN/JTWC
>To: "Steve Emmerson" <address@hidden>
>Subject: RE: 20050412: "Unable to receive" message in logfile

The above message contained the following:

> For some reason, the downstream LDM (which is running 6.3.0) thinks it
> is connecting to an upstream LDM-5 (instead of LDM-6).  The upstream LDM
> is running 6.3.0 also.  Do you know why this is??

Oops!  My bad.  The notifyme(1) utility still uses version 5 of the LDM
protocol (there was no incentive to improve it).  So, as long as that
"(noti)" string appears next to the downstream hostname, you can expect
the upstream LDM to use protocol version 5.

> niihau (ldm 6. is a system on the same network as oahu (no firewall).  When I 
> run notifyme on niihau against oahu, I see the following:
> niihau% ./notifyme.oahu
> Apr 12 21:29:03 notifyme[22209]: Starting Up: oahu: 20050412212903.319 
> TS_ENDT {
> {ANY,  ".*"}}
> Apr 12 21:29:03 notifyme[22209]: Connected to upstream LDM-5
> Apr 12 21:29:03 notifyme[22209]: NOTIFYME(oahu): OK
> Apr 12 21:34:29 notifyme[22209]: Connected to upstream LDM-5
> Apr 12 21:34:29 notifyme[22209]: NOTIFYME(oahu): OK
> Apr 12 21:39:55 notifyme[22209]: Connected to upstream LDM-5
> Apr 12 21:39:55 notifyme[22209]: NOTIFYME(oahu): OK
> Apr 12 21:45:21 notifyme[22209]: Connected to upstream LDM-5
> Apr 12 21:45:21 notifyme[22209]: NOTIFYME(oahu): OK
> Apr 12 21:50:47 notifyme[22209]: Connected to upstream LDM-5
> Apr 12 21:50:47 notifyme[22209]: NOTIFYME(oahu): OK

The above shows the notifyme(1) process repeated connecting to the
upstream LDM (because the notifying LDM child-process that the upstream
LDM server spawns repeatedly terminates).

> However, the logs on oahu show me this:
> Apr 12 22:00:31 oahu niihau(noti)[2234]: Starting Up(6.3.0/5): 
> 20050412212903.319 TS_ENDT {{ANY,  ".*"}}
> Apr 12 22:00:31 oahu niihau(noti)[2234]: topo:  niihau ANY
> Apr 12 22:00:36 oahu niihau(noti)[509]: nullproc5(niihau): RPC: Unable to 
> receive

Yup.  That's consistent with what I just wrote.

> v/r
> angelo
> 
> Angelo Alvarez
> System Administrator
> NAVPACMETOCCEN/JTWC
> https://www.npmoc.navy.mil
> email: address@hidden
> phone: 808.471.3645
> 
> 
> -----Original Message-----
> From: Steve Emmerson [mailto:address@hidden
> Sent: Tuesday, April 12, 2005 11:43
> To: Alvarez, Angelo CIV NAVPACMETOCCEN JTWC
> Cc: address@hidden
> Subject: 20050412: "Unable to receive" message in logfile
> 
> 
> Angelo,
> 
> >Date: Tue, 12 Apr 2005 11:22:42 -1000
> >From: "Alvarez, Angelo CIV NAVPACMETOCCEN JTWC" <address@hidden>
> >Organization: NAVPACMETOCCEN/JTWC
> >To: "Steve Emmerson" <address@hidden>
> >Subject: RE: 20050412: broken pipe error while compiling LDM 6.3.0 using GCC 
> >on Solaris 8 
> 
> The above message contained the following:
> 
> > I have upgraded ldm on both our upstream and downstream server.
> > However, on the upstream server, I see the following entries in ldmd.log:
> 
> > Apr 12 21:00:56 oahu gw1-dmz(noti)[21097]: nullproc5(gw1-dmz): RPC: Unable 
> > to receive
> > Apr 12 21:06:17 oahu gw2-dmz(noti)[22445]: Starting Up(6.3.0/5): 
> > 20050412205452.403 TS_ENDT {{ANY,  ".*"}}
> > Apr 12 21:06:17 oahu gw2-dmz(noti)[22445]: topo:  gw2-dmz ANY
> > Apr 12 21:06:22 oahu gw1-dmz(noti)[21777]: nullproc5(gw1-dmz): RPC: Unable 
> > to receive
> > Apr 12 21:11:43 oahu gw1-dmz(noti)[23147]: Starting Up(6.3.0/5): 
> > 20050412205452.403 TS_ENDT {{ANY,  ".*"}}
> > Apr 12 21:11:43 oahu gw1-dmz(noti)[23147]: topo:  gw1-dmz ANY
> > Apr 12 21:11:48 oahu gw2-dmz(noti)[22445]: nullproc5(gw2-dmz): RPC: Unable 
> > to receive
> > Apr 12 21:16:44 oahu gw1-dmz(noti)[23147]: nullproc5(gw1-dmz): RPC: Unable 
> > to receive
> > Apr 12 21:17:09 oahu gw2-dmz(noti)[23858]: Starting Up(6.3.0/5): 
> > 20050412205452.403 TS_ENDT {{ANY,  ".*"}}
> > Apr 12 21:17:09 oahu gw2-dmz(noti)[23858]: topo:  gw2-dmz ANY
> 
> The above is easier to interpret if we just look at the messages from
> process 22445:
> 
> > Apr 12 21:06:17 oahu gw2-dmz(noti)[22445]: Starting Up(6.3.0/5): 
> > 20050412205452.403 TS_ENDT {{ANY,  ".*"}}
> > Apr 12 21:06:17 oahu gw2-dmz(noti)[22445]: topo:  gw2-dmz ANY
> > Apr 12 21:11:48 oahu gw2-dmz(noti)[22445]: nullproc5(gw2-dmz): RPC: Unable 
> > to receive
> 
> The above means that a "notifying" upstream LDM-5 was started on host
> "oahu" due to a NOTIFYME request from host "gw2-dmz" (notifying LDM-s
> don't send data, only metadata).  The notifying LDM on "oahu" sent a
> NULLPROC message to "gw2-dmz" (to test or flush the connection) but did
> not receive the mandatory (but empty) reply.  The notifying LDM then
> terminates.
> 
> Apparently, host "gw2-dmz" is still running version 5 of the LDM.
> 
> Corresponding entries in the LDM logfile on "gw2-dmz" might prove
> illuminating.
> 
> It could be that the network between the two systems isn't very good.
> 
> > Any ideas??
> > 
> > v/r
> > angelo
> > 
> Angelo Alvarez
> > System Administrator
> > NAVPACMETOCCEN/JTWC
> > https://www.npmoc.navy.mil
> > email: address@hidden
> > phone: 808.471.3645
> 
> Regards,
> Steve Emmerson

Regards,
Steve Emmerson


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.