Troubleshooting
Search the Knowledge Base topics as a wide variety of issues and remediations are covered there.
Diagnosing Problems
Whenever you need to diagnose system problems (and before contacting Aerospike Technical Support), we recommend that you review the following points:
- If you are having problems in starting a server, check the server logs. The logs usually mention the reason for startup failure.
- If the servers are already running, check system information by running
asadmand using theinfocommand. Ensure none of the statistics are in red. - Check for cluster problems:
- Check the system latency
- Review the log files (Configuring log files on each node to see if there are warning or error messages.
- Check your client machines (application servers and application logs).
- Check the network (switches/routers/firewalls/load balancers)
- Some problems could be data-related and need to be corrected on application side.
- Search through our Knowledge-Base reference guide if the issue observed has been previously reported - Knowledge Base reference.
The troubleshooting pages in this section of the documentation provide details for how to address some common problems you may encounter when running the Aerospike software.
Check for Aerospike upgrades
After you figure out the problem, be sure to check the release notes to see if a newer version of Aerospike Database resolves your issue. If you need to upgrade your server software, you can do a hot upgrade using rolling upgrade procedure.
In the troubleshooting pages, we assume that you know how to do the following standard tasks with Aerospike Database:
- How to look at the Aerospike log (by default it is in
/var/log/aerospike/aerospike.log. - How to use asadm to update configuration dynamically.
- How to update parameters in the configuration file
- How to use asinfo to read and write parameters dynamically.
- How to check latency.
- How to start and stop asd (the main Aerospike process).
- How to do a cold or a fast restart.