Actions Component

[gregwhite]

We upgraded Nagios to the latest release (5.8.6) and copied the data from the old server to the new. However, all the links we had created in the action component didn't come with the backup. Is there a way to retrieve this information?

Thanks,
Greg

[benjaminsmith]

Hi Greg,

That data is stored in the nagiosxi database, so it should have transferred during the restore process unless there was some kind of error.

How did you do the migration? Did you run backup/restore scripts between the two systems?

Run the following query to see if the data is in your nagiosxi database, log into the CLI:

Code: Select all

echo "select value from xi_options where name='actions_component_options';" | mysql -u root -pnagiosxi nagiosxi

Regards,
Benjamin

[gregwhite]

When we ran the command a string of data was displayed. You can see that it is the data that was in the actions component. However, when you go in to the actions component it looks like it is starting brand new, no data.

[benjaminsmith]

Hi Greg,

The component might be having an issue pulling the data, can you run the following tail command as root and then try load the settings for the actions component as before and post the full output to the thread.

Code: Select all

 tail -f /var/log/httpd/*error_log /var/log/mysql/mysqld.log

This command will work on a Cent 8, but might need adjustment for other operating systems. Let me know what OS you have if you need assistance with that.

Also, please PM your system profile. Thanks, Benjamin

To send us your system profile.
Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button

[gregwhite]

We are running CentOS 7.9. Also, we converted our DB to MARIAdb. Not sure if this alters the tail command or what we need to do. I tried to attach a system profile but it is 54mb and it failed because limit is 50mb.



Greg

[benjaminsmith]

Hi Greg,

The tail command would be adjusted to:

Code: Select all

 tail -f /var/log/httpd/*error_log /var/log/mariadb/mariadb.log

Another option would be to split up the profile into separate files. Or if you open the zip, you can remove the additional archive (.tar.gz) inside containing the config files and then compress it again. Those files are not necessary.

--Benjamin

[gregwhite]

actions-component-14-oct-2021.zip

Attached are the results

Here is the output for the first 2 items that you requested:

echo "select value from xi_options where name='actions_component_options';" | mysql -u root -pnagiosxi nagiosxi

and the corrected tail of the mariadb log:

tail -f /var/log/httpd/*error_log /var/log/mariadb/mariadb.log

What’s interesting is that the ssl_error_log didn’t start filling up with those errors until I enabled the actions component and applied the settings.


After that re-running the select statement yielded only the following:

[root@lvnagiost01 tmp]# echo "select value from xi_options where name='actions_component_options';" | mysql -u root -pnagiosxi nagiosxi
value
a:2:{s:7:"enabled";i:1;s:7:"actions";a:0:{}}
[root@lvnagiost01 tmp]#

We deleted that Tar.gz file but profile still too big. Not sure how to split it.

[benjaminsmith]

Hi,

The output below confirms that the action component is enabled but there is nothing configured. If you go to Admin > Manage Components > Actions > Settings, it should look like:

actions-screenshot.png

Is this is production server? We can try to restore the nagiosxi database from the backup archive once more.

--Benjamin

[gregwhite]

I will be out of the office on Monday and Tuesday. I will follow up on Wednesday when I get back.

Thank you for your help.
Greg

[benjaminsmith]

Hi Greg,

Sounds good.

Have a great weekend!