6: Preventing mysql-server from
re-starting anywhere in the cluster
Jul 7 11:48:26 qad01 pengine: [4359]: WARN: unpack_rsc_op: Processing
failed op mysql-server_start_0 on qad01: not configured (6)
Jul 7 11:48:26 qad01 pengine: [4359]: notice: native_print:
mysql-server (ocf::heartbeat:mysq
_0 on qad01: not configured (6)
Jul 7 11:48:26 qad01 pengine: [4359]: notice: native_print:
mysql-server (ocf::heartbeat:mysql): Stopped
Jul 7 11:48:26 qad01 pengine: [4359]: info: get_failcount: mysql-server
has failed INFINITY times on qad01
Jul 7 11:48:26 qad01 pengine: [4359]: WARN:
On 07/07/2010 05:55 PM, Jake Bogie wrote:
> So I took Dan's advice this time and cleaned up my resource
> configuration, updated the script, and verified...however I'm still not
> getting the resource online...
hi,
please use hb_report to gather the logfiles.
> # cat /var/log/messages | grep mys
l): Stopped
Jul 7 11:48:26 qad01 pengine: [4359]: info: get_failcount: mysql-server
has failed INFINITY times on qad01
Jul 7 11:48:26 qad01 pengine: [4359]: WARN: common_apply_stickiness:
Forcing mysql-server away from qad01 after 100 failures
(max=100)
Jul 7 11:48:26 qad01 pengine: [4359]:
Have you copied twice this line?
socket="/var/lib/mysql/mysql.sock" binary="/usr/sbin/mysqld"
socket="/var/lib/mysql/mysql.sock" binary="/usr/sbin/mysqld"
I think so. Regardless, to test a resource agent manually requires that
you define some variables and then call the script by hand. Also, ch
Hi,
On Tue, Jul 06, 2010 at 12:42:41PM -0400, Jake Bogie wrote:
> So I took Raoul's advice and ditched the lsb:mysql check and went for
> the ocf:heartbeat version however...
>
> I'm getting this now...
>
> What am I missing? I'm having a hard time finding a document on how to
> setup this resou
So I took Raoul's advice and ditched the lsb:mysql check and went for
the ocf:heartbeat version however...
I'm getting this now...
What am I missing? I'm having a hard time finding a document on how to
setup this resource agent.
Last updated: Tue Jul 6 12:44:07 2010
Stack: openais
On 07/02/2010 11:18 PM, Jake Bogie wrote:
> Receiving this error when running crm status...the only thing I can
> think of is that since the upgrade to MySQL 5.1 the service name was
> changed from mysqld to mysql.
>
> Any thoughts on how to correct it?
what i would do:
1. crm resource stop mysq
Receiving this error when running crm status...the only thing I can
think of is that since the upgrade to MySQL 5.1 the service name was
changed from mysqld to mysql.
Any thoughts on how to correct it?
Failed actions:
mysqld_monitor_0 (node=qad01, call=4, rc=5, status=complete): not
installed
