[ClusterLabs] Antw: Re: Antw: Re: ocf:heartbeat:apache does not start

Stefan Schloesser sschloesser at enomic.com
Wed Jan 11 08:39:04 EST 2017 

Hi,

the /var/run dir resides on /run (tempfs) it is deleted upon reboot on my machine. I guess the problems arise from the switch to another service infrastructure. The ra does not take these changes into account - it starts the binary directly rather than through the service infrastructure. This probably entails a complete rewrite ...
So it seems best to create those dirs.
The loop to check for the pid sounds like a good idea - but I agree, shame that the pid is not there. Would have saved a lot of trouble...

Stefan

-----Original Message-----
From: Ulrich Windl [mailto:Ulrich.Windl at rz.uni-regensburg.de] 
Sent: Wednesday,11 January, 2017 13:52
To: users at clusterlabs.org
Subject: [ClusterLabs] Antw: Re: Antw: Re: ocf:heartbeat:apache does not start

Hi!

Personally I think a RA should not create directories it expects to be present. In this case the apache installation should have created these directories. While a "sleep 3" seems safe, you always loose 3 seconds. It might be advisable to use a loop checking for the pid file instead.
(It would be even better if the starting application creates the pid file before returning).

Ulrich

>>> Stefan Schloesser <sschloesser at enomic.com> schrieb am 11.01.2017 um 
>>> 11:25
in
Nachricht
<A5F1A1F559D1BC47BF24BD2D3ED720D3E8CF3A36 at im-server03.intermediate.de>:
> Hi,
> 
> finally got it working - several problems were fixed:
> - directories not available -> create them
> - lock wrong permissions -> chown
> - pid file not available on startup (too fast) -> sleep 3
> 
> For reference here is a diff:
> --- apache.orginal      2016-11-18 10:11:30.453946643 +0100
> +++ apache      2017-01-11 11:15:16.533845697 +0100
> @@ -191,6 +191,9 @@
>                 ocf_run $HTTPD $HTTPDOPTS $OPTIONS -f $CONFIGFILE -c 
> "PidFile $PidFile"
>         fi
> 
> +       #wait for pid to be available
> +        sleep 3
> +
>         tries=0
>         while : # wait until the user set timeout
>         do
> @@ -593,6 +596,14 @@
>                 ocf_exit_reason "Configuration file $CONFIGFILE not found!"
>                 return $OCF_ERR_INSTALLED
>         fi
> +
> +        # https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/603211 
> +        [ -d /var/run/apache2 ] || mkdir /var/run/apache2
> +        [ -d /var/lock/apache2] || mkdir /var/lock/apache2
> +        chown www-data /var/lock/apache2
> +
>         ocf_mkstatedir root 755 `dirname $PidFile` || return 
> $OCF_ERR_INSTALLED
>         return $OCF_SUCCESS
>  }
> 
> Seems to be stable now.
> 
> Stefan
> 
> -----Original Message-----
> From: Ulrich Windl [mailto:Ulrich.Windl at rz.uni-regensburg.de]
> Sent: Friday,18 November, 2016 13:49
> To: users at clusterlabs.org
> Subject: [ClusterLabs] Antw: Re: ocf:heartbeat:apache does not start
> 
> Hi!
> 
> As an exercise you could try to write your own apache RA. That 
> shouldn't bee

> to difficult. Alternatively you could try to hack the RA until it works.
Then 
> report your insights.
> Maybe you want to stop your apache and try "ocf-tester (if available) 
> to test the RA (also good when hacking it).
> 
> Ulrich
> 
>>>> Stefan Schloesser <sschloesser at enomic.com> schrieb am 18.11.2016 um
>>>> 12:02
> in
> Nachricht
> <A5F1A1F559D1BC47BF24BD2D3ED720D3DB87DAFE at im-server03.intermediate.de>:
>> Hi,
>> 
>> any progress on this issue ?
>> 
>> I seem to have the same problem the ra does not start due to a 
>> missing
>> /var/run/apache2 dir.
>> I found an old bug and a matching fix
>> https://bugs.launchpad.net/ubuntu/+source/cluster-agents/+bug/980180
>> 
>> Which changed a line on startup. Copying this to validate_all solves 
>> the problem of the missing dir, but now It's /var/lock/apache2 which 
>> is missing and after that it can't find its conf file 
>> /etc/apache2/apache2.conf which plainly is there.
>> 
>> Has anyone got this ra working on Ubuntu 16.04 ? I've got it running 
>> on
>> 12.04 and 14.04 ...
>> 
>> I'd appreciate a pointer - can't believe this is completely broken 
>> under Ubuntu 16.
>> 
>> Stefan
>> 
>> -----Original Message-----
>> From: Heiko Reimer [mailto:heiko.reimer at sport-tiedje.de]
>> Sent: Wednesday,13 July, 2016 16:30
>> To: Cluster Labs - All topics related to open-source clustering 
>> welcomed <users at clusterlabs.org>
>> Subject: Re: [ClusterLabs] ocf:heartbeat:apache does not start
>> 
>> 
>> Am 13.07.2016 um 13:17 schrieb Heiko Reimer:
>>>
>>> Am 13.07.2016 um 11:09 schrieb Klaus Wenninger:
>>>> On 07/13/2016 09:24 AM, Heiko Reimer wrote:
>>>>> Am 13.07.2016 um 09:09 schrieb Li Junliang:
>>>>>> 在 2016-07-13三的 08:59 +0200，Heiko Reimer写道：
>>>>>>> Hi,
>>>>>>>
>>>>>>> i try to setup pacemaker apache resource with ocf:heartbeat:apache.
>>>>>>> But
>>>>>>> when pacemaker try to start the resource i get
>>>>>>>
>>>>>>> Failed Actions:
>>>>>>> * apache2_start_0 on node1 'not installed' (5): call=186, 
>>>>>>> status=complete, exitreason='environment is invalid, resource 
>>>>>>> considered stopped',
>>>>>>>
>>>>>>> Here my config:
>>>>>>>
>>>>>>> primitive apache2 apache \
>>>>>>>            params configfile="/etc/apache2/apache2.conf" \
>>>>>>>            params httpd="/usr/sbin/apache2" \
>>>>>>>            params testurl="http://localhost" \
>>>>>>>            op monitor interval=10s timeout=20s \
>>>>>>>            op start timeout=40s interval=0 \
>>>>>>>            op stop timeout=60s interval=0 \
>>>>>>>            meta target-role=Started
>>>>>>>
>>>>>>> I am using Debian 8.5 with Apache 2.4.10 and Pacemaker 1.1.14.
>>>>>> Maybe you should check your apache installation on node1. 
>>>>>> Sometime I come across these problems , finally I find that 
>>>>>> apache2 is not in /usr/sbin or apache2.conf is in another 
>>>>>> directory rather than /etc/apache2.
>>>>> I have checked the path of both. They are ok. With systemd:apache2 
>>>>> everthing works.
>>>>> Yesterday i had the problem that problem occurred on both nodes (i 
>>>>> have two node setup).
>>>> If you check apache_monitor in the RA (of course I don't know your 
>>>> version of it) you can see that it creates the $OCF_ERR_INSTALLED 
>>>> as well if it doesn't find the http-client used to get the 
>>>> test-url. In the RA-version I have installed the exitreason would 
>>>> give more info about that fact like "... could not find http client 
>>>> ..." but that might be different with different versions.
>>> It looks like the ra does not create the apache2 directory in 
>>> /var/run
>> Which user creates apache2 folder in /var/run? Does pacemaker uses a 
>> specific user? I think it is root?
>>>>
>>>>>>> Mit freundlichen Grüßen / Best regards
>>>>>>>     Heiko Reimer
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Users mailing list: Users at clusterlabs.org 
>>>>>> http://clusterlabs.org/mailman/listinfo/users
>>>>>>
>>>>>> Project Home: http://www.clusterlabs.org Getting started:
>>>>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>>>>> Bugs: http://bugs.clusterlabs.org
>>>>> _____________________________________________________________
>>>>> Diese Nachricht erhalten Sie im Namen der Sport-Tiedje Gruppe 
>>>>> Sport-Tiedje Head Office:
>>>>> Sport-Tiedje GmbH
>>>>> International Headquarters
>>>>> Flensburger Str. 55
>>>>> D-24837 Schleswig
>>>>>
>>>>> Geschaeftsfuehrer / managing directors: Christian Grau, Sebastian 
>>>>> Campmann, Dr. Bernhard Schenkel Amtsgericht / local court Flensburg:
>>>>> HRB 1000 SL
>>>>> Steuer-Nr.: 1529319096
>>>>> UST-ID: DE813211547
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list: Users at clusterlabs.org 
>>>>> http://clusterlabs.org/mailman/listinfo/users
>>>>>
>>>>> Project Home: http://www.clusterlabs.org Getting started:
>>>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>>>> Bugs: http://bugs.clusterlabs.org
>>>>
>>>> _______________________________________________
>>>> Users mailing list: Users at clusterlabs.org 
>>>> http://clusterlabs.org/mailman/listinfo/users
>>>>
>>>> Project Home: http://www.clusterlabs.org Getting started: 
>>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>>> Bugs: http://bugs.clusterlabs.org
>>>
>>> _____________________________________________________________
>>> Diese Nachricht erhalten Sie im Namen der Sport-Tiedje Gruppe 
>>> Sport-Tiedje Head Office:
>>> Sport-Tiedje GmbH
>>> International Headquarters
>>> Flensburger Str. 55
>>> D-24837 Schleswig
>>>
>>> Geschaeftsfuehrer / managing directors: Christian Grau, Sebastian 
>>> Campmann, Dr. Bernhard Schenkel Amtsgericht / local court Flensburg:
>>> HRB 1000 SL
>>> Steuer-Nr.: 1529319096
>>> UST-ID: DE813211547
>>>
>>>
>>> _______________________________________________
>>> Users mailing list: Users at clusterlabs.org 
>>> http://clusterlabs.org/mailman/listinfo/users
>>>
>>> Project Home: http://www.clusterlabs.org Getting started: 
>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
>> 
>> _____________________________________________________________
>> Diese Nachricht erhalten Sie im Namen der Sport-Tiedje Gruppe 
>> Sport-Tiedje Head Office:
>> Sport-Tiedje GmbH
>> International Headquarters
>> Flensburger Str. 55
>> D-24837 Schleswig
>> 
>> Geschaeftsfuehrer / managing directors: Christian Grau, Sebastian 
>> Campmann,
> 
>> Dr. Bernhard Schenkel Amtsgericht / local court Flensburg: HRB 1000 
>> SL
>> Steuer-Nr.: 1529319096
>> UST-ID: DE813211547
>> 
>> 
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org 
>> http://clusterlabs.org/mailman/listinfo/users
>> 
>> Project Home: http://www.clusterlabs.org Getting started: 
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org 
>> http://clusterlabs.org/mailman/listinfo/users
>> 
>> Project Home: http://www.clusterlabs.org Getting started: 
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
> 
> 
> 
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org 
> http://clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org Getting started: 
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> _______________________________________________
> Users mailing list: Users at clusterlabs.org 
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org Getting started: 
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org




_______________________________________________
Users mailing list: Users at clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

More information about the Users mailing list