On Tue, Jan 18, 2011 at 04:55:38PM +0530, akshay punja wrote:
> Hi,
>
> Thanks for the help,
>
> As suggest I have changed the crm on to respawn, after the configuration
> change Rebooting has stopped.
>
> I are using tomcat, apache httpd and mysql master - slave replication, I
> have set this
Hi,
Thanks for the help,
As suggest I have changed the crm on to respawn, after the configuration
change Rebooting has stopped.
I are using tomcat, apache httpd and mysql master - slave replication, I
have set this up in multiple environments and its working fine. I are see
this issue only in o
Hi,
On Tue, Jan 18, 2011 at 08:34:57AM +0530, akshay punja wrote:
> Please let me know if any one has solved this issue. CCM exiting with return
> code 100 and system rebooting
Either bad installation or some kind of security mechanism
preventing heartbeat/ccm from operating normally.
For insta
On Tue, Jan 18, 2011 at 4:04 AM, akshay punja wrote:
> Please let me know if any one has solved this issue.
Can you try "crm respawn" instead of "crm on" so the node stays up
long enough to see why the ccm is unhappy.
Lars, you really aught to think about changing the default behavior
and adding
Please let me know if any one has solved this issue. CCM exiting with return
code 100 and system rebooting
On Mon, Jan 17, 2011 at 1:29 PM, akshay punja wrote:
> Hi All,
>
> We am using pacemaker(pacemaker-1.0.9.1-1.15.el5.i386.rpm) with
> heartbeat(heartbeat-3.0.3-2.3.el5.i386.rpm) for a product
