The following table outlines some specific areas to check when experiencing different problems:
Table 4.17. Responses to Specific Errors
| Severity | Issue | Suggested Action(s) |
|---|---|---|
| Critical | Membase Server does not start up. | Check that the Membase service is running. |
| Check error logs. | ||
| Try restarting the service. | ||
| Critical | A server is not responding. | Check that the Membase service is running. |
| Check error logs. | ||
| Try restarting the service. | ||
| Critical | A server is down. | Try restarting the server. |
| Use the command-line interface to check connectivity. | ||
| Informational | Bucket authentication failure. | Check the properties of the bucket that you are attempting to connect to. |
The primary source for run-time logging information is the Membase Web Console. Run-time logs are automatically set up and started during the installation process. However, the Membase Server gives you access to lower-level logging details if needed for diagnostic and troubleshooting purposes. Log files are stored in a binary format in the logs directory under the Membase installation directory. You must use a Membase utility (browse_logs) to extract the log contents from the binary format to a text file.