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

Re: 20050921: sasquatch can't talk to bigbird?



Gerry,

> To: Unidata Support <address@hidden>
> >From: Gerry Creager N5JXS <address@hidden>
> Subject: sasquatch can't talk to bigbird?
> Organization: Texas A&M University -- AATLT
> Keywords: 200509211347.j8LDltYJ018102 LDM IDD

The above message contained the following:

> I'm having a problem and seeing the following from an ldmadmin tail:
> _____________________________________
> Sep 21 13:42:45 sasquatch bigbird[32449]: Desired product class: 
> 20050921124245.039 TS_ENDT {{EXP|NEXRAD2|NNEXRAD|FSL3|FSL2|WMO,  "[DSW]"}}
> Sep 21 13:42:45 sasquatch bigbird[32449]: ERROR: requester6.c:457; 
> ldm_clnt.c:277: Couldn't connect to LDM 6 on bigbird.tamu.edu using 
> either port 388 or portmapper; ldm_clnt.c:116: : RPC: Remote system 
> error - No route to host
> Sep 21 13:42:49 sasquatch mesodata3[22609]: Empty intersection of HIYA 
> offer from mesodata3.tamu.edu (TS_ZERO TS_ENDT {{EXP,  ".*"}}) and 
> ACCEPT entries
> _____________________________________
> And, ldmping yields nothing, while a notifyme looks like this:
> _____________________________________
> address@hidden ~]$ ldmping bigbird.tamu.edu
> Sep 21 13:43:55      State    Elapsed Port   Remote_Host           rpc_stat
> 
> address@hidden ~]$ notifyme -xvl - -h bigbird
> Sep 21 13:44:14 notifyme[22649]: Starting Up: bigbird: 
> 20050921134414.130 TS_ENDT {{ANY,  ".*"}}
> Sep 21 13:44:14 notifyme[22649]: Connected to upstream LDM-5
> Sep 21 13:45:04 notifyme[22649]: Connected to upstream LDM-5

Odd that an ldmping(1) would fail but a notifyme(1) wouldn't.

I just did an ldmping(1) on Sasquatch to Bigbird and it worked:

    address@hidden src]$ ldmping -vl- -h bigbird
    Sep 21 20:10:52      State    Elapsed Port   Remote_Host rpc_stat
    Sep 21 20:10:52 RESPONDING   0.005921  388   bigbird      
    ...

I suspect that either Bigbird's LDM was offline, or there was a glitch
in your network for that time interval.

> PS:  I'm also seeing the occasional reference to mesodata3 and HIYAs in 
> bigbird's logfile.

Apparently, an rtstats(1) process on Mesodata3 is trying to send
statistics to Sasquatch but there's no matching ACCEPT entry in the LDM
configuration-file, etc/ldmd.conf.  Should it be trying to send the
statistics?

I'm installing a new version of the LDM on Sasquatch -- one that will,
hopefully, help us understand the HIYA/SIGSEGV problem.

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.