Manage the Monitor server

The Monitor server checks that the SecureTransport servers are running and restarts them if they terminate. However, the Monitor server does not restart a server if a dependent server is not running. The Monitor server can run on SecureTransport Server or SecureTransport Edge.

  • Click Start.

You can configure the overall behavior of the Monitor server by changing cluster-wide server configuration parameters.

  • Cluster.ServiceStatusChecks.delayBetweenChecks – the time in seconds that the Monitor server waits between checking the servers. The default is 5 seconds. This parameter is only supported for Standard Cluster (SC).
  • Cluster.ServiceStatusChecks.serviceExpireTime – the time in seconds that a server is down before the Monitor server stops checking the server and attempting to restart it. The default is 15 seconds. Once the Monitor server stops attempting to restart a service, you must restart it manually. This parameter is only supported for Standard Cluster.

You can configure how the Monitor server attempts to restart each server by changing local configuration parameters. The parameters include one of the server names: ADMIN, AS2D, DB (embedded database only), FTPD, HTTPD, SSHD, and TM.

  • Monitor.<server>.retryCount – how many times the Monitor server tries to restart the server. The default value varies depending on the server.
  • Monitor.<server>.retryDelay – the time in seconds that the Monitor server waits between attempts to restart the server. The default value varies depending on the server.
Note The Monitor server must use a non-SSL connection to check the PeSIT server, so you must select Enable PeSIT (no SSL) on the Server Control page for monitoring. To prevent non-SSL PeSIT connections, restrict access to the non-SSL port you configure to the system where the PeSIT server and the Monitor server are running.

Entries in crontab start the monitor server processes. For example,

* * * * * "<FILEDRIVEHOME>/bin/monitor_admin" >> /tmp/monitor_admin.out 2>&1

controls monitoring of the Administration Tool server. The entries run the processes every minute and append the log output to files in the /tmp directory on UNIX-based systems and the <FILEDRIVEHOME>\..\cygwin\tmp directory on Windows.

Note On Windows, it is not possible to modify existing cron jobs or to use cron to run any jobs other than the predefined SecureTransport jobs. Instead, use the Windows Task Scheduler.

Related topics:

Related Links