mySQL 5.1.73 End of Support

[dwhitfield]

Red Hat does support the packages.

We did a bit more digging and Red Hat only supports 5.1.x for 5.0.x upgrades. We have submitted internal bug report 9738 for this issue.

Thank you for bringing this issue to our attention. I apologize for our oversight on the issue.

I know you already have https://support.nagios.com/forum/viewto ... 79#p198879 but if you have any other suggestions or questions about this MySQL issue, we would be happy to hear them. Alternatively, is it ok if we go ahead and lock this thread?

As @Box293 mentioned, you could try to upgrade your MySQL. However, we do not officially support the MySQL community addition.

[jomann]

Clarification on the above post. MySQL versions mentioned for upgrade path only are for CentOS/RHEL 5.x (where they have added mysql 5.5) and not for 6.x versions of the OS which still uses MySQL 5.1.x.

Either way, upgrading your MySQL should not have an affect on the software - although we won't support the upgrade process since we have always stuck with whatever MySQL version is provided by the OS distribution.

[rajasegar]

Clarification on the above post. MySQL versions mentioned for upgrade path only are for CentOS/RHEL 5.x (where they have added mysql 5.5) and not for 6.x versions of the OS which still uses MySQL 5.1.x.

Either way, upgrading your MySQL should not have an affect on the software - although we won't support the upgrade process since we have always stuck with whatever MySQL version is provided by the OS distribution.

So to summarise, we can upgrade but Nagios wont support it, right?
Not an acceptable solution for Enterprise Level deployment.

Hope Nagios can come up with a better alternative as this will be a common risk issue in enterprise environments.

Thanks

[tmcdonald]

So to summarise, we can upgrade but Nagios wont support it, right?

That is not what was said. Please read carefully (emphasis mine):

although we won't support the upgrade process

You are welcome to upgrade any component you'd like, but we can only support the Nagios side of things. Meaning, we won't remote into your server and compile/configure the latest version of MySQL for you. However, if you upgrade past what we have tested, we cannot guarantee there will not be issues with the new component, and any issues that arise will need to be resolved either by returning to a supported version, or by waiting for it to be worked around on our end.

[rajasegar]

So to summarise, we can upgrade but Nagios wont support it, right?

That is not what was said. Please read carefully (emphasis mine):

although we won't support the upgrade process

You are welcome to upgrade any component you'd like, but we can only support the Nagios side of things. Meaning, we won't remote into your server and compile/configure the latest version of MySQL for you. However, if you upgrade past what we have tested, we cannot guarantee there will not be issues with the new component, and any issues that arise will need to be resolved either by returning to a supported version, or by waiting for it to be worked around on our end.

We need to upgrade because of the risk raised. So Nagios should tell us at the very least the version we should be updating to.
Right now it is left to the end user to figure this out and deal with the issues if any arrises. All this can be avoided if you can tell us what versions you have tested successfully.

[rkennedy]

We simply install what the yum repositories provide, and at this point it's still 5.1.73.

Code: Select all

[root@localhost libexec]# yum install mysql
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.sesp.northwestern.edu
 * extras: bay.uchicago.edu
 * updates: centos.mirrors.wvstateu.edu
base                                                     | 3.7 kB     00:00
extras                                                   | 3.4 kB     00:00
updates                                                  | 3.4 kB     00:00
updates/primary_db                                       | 2.6 MB     00:00
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mysql.x86_64 0:5.1.73-7.el6 will be installed

Without packages, mysql could be installed many different ways. It's rather difficult for us to standardize this in our install, and using repositories is going to be the safest bet in my opinion.

This goes with what @jomann mentioned -

Code: Select all

Clarification on the above post. MySQL versions mentioned for upgrade path only are for CentOS/RHEL 5.x (where they have added mysql 5.5) and not for 6.x versions of the OS which still uses MySQL 5.1.x.

[rajasegar]

We simply install what the yum repositories provide, and at this point it's still 5.1.73.

Code: Select all

[root@localhost libexec]# yum install mysql
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.sesp.northwestern.edu
 * extras: bay.uchicago.edu
 * updates: centos.mirrors.wvstateu.edu
base                                                     | 3.7 kB     00:00
extras                                                   | 3.4 kB     00:00
updates                                                  | 3.4 kB     00:00
updates/primary_db                                       | 2.6 MB     00:00
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package mysql.x86_64 0:5.1.73-7.el6 will be installed

Without packages, mysql could be installed many different ways. It's rather difficult for us to standardize this in our install, and using repositories is going to be the safest bet in my opinion.

This goes with what @jomann mentioned -

Code: Select all

Clarification on the above post. MySQL versions mentioned for upgrade path only are for CentOS/RHEL 5.x (where they have added mysql 5.5) and not for 6.x versions of the OS which still uses MySQL 5.1.x.

I have asked the team to apply for exemption. Lets see how it goes.

[rkennedy]

Sounds good - I'll leave this open - let us know if you have any further questions.