[ClusterLabs] Trouble setting up selfcompiled Apache in a pacemaker cluster on Oracle Linux 6.8

[Souvignier, Daniel]

Hi,

 

two weeks ago I had a question regarding the activation of apache (see
below). Since then I wasn't able to resolve this. Any ideas? Thanks!

 

Regards,

Daniel 

 

--

Daniel Souvignier

 

IT Center

Gruppe: Linux-basierte Anwendungen

Abteilung: Systeme und Betrieb

RWTH Aachen University

Seffenter Weg 23

52074 Aachen

Tel.: +49 241 80-29267

souvignier at itc.rwth-aachen.de <mailto:souvignier at itc.rwth-aachen.de> 

www.itc.rwth-aachen.de <http://www.itc.rwth-aachen.de/> 

 

Von: Souvignier, Daniel [mailto:Souvignier at itc.rwth-aachen.de] 
Gesendet: Montag, 16. Januar 2017 17:16
An: users at clusterlabs.org
Betreff: [ClusterLabs] Trouble setting up selfcompiled Apache in a pacemaker
cluster on Oracle Linux 6.8

 

Hi List,

 

I've got trouble getting Apache to work in a Pacemaker cluster I set up
between two Oracle Linux 6.8 hosts. The cluster itself works just fine, but
Apache won't come up. Thing is here, this Apache is different from a basic
setup because it is selfcompiled and therefore living in /usr/local/apache2.
Also it is the latest version available (2.4.25), which could also be
causing problems. To be able to debug, I went into the file
/usr/lib/ocf/resources.d/heartbeat/apache and "verbosed" it by simply adding
set -x. This way, I can extract the scripts output from the logfile
/var/log/cluster/corosync.log, which I appended to this email (hopefully it
won't get filtered). 

 

The command I used to invoke the apache script mentioned above was:

pcs resource create httpd ocf:heartbeat:apache
configfile=/usr/local/apache2/conf/httpd.conf
httpd=/usr/local/apache2/bin/httpd statusurl=http://localhost/server-status
envfiles=/usr/local/apache2/bin/envvars op monitor interval=60s

 

Before you ask: the paths are correct and mod_status is also configured
correctly (works fine when starting Apache manually). I should also add that
the two nodes which form this cluster are virtual (Vmware vSphere) hosts and
living in the same network (so no firewalling between them, there is a
dedicated firewall just before the network). I assume that it has something
to do with the handling of the pid file, but I couldn't seem to fix it until
now. I pointed Apache to create the pid file in /var/run/httpd.pid, but that
didn't work either. Suggestions on how to solv this? Thanks in advance!

 

Kind regards,

Daniel Souvignier

 

P.S.: If you need the parameters I compiled Apache with, I can tell you, but
I don't think that it is relevant here.

 

--

Daniel Souvignier

 

IT Center

Gruppe: Linux-basierte Anwendungen

Abteilung: Systeme und Betrieb

RWTH Aachen University

Seffenter Weg 23

52074 Aachen

Tel.: +49 241 80-29267

souvignier at itc.rwth-aachen.de <mailto:souvignier at itc.rwth-aachen.de> 

www.itc.rwth-aachen.de <http://www.itc.rwth-aachen.de/> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170131/b6a890fa/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5780 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170131/b6a890fa/attachment-0003.p7s>