Mailing List Archive

"init: Id crm: respawning too fast: disabled for 5 minutes"
“init: Id crm : respawning too fast: disabled for 5 minutes”

Following entry has been made in /etc/inittab for snmp:
crm:2345:respawn:/usr/sbin/crm_mon --daemonize -S 192.168.127.1

Query: Why and when is this log observed ?


_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: "init: Id crm: respawning too fast: disabled for 5 minutes" [ In reply to ]
On Thu, Apr 19, 2012 at 9:47 PM, Parshvi <parshvi.17@gmail.com> wrote:
> “init: Id  crm : respawning too fast: disabled for 5 minutes”
>
> Following entry has been made in /etc/inittab for snmp:
> crm:2345:respawn:/usr/sbin/crm_mon --daemonize -S 192.168.127.1
>
> Query: Why and when is this log observed ?
>

Based on the info provided... no idea at all.
Have you checked the system logs? What happens if you start it by hand?

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: "init: Id crm: respawning too fast: disabled for 5 minutes" [ In reply to ]
On Thu, Apr 19, 2012 at 9:47 PM, Parshvi <parshvi.17@gmail.com> wrote:
> “init: Id  crm : respawning too fast: disabled for 5 minutes”
>
> Following entry has been made in /etc/inittab for snmp:
> crm:2345:respawn:/usr/sbin/crm_mon --daemonize -S 192.168.127.1
>
> Query: Why and when is this log observed ?
>

Based on the info provided... no idea at all.
Have you checked the system logs? What happens if you start it by hand?

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: "init: Id crm: respawning too fast: disabled for 5 minutes" [ In reply to ]
Andrew Beekhof <andrew@...> writes:


> On Thu, Apr 19, 2012 at 9:47 PM, Parshvi <parshvi.17@...> wrote:
> > “init: Id  crm : respawning too fast: disabled for 5 minutes”
> >
> > Following entry has been made in /etc/inittab for snmp:
> > crm:2345:respawn:/usr/sbin/crm_mon --daemonize -S 192.168.127.1
> >
> > Query: Why and when is this log observed ?
>
> Based on the info provided... no idea at all.
> Have you checked the system logs? What happens if you start it by hand?
>

Hi Andrew,

1) I have checked the system logs, didn't find anything useful in this regard.
Looks like the logs are high when the system goes for a reboot.
2) It starts if one starts it by hand. Although it is not required to manually
start it since it is found up and running, despite the following logs appearing.

A snapshot of the logs pasted below:

May 11 11:34:51 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes
May 11 11:39:52 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes
May 11 11:44:53 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes
May 11 11:49:54 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes
May 11 11:54:55 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes
May 11 11:59:56 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes
May 11 12:00:02 ct-node-ft-112 shutdown[6676]: shutting down for system reboot
May 11 12:00:04 ct-node-ft-112 smartd[3508]: smartd received signal 15:
Terminated
May 11 12:00:04 ct-node-ft-112 smartd[3508]: smartd is exiting (exit status 0)
May 11 12:04:43 ct-node-ft-112 smartd[3518]: smartd has fork()ed into background
mode. New PID=3518.
May 11 12:04:44 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes
May 11 12:04:44 ct-node-ft-112 pcscd: winscard.c:304:SCardConnect() Reader E-
Gate 0 0 Not Found
May 11 12:04:44 ct-node-ft-112 last message repeated 3 times
May 11 12:09:45 ct-node-ft-112 init: Id "crm" respawning too fast: disabled for
5 minutes

Output of ps -ef :
3782 1 0 12:04 ? 00:00:00 /usr/sbin/crm_mon --daemonize -S 92.168.127.1


_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: "init: Id crm: respawning too fast: disabled for 5 minutes" [ In reply to ]
19.04.2012 14:47, Parshvi wrote:
> “init: Id crm : respawning too fast: disabled for 5 minutes”
>
> Following entry has been made in /etc/inittab for snmp:
> crm:2345:respawn:/usr/sbin/crm_mon --daemonize -S 192.168.127.1

From what I remember about sysvinit, services you start with respawn
flag should not detach from the controlling terminal (daemonize, go to
background). init makes all that by itself and then watches for process
to finish. Upon that it restarts the process.

So, just delete '--daemonize' and it should run fine.

Best,
Vladislav

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org