Re: Unique attribute collision for mmount Point

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Thu, May 14, 2009 at 2:22 PM, anasnajj <anasnajj@xxxxxxxxx> wrote:

Dear all

I know I asked this question before but I not get any response so I will try to re-explain it

 

I want to run 10 services on 10 nodes and each service run script that store its data by default  on /image and used mysql script which store in /var/lib/mysql

in each service there is the following resources with following order:
-IP
-LVM for my Script DATA
-LVM for mysql DATA
-File system to mount my Script DATA /images
-File system to mount /var/lib/mysql
-Script mysql
-Script : MyScript File

 

 

when I run the service its give me the following error and ignore mount point resources:

 

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <notice> Resource Group Manager Starting

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <info> Loading Service Data

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <err> Unique attribute collision. type=fs attr=mountpoint value=/Images

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <err> Error storing fs resource

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <err> Unique attribute collision. type=fs attr=mountpoint value=/var/lib/mysql

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <err> Error storing fs resource

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <err> Unique attribute collision. type=fs attr=mountpoint value=/Images

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <err> Error storing fs resource

May 13 13:56:32 MENCS01 clurgmgrd[21863]: <err> Unique attribute collision. type=fs attr=mountpoint value=/var/lib/mysql

 

 if i used different names i cant told my service to store its data on anoter location .??? because my script by default store in /Images   and cannot changed.

I think you should have a mountpoint for each resource (script, mysql) on each service.
You should change that script to use a custom directory name. If you are running a database instance for each service, you should have a separate my.cnf file for each service and also a separate "datadir" filesystem. Cluster is able to manage mysql as a resource on its own without using any external script.
I.e:
<mysql config_file="/datadir/my.cnf" listen_address="x.x.x.x" name="mydatabase1" />

Hope that helps,
Juanra

 


by the way all my nodes use the same script file located on /etc/init.d/
so i cant make service #1 store in /images1 and service#2 store on /images2 and so on..

 

 

Best Regards


--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux