Page 1 of 1

all nagiosadmin dashboards disappeared

Posted: Tue Feb 13, 2018 5:03 am
by rjjimenez
Hello.

After running the upgrade from nagiosxi to version 5.4.12, all nagios xi dashboards have disappeared.

I attached the file with the dashboards extracted from the database with the following query: echo "select * from xi_usermeta where keyname like '%dash%';" | mysql ...

the problem is that literally all disappeared and only shows me the dashboard "home" that always appears with nagios by default, but the rest do not appear.

I have also tried this query that I had previously provided, because this property would have been lost when I upgraded nagios:

echo "alter table xi_usermeta modify keyvalue LONGTEXT;" | mysql -uroot -pnagiosxi nagiosxi
dashboard-nagiosxi.png
Can you tell me what the problem is and how can I recover the data from all the dashboards?

Thank you very much

Re: all nagiosadmin dashboards disappeared

Posted: Tue Feb 13, 2018 11:24 am
by cdienger
What version was the XI server on previously ? What where the upgrade steps taken? Do you have a backup of the previous install? If so, we may be able to restore the dashboards from there but I'll need to look into the steps.

Please run echo "select * from xi_users;" to identify the user_id of the user that was logged in when the screenshot provided was taken.

Re: all nagiosadmin dashboards disappeared

Posted: Tue Feb 20, 2018 3:47 am
by rjjimenez
good morning.

We have made a backup recovery and everything works correctly again.

Today we have returned to make the upgrade from version 5.4.8 (current) to version 5.4.12, after executing the upgrade by script https://assets.nagios.com/downloads/nag ... ctions.pdf we verify that everything is going to fail, all dashboards and most reports disappear and notifications by email they stop working so we had to go back to version 5.4.8 again.

Attached the log of the upgrade:
upgradeTo5-4-12.log

Re: all nagiosadmin dashboards disappeared

Posted: Tue Feb 20, 2018 3:02 pm
by tgriep
We are currently looking to this issue and when the bug is identified, we will try and update the post with a solution.