# Troubleshooting

Storware Backup & Recovery log directory path is `/opt/vprotect/logs` - this is the first place to check for the root cause of errors. All log files are also accessible from `Logs` sections in web UI.

CLI interface records messages in `vprotect_client.log` files under the subdirectory with the same name as the node. In the same directory, you can also find `vprotect_daemon.log` files that contain all engine-related messages.

Web UI has directories where it stores log files:

![](https://content.gitbook.com/content/wUsKWUrceYHp8e9TJ00e/blobs/dU9B2tVxgV4oNvu6PnRc/Troubleshooting_1.png)

* `appserver` which has all messages coming from the application server - which hosts web UI and API
* `api` which has all messages related to - the core Storware Backup & Recovery Server application
* `cloudagent` which has all messages from Storware Cloud Agent 
* `cloudserver` which has all messages from Storware Cloud core part

To verify if services are running you can use:

* `systemctl status vprotect-server` for Server
* `systemctl status vprotect-node` for Node or `vprotect status`

If you don't find here the root cause of the problem you can switch Storware Backup & Recovery to [DEBUG mode](https://docs.storware.eu/troubleshooting/how-switch-vprotect-to-debug-mode), and recreate the task to generate logs in DEBUG mode.