There is option in amfpm to give PID file path: amfpm -h -f, --file=FILE Path to pidfile
Thanks, Praveen On 28-May-14 12:04 PM, opensaf dev wrote: > Thanks a lot Praveen. It worked except one case where I have a > constraint on the PID file location. I am using a PID file location > other then /var/run under the particular user /var/run/UserX/x.pid. In > this case I have the active monitor failed issue after couple of > seconds the component being instantiated. > > Is there a way we can get rid of this? > > Thanks > Dev > > > On Wed, May 21, 2014 at 9:36 PM, praveen malviya > <[email protected] <mailto:[email protected]>> wrote: > > Hi, > For passive monitoring configuration looks like this: > > <attr> > <name>saAmfCtRelPathAmStartCmd</name> > <value>amfpm</value> > </attr> > <attr> > <name>saAmfCtDefAmStartCmdArgv</name> > <value>-a -r comprestart</value> > </attr> > <attr> > <name>saAmfCtRelPathAmStopCmd</name> > <value>amfpm</value> > </attr> > <attr> > <name>saAmfCtDefAmStopCmdArgv</name> > <value>-o</value> > </attr> > > Please check PID file path and amfpm should be a link to > /usr/local/sbin/amfpm in the path given in node bundle. > Please check the amfpm -help for more > > usage: amfpm --start | --stop [OPTIONS] [DN] > > Start/stop AMF passive monitoring of an AMF component. > > -a, --start Start passive monitoring > -f, --file=FILE Path to pidfile > -o, --stop Stop passive monitoring > -p, --pid=PID PID > -r, --recrec=RECREC Recommended recovery > > Valid recommended recovery names: > norec (default), comprestart, compfailover, nodeswitchover > nodefailover, nodefailfast, clusterreset, apprestart, > containerrestart > > If no DN is specified, the environment variable > SA_AMF_COMPONENT_NAME is used. > If no pidfile or PID is specified, the pidfile name is > /var/run/<basename>.pid > basename is the RDN attribute value of the DN. > for example DN "safComp=snmpd,safSu=1,safSg=2N,safApp=net-snmp" > gives basename snmpd > The command will wait forever for the pidfile to appear in the > file system. > AMF timeouts (e.g. saAmfCtDefClcCliTimeout) solves the "forever" > problem. > > Thanks, > Praveen > > > On 22-May-14 9:28 AM, opensaf dev wrote: > > Hi, > > I am trying to create a non-sa-aware component for a third > party daemon > like snmpd example using amfpm. However, as soon as the SI is > being > assigned active, I am getting the below error. > > *"Component faulted due to ''activeMonitorFailed".* I tried to > get more > > logs but with info level on for the amfnd only the above line > was displayed. > > Anybody has faced similar issues, anything obvious missed or > what can be > the potential causes for this error. > > Appreciate for any help. > > Thanks > Dev > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - > For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing > platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Opensaf-users mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/opensaf-users > > > ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
