Thanks for the reply... I forgot to update this thread after finally figuring things out. Indeed you were correct, we had to remove /etc/cron.d/mrtg and restart mrtg. However, that did not stop all the other errors.
I wound up upgrading to MRTG 2.17, which was a project in itself that I will outline below. That STILL didn't eliminate all the errors, but some Google-foo led me to a website that outlined some minor code changes to a couple MRTG perl files, and that finally made MRTG happy.
Upgrading to MRTG 2.17 didn't work by just simply doing a "yum update mrtg", even after removing the * after perl from /etc/yum.conf. I wound up getting it via RepoForge, as follows:
- Make a backup copy of /etc/mrtg/mrtg.cfg
- Set up the RepoForge repository to get the more up-to-date package.
Instructions for installing it are at Using RepoForge . Once it is installed, edit /etc/yum.repos.d/rpmforge.repo, and change any line that says "enabled = 1" to "enabled = 0" to make sure that the new repositories will never be used accidentally in situations where the regular repositories should be used.
- Remove the existing mrtg-libs package (this is necessary before installing the new mrtg package, because the libraries are built into the 2.17 package rather than being a separate package). "rpm -e mrtg-libs --nodeps" will do this.
- Install mrtg 2.17 with the following command "yum --enablerepo=rpmforge-extras update mrtg"
- Restore the backup of your mrtg.cfg file (if needed)
After upgrading MRTG, I still needed to do some search/replace code changes as outlined at:
https://odesk.by/archives/1169
The "before" code didn't always match what we had, but I still went with the "after" code and it resolved the errors.
Lastly, I had to remove /etc/cron.d/mrtg and restart mrtg with "service mrtg restart" No errors!
- Scott
