Hi, From: David Vossel <[email protected]> > Subject: Re: [Linux-HA] Getting Unknown Error for HA + Asterisk > To: General Linux-HA mailing list <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > > > > > ----- Original Message ----- > > From: "Ahmed Munir" <[email protected]> > > To: [email protected] > > Sent: Monday, April 1, 2013 3:07:16 PM > > Subject: Re: [Linux-HA] Getting Unknown Error for HA + Asterisk > > > > Hi, > > > > As I ran sipsak command: sipsak -vv -s sip:[email protected] (virtual IP) > the > > output I'm getting is listed below; > > Is the virtual IP configured to always start before asterisk? >
No. If I use 'order asterisk-after-IP inf: IPaddr_10_3_152_103 p_asterisk' and stop heartbeat service in node:asterisk1, it doesn't stop heartbeat service and remains active. After removing the line from configuration it is working good i.e. stop heartbeat service and resources move to node: asterisk2. For monitor_sipuri, do you think in resource agent: asterisk, $OCF_RESKEY_monitor_sipuri isn't declare in 'meta_data' section which is causing me issue? > > -- Vossel > > > > > root@asterisk1> sipsak -vv -s sip:[email protected] > > > > message received: > > SIP/2.0 200 OK > > Via: SIP/2.0/UDP 10.3.152.105:37331 > > ;branch=z9hG4bK.2aad900e;alias;received=10.3.152.103;rport=37331 > > From: sip:[email protected]:37331;tag=305220cf > > To: sip:[email protected];tag=as0a95ab80 > > Call-ID: [email protected] > > CSeq: 1 OPTIONS > > Server: Asterisk PBX 10.12.1 > > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, > > PUBLISH > > Supported: replaces, timer > > Contact: <sip:10.3.152.103:5060> > > Accept: application/sdp > > Content-Length: 0 > > > > > > > > ** reply received after 0.300 ms ** > > SIP/2.0 200 OK > > final received > > > > As I'm also seeing its' hits in Asterisk CLI as below; > > > > <--- SIP read from UDP:10.3.152.103:51418 ---> > > OPTIONS sip:[email protected] SIP/2.0 > > Via: SIP/2.0/UDP 10.3.152.105:51418;branch=z9hG4bK.2ebc3a37;rport;alias > > From: sip:[email protected]:51418;tag=6d4212e4 > > To: sip:[email protected] > > Call-ID: [email protected] > > CSeq: 1 OPTIONS > > Contact: sip:[email protected]:51418 > > Content-Length: 0 > > Max-Forwards: 70 > > User-Agent: sipsak 0.9.6 > > Accept: text/plain > > > > <-------------> > > --- (11 headers 0 lines) --- > > Looking for 42 in sip-calls (domain 10.3.152.103) > > > > <--- Transmitting (NAT) to 10.3.152.103:51418 ---> > > SIP/2.0 200 OK > > Via: SIP/2.0/UDP 10.3.152.105:51418 > > ;branch=z9hG4bK.2ebc3a37;alias;received=10.3.152.103;rport=51418 > > From: sip:[email protected]:51418;tag=6d4212e4 > > To: sip:[email protected];tag=as6d38b059 > > Call-ID: [email protected] > > CSeq: 1 OPTIONS > > Server: Asterisk PBX 10.12.1 > > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, > > PUBLISH > > Supported: replaces, timer > > Contact: <sip:10.3.152.103:5060> > > Accept: application/sdp > > Content-Length: 0 > > > > > > <------------> > > Scheduling destruction of SIP dialog '[email protected]' in 32000 > ms > > (Method: OPTIONS) > > > > After enabling 'paras monitor_sipur="sip:[email protected]" ' in HA > > configuration, listing down the errors below; > > > > IPaddr[15287]: 2013/04/01_14:23:52 INFO: ifconfig eth0:0 down > > Apr 01 14:23:52 asterisk1 crmd: [3921]: info: process_lrm_event: LRM > > operation IPaddr_10_3_152_103_stop_0 (call=14, rc=0, cib-update=26, > > confirmed=true) ok > > Apr 01 14:23:53 asterisk1 lrmd: [3918]: info: cancel_op: operation > > monitor[11] on ocf::asterisk::p_asterisk for client 3921, its parameters: > > CRM_meta_interval=[10000] realtime=[true] CRM_meta_timeout=[120000] > > crm_feature_set=[3.0.1] CRM_meta_name=[monitor] cancelled > > Apr 01 14:23:53 asterisk1 crmd: [3921]: info: do_lrm_rsc_op: Performing > > key=8:20:0:0ab29917-7ac1-4574-9876-7631de6fb13b op=p_asterisk_stop_0 ) > > Apr 01 14:23:53 asterisk1 lrmd: [3918]: info: rsc:p_asterisk:15: stop > > Apr 01 14:23:53 asterisk1 crmd: [3921]: info: process_lrm_event: LRM > > operation p_asterisk_monitor_10000 (call=11, status=1, cib-update=0, > > confirmed=true) Cancelled > > asterisk[15303]: 2013/04/01_14:23:53 INFO: Asterisk PBX is not > > running > > asterisk[15303]: 2013/04/01_14:23:53 INFO: Asterisk PBX is not > > running > > asterisk[15303]: 2013/04/01_14:23:53 INFO: Asterisk PBX stopped > > Apr 01 14:23:53 asterisk1 crmd: [3921]: info: process_lrm_event: LRM > > operation p_asterisk_stop_0 (call=15, rc=0, cib-update=27, > confirmed=true) > > ok > > Apr 01 14:23:55 asterisk1 crmd: [3921]: info: do_lrm_rsc_op: Performing > > key=4:20:0:0ab29917-7ac1-4574-9876-7631de6fb13b op=p_asterisk_start_0 ) > > Apr 01 14:23:55 asterisk1 lrmd: [3918]: info: rsc:p_asterisk:16: start > > asterisk[15351]: 2013/04/01_14:23:55 INFO: Asterisk PBX is not > > running > > asterisk[15351]: 2013/04/01_14:23:55 INFO: 0 active channels 0 > > active calls 0 calls processed > > asterisk[15351]: 2013/04/01_14:23:58 ERROR: (type: 3, code: 1): > from > > 10.3.152.103 > > asterisk[15351]: 2013/04/01_14:24:00 INFO: 0 active channels 0 > > active calls 0 calls processed > > asterisk[15351]: 2013/04/01_14:24:03 ERROR: (type: 3, code: 1): > from > > 10.3.152.103 > > asterisk[15351]: 2013/04/01_14:24:05 INFO: 0 active channels 0 > > active calls 0 calls processed > > asterisk[15351]: 2013/04/01_14:24:08 ERROR: (type: 3, code: 1): > from > > 10.3.152.103 > > asterisk[15351]: 2013/04/01_14:24:10 INFO: 0 active channels 0 > > active calls 0 calls processed > > asterisk[15351]: 2013/04/01_14:24:13 ERROR: (type: 3, code: 1): > from > > 10.3.152.103 > > > > > > I also tested/debug resource agent as in the link: > > http://clusterlabs.org/wiki/Debugging_Resource_Failures setting > > OCF_RESKEY_monitor_sipuri=sip:[email protected] it is returning me the > code 0 > > i.e. ocf success. > > > > Please advise, what steps need to be done to overcome this issue. > > > > > > > From: David Vossel <[email protected]> > > > Subject: Re: [Linux-HA] Getting Unknown Error > > > To: General Linux-HA mailing list <[email protected]> > > > Message-ID: <[email protected]> > > > Content-Type: text/plain; charset=utf-8 > > > > > > ----- Original Message ----- > > > > From: "Ahmed Munir" <[email protected]> > > > > To: [email protected] > > > > Sent: Friday, March 29, 2013 11:26:50 AM > > > > Subject: [Linux-HA] Getting Unknown Error > > > > > > > > Hi, > > > > > > > > I recently configured Linux HA for Asterisk service (using Asterisk > > > > resource agent downloaded from link: > > > > > > > > https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/asterisk > > > > ). > > > > As per configuration it is working good but when I include > > > "monitor_sipuri=" > > > > sip:[email protected]" " parameter in primitive section it is giving > me an > > > > errors like listed below; > > > > > > > > root@asterisk2 ~> crm_mon -1 > > > > > > > > ============ > > > > > > > > Last updated: Thu Mar 28 06:09:54 2013 > > > > > > > > Stack: Heartbeat > > > > > > > > Current DC: asterisk2 (b966dfa2-5973-4dfc-96ba-b2d38319c174) - > partition > > > > with quorum > > > > > > > > Version: 1.0.12-unknown > > > > > > > > 2 Nodes configured, unknown expected votes > > > > > > > > 1 Resources configured. > > > > > > > > ============ > > > > > > > > > > > > > > > > Online: [ asterisk1 asterisk2 ] > > > > > > > > > > > > > > > > Resource Group: group_1 > > > > > > > > asterisk_2 (lsb:asterisk): Started asterisk1 > > > > > > Do you have two asterisk instances in the cluster, a LSB and OCF one?! > I'm > > > confused by this. > > > > > > > > > > > IPaddr_10_3_152_103 (ocf::heartbeat:IPaddr): > Started > > > > asterisk1 > > > > > > > > > > > > > > > > Failed actions: > > > > > > > > p_asterisk_start_0 (node=asterisk1, call=64, rc=1, > status=complete): > > > > unknown error > > > > > > > > p_asterisk_start_0 (node=asterisk2, call=20, rc=1, > status=complete): > > > > unknown error > > > > > > > > > > > > I tested the 'sipsak' tool on cli, it is executing without any issue > i.e. > > > > returning 200 OK but when I remove this "param monitor_sipuri" I'm > not > > > > getting the errors. > > > > > > Did you use the exact same SIP URI and test it on the box asterisk is > > > running on? Look through the log output. Perhaps the resource agent is > > > outputting some information that could give you a clue as to what is > going > > > on. > > > > > > A trick I'd use is running wireshark on the box the asterisk resource > is > > > starting on, watch the OPTION request come in and see how it is > responded > > > to for the resource agent to rule out any problems there. > > > > > > -- Vossel > > > > > > > Listing down the configuration below which I configured; > > > > > > > > node $id="887bae58-1eb6-47d1-b539-d12a2ed3d836" asterisk1 > > > > node $id="b966dfa2-5973-4dfc-96ba-b2d38319c174" asterisk2 > > > > primitive IPaddr_10_3_152_103 ocf:heartbeat:IPaddr \ > > > > op monitor interval="5s" timeout="20s" \ > > > > params ip="10.3.152.103" > > > > primitive p_asterisk ocf:heartbeat:asterisk \ > > > > op monitor interval="10s" \ > > > > params realtime="true" > > > > group group_1 p_asterisk IPaddr_10_3_152_103 \ > > > > meta target-role="Started" > > > > location rsc_location_group_1 group_1 \ > > > > rule $id="preferred_location_group_1" 100: #uname eq > asterisk1 > > > > colocation asterisk-with-ip inf: p_asterisk IPaddr_10_3_152_103 > > > > property $id="cib-bootstrap-options" \ > > > > symmetric-cluster="true" \ > > > > no-quorum-policy="stop" \ > > > > default-resource-stickiness="0" \ > > > > stonith-enabled="false" \ > > > > stonith-action="reboot" \ > > > > startup-fencing="true" \ > > > > stop-orphan-resources="true" \ > > > > stop-orphan-actions="true" \ > > > > remove-after-stop="false" \ > > > > default-action-timeout="120s" \ > > > > is-managed-default="true" \ > > > > cluster-delay="60s" \ > > > > pe-error-series-max="-1" \ > > > > pe-warn-series-max="-1" \ > > > > pe-input-series-max="-1" \ > > > > dc-version="1.0.12-unknown" \ > > > > cluster-infrastructure="Heartbeat" > > > > > > > > And the status I'm getting is listed below; > > > > > > > > root@asterisk1 ~> crm_mon -1 > > > > ============ > > > > Last updated: Fri Mar 29 12:25:10 2013 > > > > Stack: Heartbeat > > > > Current DC: asterisk1 (887bae58-1eb6-47d1-b539-d12a2ed3d836) - > partition > > > > with quorum > > > > Version: 1.0.12-unknown > > > > 2 Nodes configured, unknown expected votes > > > > 1 Resources configured. > > > > ============ > > > > > > > > Online: [ asterisk1 asterisk2 ] > > > > > > > > Resource Group: group_1 > > > > p_asterisk (ocf::heartbeat:asterisk): Started asterisk1 > > > > IPaddr_10_3_152_103 (ocf::heartbeat:IPaddr): Started > > > > asterisk1 > > > > > > > > > > > > Please advise to overcome this issue. > > > > > > > > -- > > > > Regards, > > > > > > > > Ahmed Munir Chohan > > > > _______________________________________________ > > > > Linux-HA mailing list > > > > [email protected] > > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > > See also: http://linux-ha.org/ReportingProblems > > > > > > > > > > > > > ------------------------------ > > > > > > _______________________________________________ > > > Linux-HA mailing list > > > [email protected] > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > See also: http://linux-ha.org/ReportingProblems > > > > > > End of Linux-HA Digest, Vol 113, Issue 1 > > > **************************************** > > > > > > > > > > > -- > > Regards, > > > > Ahmed Munir Chohan > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > > > -- Regards, Ahmed Munir Chohan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
