Nagios XI initial Install - RPM Forge repo

[krobertson71]

One of our Unix/Linux admins stated that they had to disable a repo during patching yesterday on our test Nagios XI Server.

--exclude=php*,ruby-json,rrdtool --disablerepo=rpmforge

1) I believe too many updates were pulled and cause a space issue in the partition they use to pull updates.. Waiting for verification on that.


UPDATE:

1) Here is the actual issue provided by our Unix team regarding the rpmforge repository on the Nagios XI server.

These are not Red Hat supported packages. Frequently the use of these packages create dependencies problems with packages provided by Red Hat, which is what happened yesterday. A lot of these packages are put on rpmforge because they either are newer versions or compiled with different options than what is provided by Red Hat.

2) They "do not like" having the RPM Forge repo on their servers.

Does this repo need to be there after install? I know that when Nagios XI updates are released I see things like RRD tool will be updated to the latest version, same for other sub-components.

This is a licensed Red Hate Enterprise el6 server.

Any help here would be appreciated.

[cmerchant]

You could disable and/or remove the rpmforge repo, but I would not recommend it. There are a few packages that are installed from rpmforge for the XI install and are required.

You can verify which rpm packages are installed by issuing the following:

Code: Select all

yum list installed | grep @epel

With that said, the XI upgrade script will possibly enable it again when run.

[krobertson71]

The problem is not at the time of install, it is after it is up and running.

When we were patching the server last night, this repo was trying to install updates to and was trying to break dependencies to other packages on the Red Hat Enterprise server.

After the install is complete do you see a problem disabling this repo?

[tmcdonald]

After the install is complete do you see a problem disabling this repo?

Post-install I do not see a problem, but as soon as you need to update, or install a component/plugin/wizard that needs a new package, they will of course need to be enabled.