Troubleshooting
vPlus 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:
appserver
which has all messages coming from the application server - which hosts web UI and APIapi
which has all messages related to - the core vPlus Server applicationcloudagent
which has all messages from vPlus Cloud Agentcloudserver
which has all messages from vPlus Cloud core part
To verify if services are running, you can use:
systemctl status vprotect-server
for Serversystemctl status vprotect-node
for Node orvprotect status
If you don't find here the root cause of the problem, you can switch vPlus to DEBUG mode, and recreate the task to generate logs in DEBUG mode.
Last updated