Diagnosing AMP issues
Most issues with AMP are usually caused by minor configuration issues that can be easily solved.
If you encounter a problem with AMP, follow the following steps:
- DO NOT attempt to uninstall/reinstall AMP. AMP cannot be 'fixed' by reinstalling it, and by doing so you will destroy any information that would help you solve the issue.
- AMP has a 'Debug Logging' mode that can provide additional information about what it's doing to aid in diagnostics. In AMPConfig.conf you will find a setting called
Monitoring.LogLevel- change it's value to
0to enable debug logging.
- If you've just updated AMP and the web interface no longer works or throws an error when you visit it, press CTRL+F5 to reload the page without using the cache. This will fix most in-browser issues.
- Check AMPs most recent log file. Every AMP instance creates a log file as soon as it starts up. This can be found in the AMP_LOGS directory for that specific instance in the datastore. Under Linux the default datastore directory is
/home/AMP/.ampdata/Instances, under Windows you can right click on an instance in the Instance Manager and hit 'browse datastore'. The log files are ordered by date and time, so make sure you're picking the most recent.
- Skip to the end of the log file. If AMP knows exactly what went wrong then it'll show you a diagnostics message, explaining what the problem is and possibly how to fix it.
- If it is not clear what the problem is, upload a copy of the most recent log to a paste service like hastebin.net/pastebin.net, and post a link to the log to either the support board, or to Discord - making sure to include the following:
- What OS you're using
- What version of AMP you're using (Do not say 'Latest', always check the actual version - it's shown in the log)
- What you're trying to do
- What actually happens (Do not say 'Nothing', always be brutally specific)