1.3 Troubleshooting Orchestrate Server Issues

The following sections provide solution to the problems you might encounter while using the PlateSpin Orchestrate Server:

Orchestrate Server Might Appear to Be Deadlocked When Provisioning Large Numbers of Jobs with Subjobs

Source: PlateSpin Orchestrate Server.
Explanation: In some deployments where a large number of running jobs spawn subjobs, the running jobs might appear to stop, leaving jobs in the queue.
Possible Cause: This occurs because of job limits set in the Orchestrate Server to avoid overload or “runaway” conditions.
Action: If this deadlock occurs, you can slowly adjust the job limits to tune them according to your deployment. For more information, see The Job Limits Panel in the PlateSpin Orchestrate 2.6 Development Client Reference.

Orchestrate Server Might Hang if the System Clock Is Changed Abruptly

Source: PlateSpin Orchestrate Server
Explanation: As with many applications, you should avoid abrupt changes in the system clock on the machine where the PlateSpin Orchestrate Server is installed; otherwise, the agent might appear to hang, waiting for the clock to catch up.

This issue is not affected by changes in clock time occurring from daylight saving adjustments.

Action: We recommend that you use proper clock synchronization tools such as a Network Time Protocol (NTP) server in your network to avoid large stepping of the system clock.

Authentication to an Active Directory Server Might Fail

Source: PlateSpin Orchestrate Server
Explanation: A simplified Active Directory Server (ADS) setup might be insufficient because of a customized ADS install (for example, namingContexts entries that generate referrals when they are looked up)..
Possible Cause: The checking logic in the current AuthLDAP auth provider assumes that if any namingContext entry is returned, it has found the domain and it stops searching.
Action: If you encounter this issue, you need to manually configure LDAP as a generic LDAP server, which offers many more configuration options.

The Orchestrate Server Must Have Sufficient RAM

Source: PlateSpin Orchestrate Server.
Explanation: If the PlateSpin Orchestrate Server fails to start after installation and configuration, sufficient RAM might not be installed on your hardware or assigned to the VM you are attempting to use.
Possible Cause: The PlateSpin Orchestrate Server requires 3 GB of RAM to function with the preset defaults.
Action: If the server does not start, increase your physical RAM size (or, for a VM, increase the setting for virtual RAM size). Alternatively, you can reduce the JVM heap size, as explained in Step 10 of the Installation and Configuration Steps in the PlateSpin Orchestrate 2.6 Installation and Configuration Guide.