Welcome to docs.opsview.com

Differences

This shows you the differences between two versions of the page.

opsview4.6:readonlydatabase [2015/05/27 16:31]
pknight Updated for opsview.defaults.
opsview4.6:readonlydatabase [2015/05/28 17:11] (current)
pknight Mention to quote opsview.conf variables.
Line 14: Line 14:
</code> </code>
-///usr/local/nagios/etc/opsview.defaults// has database related "_ro_" variables. Copy these to //opsview.conf// and change them to point to the slave MySQL server. The "opsview_ro_" variables are for the opsview user, and the "runtime_ro_" variables are for the nagios user. Any variables that aren't copied into //opsview.conf// or changed will default to their respective values from the non-read-only database. You can obtain the encrypted versions of the passwords by running ///usr/local/nagios/bin/opsview_crypt//.+///usr/local/nagios/etc/opsview.defaults// has database related "_ro_" variables. Copy these to //opsview.conf// and change them to point to the slave MySQL server. The "opsview_ro_" variables are for the opsview user, and the "runtime_ro_" variables are for the nagios user. Any variables that aren't copied into //opsview.conf// or changed will default to their respective values from the non-read-only database. Be sure to double quote the variable values (see the other database related values around that area in //opsview.defaults// for some examples). You can obtain the encrypted versions of the passwords by running ///usr/local/nagios/bin/opsview_crypt//.
Restart opsview-web: "service opsview-web restart". Dashboard and other parts of Opsview should now be using the slave MySQL database for most status views. Restart opsview-web: "service opsview-web restart". Dashboard and other parts of Opsview should now be using the slave MySQL database for most status views.
Navigation
Print/export
Toolbox