Dejan Muhamedagic a écrit :
Hi,

On Thu, Sep 04, 2008 at 09:48:14AM +0200, Franck Huet wrote:
Thanks Lars

It's works better now (with corrected mistakes ..) but I have now 2 ip
(192.168.4.4 mounted) and 2 apache server ....

and this which is flooding my logs on my 2 nodes :

apache[3428]:   2008/09/03_15:09:57 INFO: apache not running
apache[3428]:   2008/09/03_15:09:58 INFO: waiting for apache
/usr/local/apache-preprod/conf/httpd.conf to come up
apache[3428]:   2008/09/03_15:09:59 INFO: apache not running
apache[3428]:   2008/09/03_15:09:59 INFO: waiting for apache
/usr/local/apache-preprod/conf/httpd.conf to come up
apache[3428]:   2008/09/03_15:10:00 INFO: apache not running
apache[3428]:   2008/09/03_15:10:00 INFO: waiting for apache
/usr/local/apache-preprod/conf/httpd.conf to come up

This means that the monitor operation's constantly failing. You
need to make sure that the status module is loaded and that
access to it is allowed from localhost.

Well. Stupid question : What is the status module ? How to load it ?

It seems to work fine now, but because of this flooding, I can't stop heartbeat without a kill -9 on apache.



ps -ef (on node1 and node2 - pid are differents of course) :

root      3462     1  0 15:05 ?        00:00:00
/usr/local/apache-preprod/bin/httpd -DSTATUS -f
/usr/local/apache-preprod/conf/httpd.conf
daemon    3480  3462  0 15:05 ?        00:00:00
/usr/local/apache-preprod/bin/httpd -DSTATUS -f
/usr/local/apache-preprod/conf/httpd.conf
daemon    3481  3462  0 15:05 ?        00:00:00
/usr/local/apache-preprod/bin/httpd -DSTATUS -f
/usr/local/apache-preprod/conf/httpd.conf
daemon    3482  3462  0 15:05 ?        00:00:00
/usr/local/apache-preprod/bin/httpd -DSTATUS -f
/usr/local/apache-preprod/conf/httpd.conf
daemon    3483  3462  0 15:05 ?        00:00:00
/usr/local/apache-preprod/bin/httpd -DSTATUS -f
/usr/local/apache-preprod/conf/httpd.conf
daemon    3484  3462  0 15:05 ?        00:00:00
/usr/local/apache-preprod/bin/httpd -DSTATUS -f
/usr/local/apache-preprod/conf/httpd.conf

and ocf-tester gives that :

[EMAIL PROTECTED] ~]# ocf-tester -n test -o
configfile=/usr/local/apache-preprod/conf/httpd.conf
/usr/lib/ocf/resource.d/heartbeat/apache
Beginning tests for /usr/lib/ocf/resource.d/heartbeat/apache...
* rc=2: Validation failed.  Did you supply enough options with -o ?
Aborting tests

Not very informative ;-) Perhaps there's something in the logs?

Thanks,

Dejan

=> I'm trying to understand http://linux-ha.org/OCFResourceAgent :)


Heartbeat worked fine last time on a suse ... It's different today with
a redhat ...


Franck


Lars Marowsky-Bree a ?crit :
On 2008-09-03T10:54:12, Franck Huet <[EMAIL PROTECTED]> wrote:

Ok.

I use the orginal apache in /etc/ha.d/resources.apache

Here is now my haresources :

/noeud1 IPaddr::192.168.4.4 apache::/usr/local/apache-preprod/conf/httpd.conf/
If that is indeed cut & paste, you have several errors. the "/" at the
beginning and at the end of the lines, for example.

ResourceManager[28132]: 2008/09/03_10:35:54 info: Running /etc/ha.d/resource.d/apache /usr/local/apache-preprod/conf/httpd.conf start
apache[28433]:  2008/09/03_10:35:55 INFO: apache not running
It's not working. It's calling "start", but a later "monitor" isn't
working.

Try "ocf-tester -n test -o
configfile=/usr/local/apache-preprod/conf/httpd.conf
/usr/lib/ocf/resource.d/heartbeat/apache" and see whether that passes
with your configuration.

ResourceManager[3680]: 2008/09/03_10:37:19 ERROR: Cannot locate resource script noeud1
You have a typo in haresources. Make sure that the file is indeed
exactly the same on both nodes.


ResourceManager[3680]: 2008/09/03_10:37:19 info: Releasing resource group: noeud1 IPaddr::192.168.4.4 noeud1 IPaddr::192.168.4.4 apache::/usr/local/apache-preprod/conf/httpd.conf
You have "noeud1" appear twice.


Well. What is wrong now ?
Your configuration ;-)


Regards,
    Lars

_______________________________________________
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


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to