nimbus init.d script missing after install

[Anon Anon]

Does anyone know why, after installing Nimsoft server 6.1, there is no init.d script for nimbus? It's puzzling to me and I've read the PDF documentation which says there should be an init.d script. 

 

I'm on Centos6. Everything seems to be working and of course nimbus exists in /opt/nimsoft/bin/ but I'm not sure if this is normal or something went wrong in the install that will cause issues later.

 

Thank you in advanced for your help.

 

-CARI

[Anon Anon]

I think some of the newer installers are creating the config files to be started by Upstart rather than System V init. If I remember correctly, you might find a startup file in /etc/init/.

[Anon Anon]

I looked in the init directory and found nimbus.conf.

 

#cat /etc/init/nimbus.conf
description "NMS server"
author "Nimsoft LLC"

start on runlevel [2345]
stop on runlevel [!2345]

# if our main process fails, restart it
respawn

# we are likely to fork so let's ensure that we keep
# track of the correct pid
expect fork

# pre-start operations

pre-start script
    echo "[`date -u +%Y-%m-%dT%T.%3NZ`] (sys) Starting" >> /var/log/nimbus.sys.log
end script


# main operation

script
    exec /opt/nimsoft/bin/nimbus /opt/nimsoft >>  /var/log/nimbus.sys.log
end script


# pre-stop operations

pre-stop script
    rm -f /opt/nimsoft/robot/pids/nimbus.pid
    echo "[`date -u +%Y-%m-%dT%T.%3NZ`] (sys) Stopping" >> /var/log/nmibus.sys.log
end script

 

This looks incomplete. Was the init script renamed perhaps?

[Anon Anon]

Why do you think it is incomplete? I do not know much about Upstart, but it does not look like there are any unclosed blocks of config/code there.

 

You would not have both an init script and an Upstart config. So if you have nimbus.conf, you should not have an init script. That would result in the robot being started twice.

[Anon Anon]

Ok perhaps I am misunderstanding how this is supposed to work. I've scoured the documentation, to start and stop the service it says to use the inti.d script.  Aside form killing all the PID and then using the /opt/nimsoft/bin/nimbus command how am I supposed to use this nuimbus.conf to stop start and restart the service? I'm not familiar with running init/ scripts and when I try to run the .conf file in there this is the output:

 

# /etc/init/nimbus.conf
/etc/init/nimbus.conf: line 1: description: command not found
/etc/init/nimbus.conf: line 2: author: command not found
start: Unknown job: on
stop: Unknown job: on
/etc/init/nimbus.conf: line 8: respawn: command not found
/etc/init/nimbus.conf: line 12: expect: command not found
/etc/init/nimbus.conf: line 16: pre-start: command not found
/etc/init/nimbus.conf: line 18: end: command not found

[Anon Anon]

Maybe I'm misunderstanding the issues at hand, but you should be able to just run "service nimbus *" to manipulate the services. You have to have permissions to run the commands (typically root). The * above refers to the start, stop and restart commands, so valid commands are as follows:

 

service nimbus start

service nimbus stop

service nimbus restart

 

Also, there are some issues with the script not being the correct run level with some Linux distros I believe. If you find that upon restarting a server that the nimbus process doesn't automatically start, you will need to modify the script. Contact me at [e-mail] if you need help.

[Anon Anon]

The problem is that it's not recognizing the service as follows:

 

# service nimbus stop
nimbus: unrecognized service

# service nimbus start
nimbus: unrecognized service
# service nimbus restart
nimbus: unrecognized service

I'm not sure if I screwed something up in the installation or maybe the pre-installation.  I did a reboot and the services came back up automatically but I'm trying to perform some tests on the HA probe and want to bring the nimbus service down without turning off the server.

[Anon Anon]

oh and I'm running on centos 6.3 by the way

[Anon Anon]

If you look at your run level scripts what is the nimbus script pointing to obviously something if it comes up during boot.  Should be like a S95nimbus link in the rc3.d and or rc5.d directory.

[Anon Anon]

I think the service command only works with System V init scripts. WIth Upstart, you should be using the initctl command.

 

Examples:

 

initctl start nimbus

initctl stop nimbus

 

[Anon Anon]

Thank you, that was it, I guess I never had a need to use initctl.