Before you can configure cluster, o2cb service must be up.  You can use this 
command to check its status:

$ /etc/init.d/o2cb status

It is recommended to configure o2cb to auto start when the server boots. Use 
this command to configure the auto start:

# /etc/init.d/oc2b configure

Hope this helps,
George


-----Original Message-----
From: Sunil Mushran [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 27, 2006 7:43 PM
To: [EMAIL PROTECTED]
Cc: ocfs2-users@oss.oracle.com
Subject: Re: [Ocfs2-users] OCFS2: Could not start cluster stack

Check the support guide on cluster start/stop in the doc section on 
http://oss.oracle.com/projects/ocfs2.

Vicki Luo wrote:
> I installed OCFS2 on RHEL4 with  ocfs2-2.6.9-22.ELsmp-1.2.2-1.i686.rpm. When 
> I start ocfs2console and click on Cluster, and then Configure Nodes, it 
> returns a dialog with the following message "Could not start cluster stack. 
> This must be resolved before any OCFS2 filesystem can be mounted "
> Here is some information about my system:
> 1. Uname -a
> Linux SDCHS40I030 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:32:14 EDT 2005 i686 
> i686 i386 GNU/Linux
>  2. rpm -qa|grep ocfs2
> ocfs2-tools-1.2.1-1
> ocfs2console-1.2.1-1
> ocfs2-2.6.9-22.ELsmp-1.2.2-1
>
> 3. rpm -qa | grep kernel
> kernel-smp-2.6.9-5.EL
> kernel-utils-2.4-13.1.48
> kernel-2.6.9-5.EL
> kernel-smp-2.6.9-22.EL
>
> I saw a few solution posted, for example: depmod -a , then try again. Or 
> "SELINUX=disabled"
> I did both of them , but I still got the error message.
> Can anybody help me? What else could be wrong?
>
> Thanks,
> Vicki
>
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users@oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users
>   

_______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users


_______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users

Reply via email to