You are here

4.6 - error in install process - RHEL6

4 posts / 0 new
Last post
gpburdell93
gpburdell93's picture
4.6 - error in install process - RHEL6

The 4.6 install instructions (like the 4.5 instructions) call for the editing of the /usr/local/nagios/etc/opsview.conf file, to replace the 'changeme' values with the newly selected MySQL root password.

This file no longer contains entries with values 'changeme', which is a minor worry.

A greater worry is that the entries read:

$dbpasswd_encrypted

$odw_dbpasswd_encrypted

$runtime_dbpasswd_encrypted

etc.

and the /usr/local/nagios/bin/db_mysql script fails when running against that file.

This was an installation on a pristine server from the Opsview repo.

Regards,

Chris

smarsh
smarsh's picture
Hi Chris,

Hi Chris,

Good spot - since 4.6 and the introduction of security wallet we no longer have 'changeme' as a clear text password in opsview.conf, instead they are all auto-created authentication strings that dont really need to be changed.

I've updated the documentation to reflect this. With regards the 2nd point, "db_mysql fails", can you contact Opsview support via http://support.opsview.com who will be happy to assist.

Best,

Sam

gpburdell93
gpburdell93's picture
Thanks for correcting the

Thanks for correcting the documentation.  That means a great deal on new installs.

I corrected the opsview.conf file myself by removing '_encrypted' from the parameter names.  After I did that, the db_mysql script worked.  I'll open a ticket with support noting the change as a possible error.

I noted that my previous 4.5 version upgraded to 4.6 without a problem, and the opsview.conf parameters remained unchanged.

Regards,

Chris

smarsh
smarsh's picture
Hi Chris,

Hi Chris,

Yeah on 4.6 systems that were previously 4.5 and below, we didnt want to auto-encrypt and change things incase it caused problems for the users (i.e. that was the only place a password was being stored!). Therefore in upgrades, opsview.conf will have odw_passwd rather than odw_passwd_encrypted, for example.

Same goes for attributes - we didnt want to auto-encrypt someones WMICREDENTIALS username/password, incase that was the only place it was being stored :)

Cheers,

Sam