Then you are lucky :-D My ocf-tester doesnt know -d ...
My Ocf-tester manual is from June2011, using debian stable repos.. Maybe a too old. Lsb:apache works... but ocf would be better! Thank you anyway Matthias --- > Sorry, I dont get it. > > Thought the ocf-tester is used to see if your ra is ocf compliant. > > How to turn on debug mode? My "man ocf-tester" says: " -d Turn on RA debugging"... ;-) > > #> ocf-tester -n prim_Apache -o configfile="/etc/apache2/apache2.conf" -o > httpd="/usr/sbin/apache2" -o statusurl="http://127.0.0.1/server-status"; -o > envfiles="/etc/apache2/envvars" /usr/lib/ocf/resource.d/heartbeat/apache > > Beginning tests for /usr/lib/ocf/resource.d/heartbeat/apache... > /usr/sbin/ocf-tester: 214: /usr/sbin/ocf-tester: xmllint: not found > * rc=127: Your agent produces meta-data which does not conform to > ra-api-1.dtd > * Your agent does not support the notify action (optional) > * Your agent does not support the demote action (optional) > * Your agent does not support the promote action (optional) > * Your agent does not support master/slave (optional) > * Your agent does not support the reload action (optional) > Tests failed: /usr/lib/ocf/resource.d/heartbeat/apache failed 1 tests > --- See above and your syslog (cluster log messages). Regards, Ulrich > > You could try to test the RA with ocf-tester in debug mode: best assemble > the > config options in a small command file to execute... > >>>> "Hoffmann, Matthias" <[email protected]> schrieb am > 10.06.2014 um 11:37 in Nachricht > <3ec985b70510fe48bcc8a77e9b1ef50c70f...@exchange2010.worms.schlemmerblock.de>: > > EST)> Hi, >> >> thanks for your reply. >> >> I added "http://"; but no change at all. >> >> info ocf:heartbeat:apache -> >> >> testurl (string): test url >> URL to test. If it does not start with "http", then it's >> considered to be relative to the Listen address. >> >> At least I know when it works, when the apache server is started with >> /etc/init.d/apache2 start (and stopped again) BEFORE the cluster tries > it... >> No idea what the problem is, this envvars file export stuff didnt help.. >> >> Anything happens when the apache actually was running... but this cant be >> the solution ;( >> >> Regards, >> Matthias >> >> -----Ursprüngliche Nachricht----- >> Von: [email protected] >> [mailto:[email protected]] Im Auftrag von Ulrich Windl >> Gesendet: Dienstag, 10. Juni 2014 11:25 >> An: '[email protected]' >> Betreff: [Linux-HA] Antw: apache2 fails >> >>>>> "Hoffmann, Matthias" <[email protected]> schrieb am >> 10.06.2014 um 10:10 in Nachricht >> > <3ec985b70510fe48bcc8a77e9b1ef50c70f...@exchange2010.worms.schlemmerblock.de>: >> >> EST)> Hello, >>> >>> there is a problem with my apache2 resource -> >>> >>> primitive prim_Apache ocf:heartbeat:apache \ >>> params configfile="/etc/apache2/apache2.conf" >>> httpd="/usr/sbin/apache2" statusurl="127.0.0.1/server-status" >>> envfiles="/etc/apache2/envvars" \ >>> op monitor interval="20" timeout="30" >> >> I wonder how strict the rules for URLs are. Do you have to use "http://"; >> maybe? >> >>> >>> syslog: >>> >>> ERROR: command failed: /usr/sbin/apache2 -DSTATUS -f > /etc/apache2/apache2.conf >>> Jun 10 09:54:32 visn1 apache[12195]: INFO: apache not running >>> Jun 10 09:54:32 visn1 apache[12195]: INFO: waiting for apache >>> /etc/apache2/apache2.conf to come up >>> >>> When I try to manually "/usr/sbin/apache2 -DSTATUS -f >>> /etc/apache2/apache2.conf" it says >>> >>> apache2: bad user name ${APACHE_RUN_USER} >>> >>> Then I exported manually all things that is in /etc/apache2/envvars, then >>> the -DSTATS command works, but apache still not starting in cluster. >>> thats why i configured envfiles (but it should be default the same > anyway?) >>> >>> Weird thing is, that it DID work before a few hours (but only one node was > >>> online), but i dont get any hint WHY it did work... >>> >>> /etc/init.d/apache2 start works and status-server IS avaiable... (tested > via >>> lynx and 127.0.0.1/server-status >>> >>> Any ideas? Please... >>> >>> regards, >>> Matthias >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
