Proceed with caution
We do not recommend making any direct changes to the Opsview databases. Wherever possible, you should use the API instead.
Changes to the Opsview databases can irreparably damage your Opsview installation.
Always take appropriate backup precautions before making any direct changes to the Opsview databases.
All connections to the Opsview databases are routed through the opsview-loadbalancer
component on the orchestrator. The load balancer does not accept outside connections by default. This article explains how to allow external connections to the database via the orchestrator.
Prerequisites
- None
Process
Nonpersistent changes
The following changes may not persist across runs of opsview-deploy. You may need to re-apply these changes each time you run opsview-deploy.
- Log in to your orchestrator as
root
. - Open the file
/opt/opsview/loadbalancer/etc/database-balance.cfg
in your preferred text editor. - Change the line
bind 127.0.0.1:13306
to
bind 0.0.0.0:13306
- Restart the
opsview-loadbalancer
component usingopsview-monit
:
/opt/opsview/watchdog/bin/opsview-monit restart opsview-loadbalancer
Comments
0 comments
Please sign in to leave a comment.