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

20050412: "Unable to receive" message in logfile

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.

  • Subject: 20050412: "Unable to receive" message in logfile
  • Date: Tue, 12 Apr 2005 15:42:51 -0600
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