Question on RC script - for dynaTrace server
If the command in our environment to start the dynaTrace server is ‘nohup ./dtserver &’, what parameters should be specified for the RC scripts to function properly?
I am aware I need to change the DT_HOME path to our specific directory but what needs to be added for the ‘nohup’ and ‘&’?
# To use this file in your environment, adjusting the following variables:
# - DT_HOME installation directory of dynaTrace software
# - DT_OPTARGS optional arguments (e.g. -vm, -instance, -server, etc.)
# - DT_INSTANCE instance name if -instance argument is specified
DT_HOME=/home/dmaaxa0/dynatrace-5.5.0
DT_OPTARGS=
# When using an instance name, ensure that the -instance argument from
# DT_OPTARGS is in sync with the following DT_INSTANCE variable:
# (e.g.: "-instance InstName" requires "DT_INSTANCE=InstName")
DT_INSTANCE=
DT_PRODUCT=Server
DT_BINARY=dtserver
Why is the standard startup call that is done in the RC script now working for you?
It uses $DT_HOME/$DT_BINARY -bg $DT_OPTARGS
When we have a maintenance window and server is taken down, dynaTrace server (or collector) does not restart automatially. It is necessary for me to login and manually restart processes. Earlier this morning I modified the DT_HOME to the correct path. So based on what you are saying above with format of $DT_HOME/$DT_BINARY -bg $DT_OPTARGS, if I was trying to execute command: nohup ./dtserver &
DT_HOME is now correct
DT_BINARY was already correct
'DT_OPTARGS=' is empty. Is there where i would enter the & command or do I need to worry about the process stopping (logout) arguments if passed in a RC script? That's why I have the "nohup ./dtserver &" and wondered how to pass these arguments.
$DT_OPTARGS is meant to pass arguments to the dynatrace server/collector and not to define how these binaries are beeing launched.
In your case you can modify the script and launch the dynaTrace server differently e.g. from
$DT_HOME/$DT_BINARY - bg $DT_OPTARGS
to
nohup $DT_HOME/$DT_BINARY $DT_OPTARGS &
or - and I think that's the more elegant way - just add the init.d. script to the right runlevels so that the server is started automatically with system start or when entering accoring runlevels.
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 