Skip to content
Troubleshooting

Startup Failure

In some instances, AMI will fail to launch. This is usually not a cause for concern. Please refer to this page for common reasons why AMI fails to launch.

Note

If you have updated Java recently, your VM options may be out of date. Check this first by following the instructions here.

General

Causes for startup failures will be tracked in AMI's logging systems. See the list below for where your various logs and AMI log files will be located.

To diagnose startup failures, information can generally be found in the following:

  1. The error.log file in the amione directory where errors are logged

  2. amione/log/AmiOne.log where non-terminating errors are logged

To diagnose startup failures, information can generally be found in the following:

  1. Logs that appear in your terminal when running AMI

  2. amione/log/stderr.log where errors are logged

  3. amione/log/AmiOne.log where non-terminating errors are logged

Common errors

Error: Could not open port

The most common error when starting AMI is that it doesn't appear to run. This is usually because AMI is already running or you are attempting to launch an AMI instance with a port clash.

Make sure that AMI is not already running by checking if AmiOne.exe is running under "Background Processes" in the Task Manager.

If AMI is definitely not running, then check the ports in your configuration to ensure they do not clash with any other program. See this page for which ports to configure for AMI.

The most common error when starting AMI is that it doesn't appear to run. This is usually because AMI is already running or you are attempting to launch an AMI instance with a port clash.

Make sure that AMI is not already running by checking for the AmiOne process.

If AMI is definitely not running, then check the ports in your configuration to ensure they do not clash with any other program. See this page for which ports to configure for AMI.

Error: Could not create the Java Virtual Machine

In Linux, assuming you have followed the steps here, if you are still seeing the following error type in stderr.log:

1
2
3
Unrecognized option: <SOME_JAVA_OPTION>
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

You will need to navigate to the amione directory and modify the AMI_One_linux.vmoptions file to remove the corresponding line.

Alternatively, you can delete the VM options file and remove the corresponding option(s) from the start.sh script and rerun to generate a new VM options file.

Warning

Editing your start.sh file is generally not recommended as upgrades will typically not maintain any changes.

If you do require further assistance to configure your start.sh script, please reach out to us at support@3forge.com