[Pacemaker] pacemaker won't start mysql in the second node

[Liang.Ma at asc-csa.gc.ca]

Thanks Michael, but the uid and permissions seem the same on both nodes. 

Liang Ma
Contractuel | Consultant | SED Systems Inc. 
Ground Systems Analyst
Agence spatiale canadienne | Canadian Space Agency
6767, Route de l'Aéroport, Longueuil (St-Hubert), QC, Canada, J3Y 8Y9
Tél/Tel : (450) 926-5099 | Téléc/Fax: (450) 926-5083
Courriel/E-mail : [liang.ma at space.gc.ca]
Site web/Web site : [www.space.gc.ca ] 




-----Original Message-----
From: Michael Schwartzkopff [mailto:misch at clusterbau.com] 
Sent: February 2, 2011 11:00 AM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] pacemaker won't start mysql in the second node

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