hcienginerestart

This command restarts engine processes, threads, and MonitorD. It supports the GUI for restarting an engine process, thread, and MonitorD.

hcienginerestart -d delay interval -p process [,process...] [-n]

or

hcienginerestart -d delay interval -p process [,process...] 
[-h host] [-s thread [, thread...] ] -- allElse [-n]
  • -d delay interval is the unit for delay interval is seconds. The default value is 30s, and is defined in the GUI at the site-level configuration. For a different time-out, use the command-line directly.
  • -p process [,process...] restarts the indicated processes.
  • -h host is the name of the remote host to run the engine on.
  • -s thread is a comma-separated list of threads to restart.
  • -- separates the script args from engine args.
  • allElse specifies all other arguments are passed to the engine.
  • -n specifies to not run the engine in a service on Windows.

For hciengine:

hcienginerestart -d delay interval -p process[,process...] 
[-h host] [-s thread[,thread...]] -- allElse
  • If hcienginerestart is invoked when the process is not running, then the hcicmd invocation to stop would fail. If it verifies that the process is not running after the delay interval has elapsed, then it attempts to start it with the remaining arguments.
  • The -p argument can be a process list.
  • If the process cannot be stopped, then it returns an error after the delay interval has elapsed.
For example, to restart a process:
hcienginerestart -d delay interval -p process

For threads:

hcicmd -p process -c "thread_name prestart delay interval"
  • If hcicmd is invoked when the process is not running with thread_name prestart, then it does not connect. In this case, you can invoke hcienginerun with the thread start args. For example:
    hcicmd -p process -c thread name prestart delay interval
  • In some instances, hcicmd is called when the process is running, but the indicated thread is not. When this happens, it starts the thread after the delay interval has elapsed.
  • In other instances, hcicmd is called when the process is running, but the indicated thread has not stopped. When this happens, it returns an error after the delay interval has elapsed.

For site daemons:

hcisitectl [-f] [-h host] [{ -K | -k what }] [{ -S | -s what}] 
[{ -R | -r what} -d delay interval] [-u #users] [-A args]

For site daemons it restarts when the -R or -r argument is used.

  • If hcisitectl is invoked this way when the daemon is not running, then the invocation to stop fails. If it can verify that the process is not running after the delay interval has elapsed, then it still attempts to start it.
  • If it is unable to stop the daemon, then it returns an error after the delay interval has elapsed.
  • If using -R or -r, then the -d argument is required.

Examples:

  • To restart the MonitorD:
    hcisitectl -r m -d delay interval
  • To restart the Lock Manger:
    hcisitectl -r l -d delay interval
  • To restart all daemons:
    hcisitectl -R -d delay interval

The unit for delay interval is seconds. The default value is 30s, and is defined in the GUI at the site-level configuration. For a different time-out, you can change delay interval .