Metasploit stores system events in log files. You can use the information in the log files to troubleshoot issues you've encountered with Metasploit. For example, if you need to troubleshoot an issue with updates, you can view the license log to see a list of events related to product activation, license keys, and updates.
Log files can become large over time, so you may need to manually clear the log files to reduce the amount of disk space that they consume.
The follow logs are available for you to use to troubleshoot issues:
- Framework log - This log contains information about loading the Metasploit Framework. You can view this log to troubleshoot issues that you may have with running modules. The Framework log is located in
- License log - This log contains the events related to product licensing and product updates. You can view this log to troubleshoot problems that you may have applying a license key or installing an update. The license log is located in
- PostgreSQL log - This log documents the start up and shutdown notices. You can view this log to track the latest events in the database. The PostgreSQL log is located in
- Production log - This log contains all Rails events. You can use this log to troubleshoot Rails issues, such as routing errors, and to trace the actions that were taken for a particular connection. The production log is located in
- Pro service log - This log contains the events for Pro service. You can view this log to troubleshoot errors with the Metasploit service. The Pro service log is located in
- Task log - This log contains all activity for tasks performed in Pro. You can use this log to track the progress of tasks and troubleshoot errors that occur. The task log is located in
- Thin log - This log contains the events for Thin service. You can view this log to diagnose issues between Rails and Nginx. The Thin log is located in
- Web server error log - This log contains all Nginx errors and warnings. You can view this log to identify if an issue is related to Nginx rather than Rails or Pro Service. The error log is located in
- Web server access log - This log contains every GET and POST request to Nginx and logs successful HTTP requests. Use this log to track down Rails issues. The access log is located in
- Report log - This log contains the report logs.
- Export log - This log contains the export information.