Troubleshooting Orchestrator Startup Operations

The Orchestrator log can be found in the following default location:

C:\Program Files (x86)\Aspera\Orchestrator\www\var\run\log\orchestrator.log

The log file is rotated each day to prevent it from growing too large.

MySQL:Orchestrator relies on the proper functioning of the MySQL database. If the MySQL database is not started, Orchestrator won’t start. The following are reasons that a user might not be able to start the MySQL database:

The user doesn’t have permissions to run MySQL.
The disk drive is full.
The following conditions are true for MySQL or the user who started MySQL:
- Doesn’t have the rights to write into mysql logs.
- Cannot write to the disk with temp files (PID files, SOCK files).

Ruby: If the Ruby executable or Ruby Installation under C:\Ruby have been deleted or the user doesn’t have permissions to run Ruby, it may be the case that Ruby and other Ruby related executables have been added to the PATH environment variable. They have to remain added to the PATH variable on this machine.

License file: Orchestrator won’t start if the license file is absent or if expired. Look for messages in the log file that indicate this issue. The footer in the Orchestrator UI also gives an indication of when a license file expires.