Re: [ldm-users] Downstream LDM Problems

• To: emmerson@xxxxxxxx, Gilbert Sebenste <sebenste@xxxxxxxxxxxxxxxxxxxxx>
• Subject: Re: [ldm-users] Downstream LDM Problems
• From: Phil Birnie <phil@xxxxxxxxxxx>
• Date: Fri, 8 Jul 2011 18:15:14 -0400

Hi Steve & Gilbert, all.

Thanks for your response and help.

Some good progress.... first: silly, silly problem -- and a major oversight on 
my part -- even after all of the preaching re: a synchronized clock at the 
workshop.  The clock was set to CDT instead of EDT; none of the products were 
coming in until 1 hour later. Once we set the clock, everything began working 
as it should.  The minutes and seconds looked fine; I didn't notice that the 
hour was one off.    

The only outstanding issue I'm dealing with is the log file. 

> You've *got* to get logging enabled on Twister2. Is it a Linux system?
> If so, what is the value of the SELINUX parameter in the file
> "/etc/selinux/config"?
> If it isn't "disabled", then set it to that value.

Yes, it is set to this "disabled".  I am Unix competent but not an expert.  If 
you have any advice here, I'd be thankful.  

Thanks again for taking the time to help us and have a nice weekend,

-- Phil & several others here at OSU... 

On Jul 8, 2011, at 12:35 PM, Steve Emmerson wrote:

> Phil,
> 
>> Our setup is as follows: 
> 
> 
>> Upstream LDMs for Twister
>> |
>> ============ FIREWALL ============
>> |
>> |
>> Twister (twister.sbs.ohio-state.edu -- LDM v. 6.7.0)
>> |
>> |
>> Twister2 (128.146.191.17 -- twister2.sbs.ohio-state.edu not active on DNS 
>> yet -- LDM v. 6.9.8) 
> 
> You say the IP address for Twister2 is 128.146.191.17 but the examples
> give it as 128.146.194.17.
> 
>> I can't even find the LDM logs on Twister2 for some reason (ran
>> --enable-logging=local0 when configuring & ldmd.log is empty nor is
>> there any info in /var/log/messages),
> 
> You've *got* to get logging enabled on Twister2. Is it a Linux system?
> If so, what is the value of the SELINUX parameter in the file
> "/etc/selinux/config"?
> If it isn't "disabled", then set it to that value.
> 
>> but in Twister's LDM logs I found
>> that Twister2 can connect, but we receive the following error (just
>> _once_ per ldmadmin start occurrence):
>> 
>> *LDMD.LOG OUTPUT FROM  TWISTER: *
>> 
>> Jul 08 05:41:45 twister 128.146.194.17(feed)[26069] NOTE: Starting
>> Up(6.7.0/6): 20110708054322.793 TS_ENDT {{ANY,  ".*"}},
>> SIG=0908bdc773bda996582bd23bf9192761, Primary 
>> Jul 08 05:41:45 twister 128.146.194.17(feed)[26069] NOTE: topo:
>> 128.146.194.17 {{ANY, (.*)}} 
>> Jul 08 05:43:51 twister 128.146.194.17(feed)[26069] ERROR: Couldn't
>> flush connection; nullproc_6() failure to 128.146.194.17: RPC: Unable to
>> receive; errno = Connection reset by peer 
>> Jul 08 05:43:51 twister rpc.ldmd[25241] NOTE: child 26069 exited with
>> status 6 
>> 
>> 
>> *NOTIFYME OUTPUT FROM TWISTER2 TO TWISTER: *
>> *
>> *
>> *
>> [ldm@twister2 ~]$ notifyme -vl - -h twister.sbs.ohio-state.edu
>> <http://twister.sbs.ohio-state.edu>
>> Jul 08 16:02:16 notifyme[27739] NOTE: Starting Up:
>> twister.sbs.ohio-state.edu <http://twister.sbs.ohio-state.edu>:
>> 20110708160216.486 TS_ENDT {{ANY,  ".*"}}
>> Jul 08 16:02:16 notifyme[27739] NOTE: LDM-5 desired product-class:
>> 20110708160216.486 TS_ENDT {{ANY,  ".*"}}
>> Jul 08 16:02:16 notifyme[27739] INFO: Resolving
>> twister.sbs.ohio-state.edu <http://twister.sbs.ohio-state.edu> to
>> 128.146.194.91 took 0.002285 seconds
>> Jul 08 16:02:16 notifyme[27739] NOTE:
>> NOTIFYME(twister.sbs.ohio-state.edu <http://twister.sbs.ohio-state.edu>): OK
> 
> Does the notifyme(1) process on Twister2 print any notifications?
> 
> Regards,
> Steve Emmerson

• Follow-Ups:
  • Re: [ldm-users] Downstream LDM Problems
    • From: Gilbert Sebenste

• References:
  • [ldm-users] Downstream LDM Problems
    • From: Phil Birnie