[Pacemaker] pacemaker won't start mysql in the second node
Michael Schwartzkopff
misch at clusterbau.com
Wed Feb 2 15:59:51 UTC 2011
On Wednesday 02 February 2011 16:05:30 Liang.Ma at asc-csa.gc.ca wrote:
> Hi,
>
> I did what Michael suggested (included below). When there are only
> ms_drbd_mysql and fs_mysql, no problem to fail over to node 2. Added ip1,
> it still fail over to arsvr2 fine when I put node 1 (arsvr1) standby. But
> when I added mysql in group MySQLDB, it behaved exactly the same. fs_mysql
> started and mounted on arsvr2, and even ip1 started no problem, but mysql
> failed to start. Crm_mon shows the error
>
> Failed actions: mysql_start_0 (node=arsvr2, call=32, rc=4,
> status=complete): insufficient privileges
>
> While the cluster log didn't show anything on mysql start.
- Please check the uids of the mysql user on both nodes.
- please check the rights on the mysql binaries and the database files on both
server when DRBD active.
Greetings,
--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München
Tel: (0163) 172 50 98
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110202/69edab2c/attachment-0005.sig>
More information about the Pacemaker
mailing list