Nagios Support Forum

Hi Team,

We have observed that whenever we patch the Nagios server, SQL named instances configuration automatically add four \ symbols in the arguments.

The plugin for mssql_health is supposed to input the named instances with four \ symbols however, for some of the 2012 R2 database servers the configuration is giving the correct output only if there are two \ symbols in the arguments.

After patching as the arguments are automatically getting updated with four \ symbols we are having to update the configuration again.

Can someone please help understand what is causing this and how it can be fixed?

Regards,
Rebecca Murray

Hi Rebecca,

Is this happening when you upgrade XI, or from yum updates to the OS, or both?

--Jeffrey

Hi Jeffrey,

This happens only when we do the yum updates.

Regards,
Rebecca Murray

Could you attach your actual plugin so we can have a look at it?
Also, if you wanted to PM a system profile, that would also be helpful.
--Jeffrey

Hi Jeffrey,

Thanks for checking this.

Please find attached copy of the plugin that we use.

I'll PM you a copy of the profile as well.

Regards,
Rebecca Murray

What is the output of these commands:
Are you saying that once you run a yum update you need to go update all of the services for 2012 R2 servers in Configure > Core Config Manager > Services in order to resolve it? What I mean is your also not changing the plugin too, right?

Can you check your yum history and show us what packages were updated?

Additionally, check_mssql_health isn't our plugin so it's unlikely related to the plugin.

Hi Sean,

Yes, that's right we make the changes in the service configurations not the plugin or the command as these are for only named instances which are mentioned in arguments.

Here the output of the commands.

[root@host ~]# rpm -qa | grep nagiosxi
nagiosxi-deps-el7-5.6.14-1.noarch
[root@host ~]# rpm -qa | grep mssql
php-mssql-5.4.16-9.el7.x86_64
python2-pymssql-2.1.4-1.el7.x86_64

[root@host ~]# yum history
Loaded plugins: fastestmirror
Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast
ID | Login user | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
61 | root <root> | 2020-04-27 03:01 | Update | 1
60 | root <root> | 2020-04-14 16:11 | Update | 1
59 | <nagios> | 2020-03-31 04:03 | Update | 1
58 | root <root> | 2020-03-22 06:34 | I, O, U | 292 ##
57 | root <root> | 2020-02-04 12:56 | Install | 3 #<
56 | <nagios> | 2020-01-21 22:54 | Update | 1 >
55 | <nagios> | 2019-12-11 20:33 | Update | 1
54 | <nagios> | 2019-11-08 11:58 | Update | 1
53 | <nagios> | 2019-10-01 09:25 | Update | 1
52 | <nagios> | 2019-10-01 09:24 | Update | 1
51 | root <root> | 2019-09-19 10:42 | Install | 13
50 | root <root> | 2019-08-30 14:25 | Install | 1
49 | root <root> | 2019-08-30 14:07 | Install | 1
48 | root <root> | 2019-08-22 23:37 | Install | 4
47 | <nagios> | 2019-08-21 20:14 | Update | 1
46 | root <root> | 2019-08-19 13:19 | Install | 11
45 | root <root> | 2019-08-19 13:18 | Install | 1
44 | <nagios> | 2019-08-17 12:49 | Update | 1
43 | root <root> | 2019-08-11 13:43 | Install | 2
42 | root <root> | 2019-08-11 12:50 | Install | 5 EE
history list


Regards,
Rebecca Murray

You would need to show the packages like this:
- Get the ID from the yum history output

Hi Sean,

Please find below details:



[root@host ~]# yum history info
Loaded plugins: fastestmirror
Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast
Transaction ID : 61
Begin time : Mon Apr 27 03:01:41 2020
Begin rpmdb : 775:5092e538fdbd9ea4ba373778993b0963fea8e79c
End time : (0 seconds)
End rpmdb : 775:80d1459bf274b3602c9be0b0ba31ac6fbd6713bd
User : root <root>
Return-Code : Success
Command Line : -y --nogpgcheck localinstall /tmp/nagiosxi/nagiosxi-deps-el7-5.6.14-1.noarch.rpm
Transaction performed with:
Installed rpm-4.11.3-40.el7.x86_64 @base
Installed yum-3.4.3-163.el7.centos.noarch @base
Installed yum-plugin-fastestmirror-1.1.31-52.el7.noarch @base
Packages Altered:
Updated nagiosxi-deps-el7-5.6.13-1.noarch @/nagiosxi-deps-el7-5.6.13-1.noarch
Update 5.6.14-1.noarch @/nagiosxi-deps-el7-5.6.14-1.noarch
history info

I'm stumped. I can't think of a reason why this would occur after running a yum update. No yum packages should modify the nagios configs.