[Pacemaker] Jboss with httpd proxy_balancer module

[Andrew Beekhof]

On 16 Apr 2014, at 8:10 pm, orlste at tiscali.it wrote:

> Hi all,
> 
>  I've a problem to integrate in pacemaker the apache-module for jboss, on a two-node cluster with a pacemaker configuration already existing.
> 
> I try to use apache:ocf mdule as follow:
> 
> primitive apache ocf:heartbeat:apache \
>         params configfile="/opt/jboss/httpd/httpd/conf/httpd.conf" \
>         params httpd="/opt/jboss/httpd/sbin/httpd" \
>         op start interval="0" timeout="40" \
>         op stop interval="0" timeout="60" \
>         op monitor interval="120s" timeout="60s" \
>         meta target-role="Started"
> 
> But I get following error on messages:
> 
> attrd[13343]:   notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-apache (<null>)
> attrd[13343]:   notice: attrd_perform_update: Sent delete 5565: node=toemaprend1, attr=fail-count-apache, id=<n/a>, set=(null), section=status
> attrd[13343]:   notice: attrd_perform_update: Sent delete 5567: node=toemaprend1, attr=fail-count-apache, id=<n/a>, set=(null), section=status
> crmd[13345]:  warning: decode_transition_key: Bad UUID (crm_resource.c) in sscanf result (4) for 35914:0:0:crm_resource.c  

That one is fixed in a later version, you can ignore it though.

>              
> apache(apache)[35916]: INFO: apache not running
> crmd[13345]:   notice: process_lrm_event: LRM operation apache_monitor_0 (call=10812, rc=7, cib-update=3121, confirmed=true) not running

So far so good.

> apache(apache)[35954]: INFO: apache not running
> apache(apache)[35954]: INFO: waiting for apache /opt/jboss/httpd/httpd/conf/httpd.conf to come up
> apache(apache)[35954]: INFO: apache not running
> apache(apache)[35954]: INFO: waiting for apache /opt/jboss/httpd/httpd/conf/httpd.conf to come up
> ...
> lrmd[13342]:  warning: child_timeout_callback: apache_start_0 process (PID 35954) timed out
> lrmd[13342]:  warning: operation_finished: apache_start_0:35954 - timed out after 40000ms

Anything in the apache log files?
Perhaps edit the apache agent to include 'set -x' at the top.  That will produce a tonne of logging too.

> crmd[13345]:    error: process_lrm_event: LRM operation apache_start_0 (10815) Timed Out (timeout=40000ms)
> attrd[13343]:   notice: attrd_ais_dispatch: Update relayed from toemaprend2
> attrd[13343]:   notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-apache (INFINITY)
> attrd[13343]:   notice: attrd_perform_update: Sent update 5571: fail-count-apache=INFINITY
> attrd[13343]:   notice: attrd_ais_dispatch: Update relayed from toemaprend2
> attrd[13343]:   notice: attrd_trigger_update: Sending flush op to all hosts for: last-failure-apache (1397641676)
> attrd[13343]:   notice: attrd_perform_update: Sent update 5573: last-failure-apache=1397641676
> attrd[13343]:   notice: attrd_ais_dispatch: Update relayed from toemaprend2
> attrd[13343]:   notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-apache (INFINITY)
> attrd[13343]:   notice: attrd_perform_update: Sent update 5575: fail-count-apache=INFINITY
> attrd[13343]:   notice: attrd_ais_dispatch: Update relayed from toemaprend2
> attrd[13343]:   notice: attrd_trigger_update: Sending flush op to all hosts for: last-failure-apache (1397641676)
> attrd[13343]:   notice: attrd_perform_update: Sent update 5577: last-failure-apache=1397641676
> apache(apache)[39199]: INFO: apache is not running.
> apache(apache)[39199]: INFO: apache children were signalled (SIGTERM)
> apache(apache)[39199]: INFO: apache children were signalled (SIGHUP)
> crmd[13345]:   notice: process_lrm_event: LRM operation apache_stop_0 (call=10818, rc=0, cib-update=3123, confirmed=true) ok
> 
> On crm status:
> 
> Failed actions:
>     apache_start_0 (node=toemaprend2, call=551, rc=1, status=Timed Out): unknown error
>     apache_start_0 (node=toemaprend1, call=10815, rc=1, status=Timed Out): unknown error
> 
> So i try to modify the config with anything:ocf and it works for start/stop and migrate:
> 
> primitive res_web_ha ocf:heartbeat:anything \
> params binfile="/opt/jboss/httpd/sbin/apachectl" cmdline_options="start" \
> operations $id="res_web_ha-operations" \
> op start interval="0" timeout="20" \
> op stop interval="0" timeout="20" \
> op monitor interval="10" timeout="20" start-delay="0"
> 
> But I have failure on monitoring:
> 
> lrmd[13342]:   notice: operation_finished: res_web_ha_monitor_0:25962 [ /usr/lib/ocf/resource.d/heartbeat/anything: line 60: kill: (23849) - No such process ]
> crmd[13345]:   notice: process_lrm_event: LRM operation res_web_ha_monitor_0 (call=10851, rc=0, cib-update=3143, confirmed=true) ok
> lrmd[13342]:   notice: operation_finished: res_web_ha_monitor_10000:25977 [ /usr/lib/ocf/resource.d/heartbeat/anything: line 60: kill: (23849) - No such process ]
> crmd[13345]:   notice: process_lrm_event: LRM operation res_web_ha_monitor_10000 (call=10854, rc=0, cib-update=3144, confirmed=false) ok
> lrmd[13342]:   notice: operation_finished: res_web_ha_monitor_10000:26522 [ /usr/lib/ocf/resource.d/heartbeat/anything: line 60: kill: (23849) - No such process ]
> lrmd[13342]:   notice: operation_finished: res_web_ha_monitor_10000:27030 [ /usr/lib/ocf/resource.d/heartbeat/anything: line 60: kill: (23849) - No such process ]
> lrmd[13342]:   notice: operation_finished: res_web_ha_monitor_10000:27515 [ /usr/lib/ocf/resource.d/heartbeat/anything: line 60: kill: (23849) - No such process ]
> 
> and no error on crm status.
> 
> I could use the anything:ocf config, but in this way I don't know how to monitor the resource.
> 
> Can you help me?
> 
> Thanks,
> 
>  Ste
> 
> 
> 
> Scopri istella, il nuovo motore per il web italiano.
> Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video.
> Usa istella, vai su http://www.istella.it?wtk=amc138614816829636
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140422/96563713/attachment-0004.sig>