NagiosXI post upgrade

[jdalrymple]

Our installer just installs mysql-server from the base repo. 5.1.73 is the current version in Cent66's base repo, were you hoping to compile from source? If so you'll probably end up with a version that works fine, but down the road we may have more trouble helping you solve weird problems, mostly due to the alternative install strategy and less to do with the actual version.

[jdalrymple]

As for the other bit ... the common tools are base64 encoded values in the postgres database. I ran the backup script and this row did come back OK.

If you want to dig into your backup, you can grep for 'commontools' in nagiosxi.sql and then punch the long ugly string into a base64 decoder:

http://www.string-functions.com/base64decode.aspx

I saw what I expected to see... can you see if you do too?

Code: Select all

[jdalrymple@localhost 1427396503]$ grep commontools /pgsql/nagiosxi.sql
130     commontools     YToxOntzOjY6ImpqYWo0YSI7YToyOntzOjQ6Im5hbWUiO3M6ODoiTmV3IFRvb2wiO3M6MzoidXJsIjtzOjIxOiJodHRwOi8vd3d3Lmdvb2dsZS5jb20iO319

[mon-team]

I get this output both in my backup pre-upgrade(XI 2012R2.9) and post-upgrade (XI 2014R2.6)

[root@nagios]# grep commontools pgsql/nagiosxi.sql
149 commontools a:14:{s:6:"lvfcgc";a:2:{s:4:"name";s:4:"YYY";s:3:"url";s:16:"https://XXX";}s:6:"va6ulk";a:2:{s:4:"name";s:5:"YYY";s:3:"url";s:23:"https://XXX";}s:6:"sqieuf";a:2:{s:4:"name";s:10:"MONITORING";s:3:"url";s:28:"https://XXX";}s:6:"hoaclk";a:2:{s:4:"name";s:23:"SD CONSOLE [DEPRECATED]";s:3:"url";s:54:"https://XXX";}s:6:"5pn5u9";a:2:{s:4:"name";s:20:"SERVICE AVAILABILITY";s:3:"url";s:50:"https://XXX";}s:6:"cvvaps";a:2:{s:4:"name";s:9:"YYY";s:3:"url";s:27:"https://XXX";}s:6:"pm64k0";a:2:{s:4:"name";s:22:"VIDEOWALL KA-SAT GW1-4";s:3:"url";s:71:"https://XXX";}s:6:"ef4h76";a:2:{s:4:"name";s:22:"VIDEOWALL KA-SAT GW5-8";s:3:"url";s:71:"https://XXX";}s:6:"uu0qs7";a:2:{s:4:"name";s:18:"VIDEOWALL TOOWAY I";s:3:"url";s:55:"http://XXX";}s:6:"gbcnfe";a:2:{s:4:"name";s:15:"VIDEOWALL YYY";s:3:"url";s:48:"https://XXX";}s:6:"seskin";a:2:{s:4:"name";s:4:"YYY";s:3:"url";s:15:"http://XXX";}s:6:"ndfc03";a:2:{s:4:"name";s:12:"YYY";s:3:"url";s:19:"http://skylogic.lan";}s:6:"4mio9b";a:2:{s:4:"name";s:9:"YYY";s:3:"url";s:20:"http://XXX";}s:6:"f0utp5";a:2:{s:4:"name";s:8:"INTRANET";s:3:"url";s:74:"http://XXX";}}

It seems like the common tools in XI 2012R2.9 are not base64 encoded values in the postgres database while XI 2014R.2.6 expects these values to be encoded.

[jdalrymple]

I've inquired with the developers. I've also tried to base64 encode the contents you sent to me and shovel it into my XI instance and it just broke it. I'll get with them for a reason and/or solution.