"Command is respawning too rapidly" & "error getting database referen.."

[Marco_67]

Hello,

after applied some security baseline my system is showing the following error message:
"INIT: Command is respawning too rapidly.
Will try again in 5 minutes.
Check for possible errors.
id: EM "/opt/hpservices/contrib/vaeh/bin/startEM.sh""
Furthermore while running the command launcher I'm getting the error message: "error getting database reference
from localhost" amd the CommandView tool doesn't show the VA7410 attached to the system...

Any help will be more than welcome.
Best regards
Marco

[Peter Godron · Accepted solution]

Marco.
modify your /etc/inittab file
change spawn to off on the line mentioning EM

[Luk Vandenbussche]

check this link

http://docs.hp.com/en/5990-8547/apgs02.html?btnPrev=%AB%A0prev

[A. Clay Stephenson]

While editing /etc/inittab may be the solution, it's only part of the solution because unless you issue an "init q" command, init will not reread inittab and won't have a clue that anything has changed. Man init for details.

[Marco_67]

by setting off the mentioned line into inittab I got rid of the first error.
I'm still having problem with the launcher command: "error getting database reference
from localhost"

[Peter Godron]

Marco,
is your hostname being correctly resolved by DNS ?

[Marco_67]

yes, the host/ip is correctly resolved by DNS.

[Sandman!]

Was the CommandView tool installed properly? Check syslog.log and swagent.log files for errors related to CommandView.

[Bill Hassell]

And to amplify Clay's answer, you have disabled the script called: "/opt/hpservices/contrib/vaeh/bin/startEM.sh"

This script is not running correctly. I'm sure someone tested it as a local user and it worked OK but inittab items require a LOT more details to be handled, including proper error reporting. The respawn option in inittab will keep restarting the script as fast as it can and to protect against runaway scripts, init checks that a command does not seem to be working correctly with the above error message.

Two things:

1. The script must be designed to run in a minimum environment -- which is nothing like a login user environment. Most of the assumptions about $PATH and other variables are not valid. Your script will have to explicitly set the required paths in $PATH and any other variables that are needed. The script should normally run for a long time minutes to hours or days.

2. inittab is generally deprecated for use in starting scripts or other processes. If you want to start a process at bootup, it would normally be setup in /sbin/init.d with links to start and stop sequences plus a config script in /etc/rc.config.d.