Starting and Stopping UNIX Platform Agents

The specifics of this procedure depend on your UNIX system (SysVinit, systemd, or Solaris SMF).

SysVinit

On a SysVinit system, use the scheduler script to start and stop network-processor daemons. You can start all network-processor daemons, or start a specific instance. When doing so, you can optionally provide a Platform Agent instance directory (the installation directory of the Platform Agent instance).

`${InstallDir}`/latest/etc/scheduler {start|start-instance|stop|stop-instance|list|list-instances|restart|status}

start                                                         start all network processors
start-instance <instance_name> [<instance_directory>]         start a specific instance
stop                                                          stop all network processors
stop-instance <instance_name> [<instance_directory>]          stop a specific instance
list | list-instances                                         list all instances
restart                                                       restart all network processors
status                                                        list all instances with the current status

systemd

On a systemd system, use the systemctl command, as follows.

systemctl {start|status|stop} scheduler[@<instance>]

systemctl start scheduler          start all instances
systemctl start "scheduler@<instance>"                        start instance <instance>
systemctl stop scheduler          stop all instances
systemctl stop "scheduler@<instance>"         stop instance <instance>
systemctl status scheduler                                    print status of scheduler unit
systemctl status "scheduler@<instance>"                       print status of <instance> unit

Configuring Start at System Startup

If you enable a platform agent service on a particular computer, the Platform Agent instance will be started at system startup. If you disable a Platform Agent service, it will not start at system startup.

To enable or disable a Platform Agent service for a specific instance, use commands like the following:

systemctl enable "scheduler@<instance>"
systemctl disable "scheduler@<instance>"

To enable or disable a Platform Agent service for all instances, use commands like the following:

systemctl enable scheduler
systemctl disable scheduler

If you make changes to the systemd configuration, you must reload the configuration, like so:

systemctl daemon-reload
systemctl reset-failed

Solaris SMF

On an SMF system, use the following tools to control Platform Agent services.

• svcs: Use this to inspect service status.
• svcadm: Use this to enable, disable, and clear maintenance flags on services.
• svccfg: Use this to configure SMF.

Starting and Stopping Platform Agent Services

if you do not specify a specific Platform Agent instance to start (enable) or stop (disable), then all Platform Agent instances will be affected.

svcadm enable redwood/scheduler[:<instance_>]
svcadm disable redwood/scheduler[:<instance_>]

Troubleshooting Platform Agent Services

If a Platform Agent service instance fails, its maintenance flag is set, and the service cannot be enabled again unless the flag is cleared. In general, you can inspect the SMF log using svcs -x redwood/scheduler:<instance> and the Platform Agent logs under <install_dir>/var/<server_sid>/<instance>/trc/.

Once you have resolved the issue, check if any processes associated with the Platform Agent instance are running, terminate any existing processes, and clear the maintenance flag for the service, like so:

#Check if any processes are still running for the service:
svcs -p redwood/scheduler:<instance>
#Terminate any processes, note that these might be associated with RunMyJobs processes
pkill -9 <process_name>
#Clear the maintenance flag
svcadm clear redwood/scheduler:<instance>