Or perhaps the communication error is between your controllers in case you are observing the failure on the STANDBY controller.
Mathi. ----- [email protected] wrote: > Hi, > > Yes, this would generally mean that there is a communication error > between your payload > and the controller. The payload is unable to see the controller. > > You may enable the traces of IMMND on the payload and check the > syslog, IMMNDtrace (and/or mds.log) > for any evidence related to the communication error. > > (The syslog on the controller should also help understand if the > controller is able to see the payload.) > > - Mathi. > > ----- [email protected] wrote: > > > So you mean immd on active controller somehow failed? > > > > > > Sent from Samsung Mobile > > > > > > -------- Original message -------- > > From: Neelakanta Reddy > > Date:2015/01/23 1:13 PM (GMT+08:00) > > To: Yao Cheng LIANG ,[email protected] > > Subject: Re: [users] immnd start failure > > > > Hi, > > > > Here rc=2 means FAILURE. > > > > The cause of the issue is active IMMD is not present in the > cluster. > > IMMND of payload/controllere tries to send to IMMD. > > > > check why active IMMD is not present in the cluster. > > > > /Neel. > > > > On Friday 23 January 2015 10:35 AM, Yao Cheng LIANG wrote: > > So this a communication error? Or what may cause this issue? Whar > rc=2 > > means? > > > > Thanks. > > > > Ted > > > > > > Sent from Samsung Mobile > > > > > > -------- Original message -------- > > From: Neelakanta Reddy > > Date:2015/01/23 12:59 PM (GMT+08:00) > > To: Yao Cheng LIANG > > > ,[email protected]<mailto:[email protected]> > > Subject: Re: [users] immnd start failure > > > > Hi, > > > > IMMND always send to active IMMD controller. > > > > /Neel. > > > > On Friday 23 January 2015 10:27 AM, Yao Cheng LIANG wrote: > > Here you mean immd on active controller or on local(standby) node? > > > > Thanks. > > > > Ted > > > > > > Sent from Samsung Mobile > > > > > > -------- Original message -------- > > From: Neelakanta Reddy > > Date:2015/01/23 12:33 PM (GMT+08:00) > > To: > > > [email protected],Yao<mailto:[email protected],Yao> > > Cheng LIANG > > Subject: Re: [users] immnd start failure > > > > Hi, > > > > This is the case when IMMND tries to send to IMMD, But IMMD is not > > available in the cluster. > > Once the IMMD is available the message willnot appear. > > > > /Neel. > > > > On Friday 23 January 2015 06:49 AM, Yao Cheng LIANG wrote: > > > BTW, it continues print these messages even after I reboot this > node > > and only after I reboot active controller it can be successfully > > started. > > > > > > -----Original Message----- > > > From: Yao Cheng LIANG [mailto:[email protected]] > > > Sent: Friday, January 23, 2015 9:18 AM > > > To: > > > [email protected]<mailto:[email protected]> > > > Subject: [users] immnd start failure > > > > > > All, > > > > > > When I was starting OpenSAF controller, it prints errors below. > > Could anyone tell me what caused this? Is "Rc:2" means root cause > is > > 2? > > > > > > Jan 22 13:04:30 localhost osafimmnd[2231]: MDS Send Failed to > > service:IMMD rc:2 Jan 22 13:04:30 localhost osafimmnd[2231]: MDS > Send > > Failed to service:IMMD rc:2 Jan 22 13:04:30 localhost > osafimmnd[2231]: > > MDS Send Failed to service:IMMD rc:2 Jan 22 13:04:30 localhost > > osafimmnd[2231]: MDS Send Failed to service:IMMD rc:2 > > > > > > ------------------------------------------------------------------------------ > > > New Year. New Location. New Benefits. New Data Center in Ashburn, > > VA. > > > GigeNET is offering a free month of service with a new server in > > Ashburn. > > > Choose from 2 high performing configs, both with 100TB of > > bandwidth. > > > Higher redundancy.Lower latency.Increased capacity.Completely > > compliant. > > > http://p.sf.net/sfu/gigenet > > > _______________________________________________ > > > Opensaf-users mailing list > > > > > > [email protected]<mailto:[email protected]> > > > https://lists.sourceforge.net/lists/listinfo/opensaf-users > > > > > > > > > ------------------------------------------------------------------------------ > > > New Year. New Location. New Benefits. New Data Center in Ashburn, > > VA. > > > GigeNET is offering a free month of service with a new server in > > Ashburn. > > > Choose from 2 high performing configs, both with 100TB of > > bandwidth. > > > Higher redundancy.Lower latency.Increased capacity.Completely > > compliant. > > > http://p.sf.net/sfu/gigenet > > > _______________________________________________ > > > Opensaf-users mailing list > > > > > > [email protected]<mailto:[email protected]> > > > https://lists.sourceforge.net/lists/listinfo/opensaf-users > > > > > > > > > ------------------------------------------------------------------------------ > > New Year. New Location. New Benefits. New Data Center in Ashburn, > VA. > > GigeNET is offering a free month of service with a new server in > > Ashburn. > > Choose from 2 high performing configs, both with 100TB of > bandwidth. > > Higher redundancy.Lower latency.Increased capacity.Completely > > compliant. > > http://p.sf.net/sfu/gigenet > > _______________________________________________ > > Opensaf-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/opensaf-users ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
