[Linux-ha-dev] help with starting apache

2006-04-04 Thread Diego Leider
Hi,

I want to do something as simple as starting the apache webserver on one
of the machines running heartbeat.
When i run the command crm_resource -V -W -r WebServerApache i get 

crm_resource[9607]: 2006/04/04_12:03:11 WARN:
mask(unpack.c:unpack_rsc_op): Processing failed op
(WebServerApache_monitor_0) for WebServerApache on yin
crm_resource[9607]: 2006/04/04_12:03:11 WARN:
mask(unpack.c:unpack_rsc_op): Processing failed op
(WebServerApache_stop_0) for WebServerApache on yin
crm_resource[9607]: 2006/04/04_12:03:11 WARN:
mask(unpack.c:unpack_rsc_op): Handling failed stop for WebServerApache
on yin
resource WebServerApache is running on: yin

But when i check if apache is really running on yin i can see it is not
up.

Can somebody please point me in the right direction.
cib.xml and log file are attached!

Cheers,


-- 

Diëgo Leider


Software Developement
Phone:  +31 (0)36 5483783
Fax:+31 (0)36 5483788
Email:  [EMAIL PROTECTED]

Daisycon B.V.
P.J. Oudweg 5
1314CH, Almere
The Netherlands

 cib generated=true cib_feature_revision=1.2 admin_epoch=0 have_quorum=true num_peers=3 crm_feature_set=1.0.4 debug_source=create_node_entry last_written=Tue Apr  4 11:56:41 2006 dc_uuid=ce80aab7-3b5e-4a4c-afa7-9049b7258cac ccm_transition=15 epoch=40 num_updates=707
   configuration
 crm_config
   cluster_property_set id=default
 attributes
   nvpair id=symmetric_cluster name=symmetric_cluster value=true/
   nvpair id=no_quorum_policy name=no_quorum_policy value=stop/
   nvpair id=stonith_enabled name=stonith_enabled value=false/
   nvpair id=short_resource_names name=short_resource_names value=true/
   nvpair id=is_managed_default name=is_managed_default value=true/
   nvpair id=transition_idle_timeout name=transition_idle_timeout value=6/
   nvpair id=default_resource_stickiness name=default_resource_stickiness value=0/
   nvpair id=stop_orphan_resources name=stop_orphan_resources value=false/
   nvpair id=stop_orphan_actions name=stop_orphan_actions value=false/
   nvpair id=remove_after_stop name=remove_after_stop value=false/
 /attributes
   /cluster_property_set
 /crm_config
 nodes
   node id=ce80aab7-3b5e-4a4c-afa7-9049b7258cac uname=athena type=normal/
   node id=80b40b46-39d3-4e91-a37e-d75118eb4809 uname=yin type=normal/
   node id=c4962a33-6a72-4a43-aa14-0b9397e71466 uname=ceres type=normal/
   node id=dedfc24b-0b10-493f-ae9a-52d3c1a1c523 uname=venus type=normal/
 /nodes
 constraints/
 resources
   primitive id=WebServerIP class=ocf type=IPaddr provider=heartbeat
 instance_attributes
   attributes
 nvpair id=WebServerIP_ip name=ip value=192.168.1.79/
   /attributes
 /instance_attributes
 operations
   op id=1 name=stop timeout=3s/
   op id=2 name=start timeout=5s/
   op id=3 name=monitor interval=10s timeout=3s/
   op id=4 name=monitor interval=1min timeout=5s/
 /operations
   /primitive
   primitive class=ocf provider=heartbeat id=WebServerApache type=Apache
 operations
   op id=WebServerApache_op1 name=stop timeout=10s/
   op id=WebServerApache_op2 name=start timeout=10s on_fail=stop/
   op id=WebServerApache_op3 name=monitor interval=10s timeout=3s on_fail=stop/
 /operations
 instance_attributes
   attributes
 nvpair id=apache_config name=apache_config value=/etc/httpd/conf/httpd.conf/
   /attributes
 /instance_attributes
   /primitive
 /resources
   /configuration
 /cib
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): +   
/transient_attributes
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): +   lrm
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): + 
lrm_resources/
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): +   /lrm
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): + /node_state
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): +   /status
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): + /cib
Apr  4 11:45:31 yin cib: [19866]: WARN: mask(callbacks.c:cib_process_request): 
A-Sync reply to unknown failed: reply failed
Apr  4 11:45:31 yin cib: [19866]: info: 
mask(callbacks.c:cib_common_callback_worker): Processing cib_update operation 
from 19869/cib_rw
Apr  4 11:45:31 yin cib: [19866]: info: mask(notify.c:cib_diff_notify): 
Local-only Change (client:19869, call: 12): 0.39.687 (ok)
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): - cib
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): -   status
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): - node_state 
origin=do_dc_join_offer_all id=80b40b46-39d3-4e91-a37e-d75118eb4809/
Apr  4 11:45:31 yin cib: [19866]: info: mask(cib:diff): - node_state 

Re: [Linux-ha-dev] help with starting apache

2006-04-04 Thread Andrew Beekhof
On Apr 4, 2006, at 12:12 PM, Diego Leider wrote:Hi,I want to do something as simple as starting the apache webserver on oneof the machines running heartbeat.When i run the command "crm_resource -V -W -r WebServerApache" i get crm_resource[9607]: 2006/04/04_12:03:11 WARN:mask(unpack.c:unpack_rsc_op): Processing failed op(WebServerApache_monitor_0) for WebServerApache on yincrm_resource[9607]: 2006/04/04_12:03:11 WARN:mask(unpack.c:unpack_rsc_op): Processing failed op(WebServerApache_stop_0) for WebServerApache on yincrm_resource[9607]: 2006/04/04_12:03:11 WARN:mask(unpack.c:unpack_rsc_op): Handling failed stop for WebServerApacheon yinmy guess is your resource agent is broken.try checking out: http://www.linux-ha.org/LSBResourceAgentspecifically the parts on status and stopping a stopped resourceresource WebServerApache is running on: yinBut when i check if apache is really running on yin i can see it is notup.Can somebody please point me in the right direction.cib.xml and log file are attached!Cheers,-- Diëgo LeiderSoftware DevelopementPhone:  +31 (0)36 5483783Fax:    +31 (0)36 5483788Email:  [EMAIL PROTECTED]Daisycon B.V.P.J. Oudweg 51314CH, AlmereThe Netherlandscib.xmlmessages___Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.orghttp://lists.linux-ha.org/mailman/listinfo/linux-ha-devHome Page: http://linux-ha.org/  -- Andrew Beekhof  "No means no, and no means yes, and everything in between and all the rest" - TISM  ___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] help with starting apache

2006-04-04 Thread Andrew Beekhof
On 4/4/06, Andrew Beekhof [EMAIL PROTECTED] wrote:


 On Apr 4, 2006, at 12:12 PM, Diego Leider wrote:

 Hi,

 I want to do something as simple as starting the apache webserver on one
 of the machines running heartbeat.
 When i run the command crm_resource -V -W -r WebServerApache i get

 crm_resource[9607]: 2006/04/04_12:03:11 WARN:
 mask(unpack.c:unpack_rsc_op): Processing failed op
 (WebServerApache_monitor_0) for WebServerApache on yin
 crm_resource[9607]: 2006/04/04_12:03:11 WARN:
 mask(unpack.c:unpack_rsc_op): Processing failed op
 (WebServerApache_stop_0) for WebServerApache on yin
 crm_resource[9607]: 2006/04/04_12:03:11 WARN:
 mask(unpack.c:unpack_rsc_op): Handling failed stop for WebServerApache
 on yin


 my guess is your resource agent is broken.
 try checking out: http://www.linux-ha.org/LSBResourceAgent
 specifically the parts on status and stopping a stopped resource

actually you got the resource type wrong.  Apache should be all lowercase.
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] help with starting apache

2006-04-04 Thread Andrew Beekhof
On 4/4/06, Diego Leider [EMAIL PROTECTED] wrote:
 I specified use_logd in ha.cf. I attached /var/log/messages from one
 of the machines. Is this what you mean?

 On Tue, 2006-04-04 at 13:30 +0200, Andrew Beekhof wrote:
  On 4/4/06, Diego Leider [EMAIL PROTECTED] wrote:
   I changed type=Apache to lower case but I get the same result.
   Even when I specify primitive class=heartbeat provider=heartbeat
   id=WebServerApache type=apache in the cib.xml file i get the same
   result.
 
  can you post updated logs?

You've got yourself into a bit of a mess here because you can't stop a
resource that has no resource agent.

The easiest way out is to shut down both nodes and start them up again.

There is a way to do this without stopping the nodes but its more complex.
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/