[Linux-HA] Problem with starting Apache and MySQL

[Malte Geierhos]

Am 16.10.09 15:11, schrieb dembi:

Just test if you get valid responses by testing :

wget http://localhost/server-status

Howto configure Apache goes beyond the scope of this list.
Please try for yourself until it works. Then use the ocf-tester and see 
if it works with your environment.

> I have installed wget:
>
> sudo dpkg -l|grep wget
> ii  wget  1.11.4-2
>
> And I have Loaded Module of ‘mod_status’. I can see this using phpinfo()
> function.
>
> Please see my status.conf
>
> <Location /server-status>
>      SetHandler server-status
>      Order deny,allow
>      Deny from all
> #    Allow from localhost ip6-localhost
>      Allow from all
> </Location>
>
>
> But I still can not start Apache with OCF script
> Please see my log file:
>
> Oct 16 16:08:31 aps-1 tengine: [18324]: info: send_rsc_command: Initiating
> action 11: apache_monitor_0 on aps-3
> Oct 16 16:08:31 aps-1 pengine: [18325]: WARN: unpack_rsc_op: Processing
> failed op apache_start_0 on aps-1: Timed Out
> Oct 16 16:08:31 aps-1 pengine: [18325]: WARN: unpack_rsc_op: Compatability
> handling for failed op apache_start_0 on aps-1
> Oct 16 16:08:31 aps-1 pengine: [18325]: notice: native_print:
> apache#011(heartbeat::ocf:apache):#011Stopped
> Oct 16 16:08:31 aps-1 pengine: [18325]: notice: StartRsc:  aps-3#011Start
> apache
> Oct 16 16:08:31 aps-1 pengine: [18325]: notice: RecurringOp: aps-3#011
> apache_monitor_5000
> Oct 16 16:08:32 aps-1 tengine: [18324]: info: match_graph_event: Action
> apache_monitor_0 (11) confirmed on aps-3 (rc=0)
> Oct 16 16:08:34 aps-1 tengine: [18324]: info: send_rsc_command: Initiating
> action 93: apache_start_0 on aps-3
> Oct 16 16:08:54 aps-1 tengine: [18324]: WARN: print_elem: Action missed its
> timeout[Action 93]: In-flight (id: apache_start_0, loc: aps-3, priority: 0)
> Oct 16 16:08:55 aps-1 tengine: [18324]: WARN: update_failcount: Updating
> failcount for apache on d305cc9a-6c27-4de0-ab2d-775419549bde after failed
> start: rc=-2
> Oct 16 16:08:55 aps-1 tengine: [18324]: info: match_graph_event: Action
> apache_start_0 (93) confirmed on aps-3 (rc=4)
> Oct 16 16:08:55 aps-1 pengine: [18325]: WARN: unpack_rsc_op: Processing
> failed op apache_start_0 on aps-3: Timed Out
> Oct 16 16:08:55 aps-1 pengine: [18325]: WARN: unpack_rsc_op: Compatability
> handling for failed op apache_start_0 on aps-3
> Oct 16 16:08:55 aps-1 pengine: [18325]: WARN: unpack_rsc_op: Processing
> failed op apache_start_0 on aps-1: Timed Out
> Oct 16 16:08:55 aps-1 pengine: [18325]: WARN: unpack_rsc_op: Compatability
> handling for failed op apache_start_0 on aps-1
> Oct 16 16:08:55 aps-1 pengine: [18325]: notice: native_print:
> apache#011(heartbeat::ocf:apache):#011Started aps-3 FAILED
> Oct 16 16:08:55 aps-1 pengine: [18325]: WARN: native_color: Resource apache
> cannot run anywhere
> Oct 16 16:08:55 aps-1 pengine: [18325]: notice: StopRsc:   aps-3#011Stop
> apache
> Oct 16 16:08:55 aps-1 tengine: [18324]: info: send_rsc_command: Initiating
> action 5: apache_stop_0 on aps-3
> Oct 16 16:08:56 aps-1 tengine: [18324]: info: match_graph_event: Action
> apache_stop_0 (5) confirmed on aps-3 (rc=0)
>
>
>
> Malte Geierhos-2 wrote:
>    
>> Hi
>>      
>>> Ok, If I have stopped heartbeat resource on my aps-3 which was as DC.
>>> All resources were successfully migrated on aps-1.
>>> Can I think that all work ok.
>>> Or may be I should perform additional testing?
>>>
>>> And can you please explain to me why it was not working with ‘ocf’
>>> resource?
>>>
>>> Thanks in advance.
>>>
>>>