Hi Anyone who can help to get this working? Or where I can look?
Many thanks On 07/13/2014 04:28 PM, W Forum W wrote: > Hi, > > The apache logs doesn't say a lot (LogLevel debug) > > [error] python_init: Python version mismatch, expected '2.7.2+', found > '2.7.3'. > [error] python_init: Python executable found '/usr/bin/python'. > [error] python_init: Python path being used > '/usr/lib/python2.7/:/usr/lib/python2.7/plat-linux2:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'. > [notice] mod_python: Creating 8 session mutexes based on 150 max > processes and 0 max threads. > [notice] mod_python: using mutex_directory /tmp > [notice] Apache/2.2.22 (Debian) PHP/5.4.4-14+deb7u12 mod_python/3.3.1 > Python/2.7.3 mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming > normal operations > [notice] caught SIGTERM, shutting down > > The configuration should be ok, or do I miss something > > primitive p_ps_apache lsb:apache2 \ > op monitor interval="60" timeout="30" \ > op start interval="0" timeout="30" \ > op start interval="0" timeout="30" > > Many thanks > hi, we are using debian and selinux is default disabled in debian. we > don't use it either is there no way to find what causes apache not to > start? many thanks!!!! On 07/11/2014 01:36 AM, Andrew Beekhof wrote: >>>> On 10 Jul 2014, at 7:58 pm, W Forum W <wfor...@gmail.com> wrote: >>>> >>>>> Hi thanks for the help. >>>>> the status url is configured and working, also no error in apache >>> log when I start the service manually >>>>> any other ideas where to look?? >>>> selinux. if it starts from the command line but not in the cluster >>> its very often selinux >>>>> many thanks!! >>>>> >>>>> >>>>> On 07/09/2014 12:53 AM, Andrew Beekhof wrote: >>>>>> On 8 Jul 2014, at 11:15 pm, W Forum W <wfor...@gmail.com> >>>>>> wrote: >>>>>> >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I have a two node cluster with a DRBD, heartbeat and pacemaker (on >>> Debian Wheezy) >>>>>>> The cluster is working fine. 2 DRBD resources, Shared IP, 2 File >>> systems and a postgresql database start, stop, migrate, ... correctly. >>>>>>> Now the problem is with the lsb:apache2 resource agent. >>>>>>> When I try to start is (crm resource start p_ps_apache) >>> immediately I got an error like >>>>>>> p_ps_apache_monitor_60000 (node=wegc203136, call=653, rc=7, >>> status=complete): not running >>>>>>> When I start Apache from the console (service apache2 start), it >>> works fine >>>>>>> I have checked if the Init Script LSB is compatible (see >>>>>>> http://www.linux-ha.org/wiki/LSB_Resource_Agents >>>>>>> ). >>>>>>> All sequences tested are ok >>>>>>> >>>>>>> How can I found out why crm is not starting Apache? >>>>>>> >>>>>> most likely the status url is not setup/configured. >>>>>> have you checked the apache logs? >>>>>> >>>>>> >>> On 07/11/2014 05:41 PM, Michael Monette wrote: >>> Is there a certificate passphrase when starting apache from command line? >>> >>> On July 11, 2014 11:38:11 AM EDT, W Forum W <wfor...@gmail.com> wrote: >>> >>> hi, >>> >>> we are using debian and selinux is default disabled in debian. >>> we don't use it either >>> >>> is there no way to find what causes apache not to start? >>> >>> many thanks!!!! >>> >>> On 07/11/2014 01:36 AM, Andrew Beekhof wrote: >>>> On 10 Jul 2014, at 7:58 pm, W Forum W <wfor...@gmail.com> wrote: >>>> >>>>> Hi thanks for the help. >>>>> the status url is configured and working, also no error in apache log >>>>> when I start the service manually >>>>> >>>>> any other ideas where to look?? >>>> selinux. if it starts from the command line but not in the cluster its >>>> very often selinux >>>> >>>>> many thanks!! >>>>> >>>>> >>>>> On 07/09/2014 12:53 AM, Andrew Beekhof wrote: >>>>>> On 8 Jul 2014, at 11:15 pm, W Forum W <wfor...@gmail.com> >>>>>> wrote: >>>>>> >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I have a two node cluster with a DRBD, heartbeat and pacemaker (on >>>>>>> Debian Wheezy) >>>>>>> The cluster is working fine. 2 DRBD resources, Shared IP, 2 File >>>>>>> systems and a postgresql database start, stop, migrate, ... correctly. >>>>>>> >>>>>>> Now the problem is with the lsb:apache2 resource agent. >>>>>>> When I try to start is (crm resource start p_ps_apache) immediately >>>>>>> I got an error like >>>>>>> >>>>>>> p_ps_apache_monitor_60000 (node=wegc203136, call=653, rc=7, >>>>>>> status=complete): not running >>>>>>> >>>>>>> When I start Apache from the console (service apache2 start), it >>>>>>> works fine >>>>>>> >>>>>>> I have checked if the Init Script LSB is compatible (see >>>>>>> http://www.linux-ha.org/wiki/LSB_Resource_Agents >>>>>>> ). >>>>>>> All sequences tested are ok >>>>>>> >>>>>>> How can I found out why crm is not starting Apache? >>>>>>> >>>>>> most likely the status url is not setup/configured. >>>>>> have you checked the apache logs? >>>>>> >>>>>> >>> 08.07.2014 16:15, W Forum W wrote: >>> Hi, >>> >>> I have a two node cluster with a DRBD, heartbeat and pacemaker (on >>> Debian Wheezy) >>> The cluster is working fine. 2 DRBD resources, Shared IP, 2 File systems >>> and a postgresql database start, stop, migrate, ... correctly. >>> >>> Now the problem is with the lsb:apache2 resource agent. >>> When I try to start is (crm resource start p_ps_apache) immediately I >>> got an error like >>> >>> /p_ps_apache_monitor_60000 (node=wegc203136, call=653, rc=7, >>> status=complete): not running/ >>> >>> When I start Apache from the console (service apache2 start), it works fine >>> >>> I have checked if the Init Script LSB is compatible (see >>> http://www.linux-ha.org/wiki/LSB_Resource_Agents). >>> All sequences tested are ok >>> >>> How can I found out why crm is not starting Apache? >> Is it really not started, or just is not configured enough to be >> successfully monitored and then monitor op fails? >> What your apache logs say? >> >> >
_______________________________________________ Pacemaker mailing list: Pacemaker@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
