From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Mahoney Date: Wed Mar 28 11:15:55 2007 Subject: [Ocfs2-devel] mount gnenerates an error : "Unable to access cluster service while starting heartbeat" In-Reply-To: <147a89290703281110j58cc0c79nc970def2e408473c@mail.gmail.com> References: <147a89290703280827w67339993y32557cfd8067733a@mail.gmail.com> <460A968D.4030204@oracle.com> <147a89290703281029q8818140kc7f1d872e9f3df61@mail.gmail.com> <460AA6E3.4000802@oracle.com> <147a89290703281110j58cc0c79nc970def2e408473c@mail.gmail.com> Message-ID: <460AB0D4.8060708@suse.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ocfs2-devel@oss.oracle.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andy Johnson wrote: > *Sunil Mushran, > Are you sure ? > > Before and **after** > " service hearbeat start" > I have the **same** results; heartbeat user space is not mentioned; This > is on fedora core 6. > > here is what I get: > * **cat /etc/sysconfig/o2cb > # > # This is a configuration file for automatic startup of the O2CB > # driver. It is generated by running /etc/init.d/o2cb configure. > # Please use that method to modify this file > # > > # O2CB_ENABELED: 'true' means to load the driver on boot. > O2CB_ENABLED=false > > # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. > O2CB_BOOTCLUSTER= > > # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. > O2CB_HEARTBEAT_THRESHOLD= It looks like you haven't actually configured a cluster to use. The command to configure a cluster is in the header of the file you pasted: /etc/init.d/o2cb configure - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGCrDTLPWxlyuTD7IRAmFgAKCdtiooVVAgAokfb+gh7ifpG6iaRACfXE/1 kriNZ4yJAQhRVEocI6P/kGI= =4HwK -----END PGP SIGNATURE-----