I hope someone can help me, I wasn't sure where this message should go. Every day, when I log into my server and run "top", I see that there are 3 instances of up2date running, which are effectively using up all CPU time. I have been able to manually kill each of them without any apparent problems, but figuring out why this happens is the challenge.

Perhaps someone can explain to me the relationship between cPanel and up2date? I know there is a cron job set up that runs /scripts/upcp, which in turn runs up2date. I'm running Redhat Enterprise 3, and I was concerned about the recent mod_ssl exploit that was reported. When I run up2date by itself, I see that certain packages (such as kernel, httpd, php, etc) are excluded from being updated. The mod_ssl fix says it requires some of these excluded packages. If I clear the exclusion list in up2date and run again, it fails. If I let /scripts/upcp run, it *re-inserts* those packages into the exclude list.

How am I supposed to install the mod_ssl fix? Please help...

I believe I answered this in another forum for you?

I am having the exact same problem. Also, attempts to updated Apache through the cPanel control panel fail, while they worked a week or so ago. I have no idea what the problem is nor how to fix it.



I looked through your posts and didn't see any solution to his problem, so if you could repost it, I would greatly appreciate it.

Thanks.

That would have been this thread
http://forums.cpanel.net/showthread.php?t=27055

You are my hero.

I followed everything you said in that other thread and everything seems to be working properly again.

Thanks a lot.

Glad you've got it working

We dont have access to the CPanel forum for some reason - mailed them. Please post the fix here as we are also having a problem updating Cpanel and up2date.

Thanks

My pleasure:

Thanks

Here's an addendum if the problem persists:

Try the following:

1. Issue the following to get the PID's of any processes access the rpm database:
lsof | grep /var/lib/rpm

2. The PID's are in the second column, you need to kill each of the separate ones off:
kill -9 PID

3. Now you need to clean up any lock files:
rm -f /var/lib/rpm/__*

4. Try again. If you get rpm database errors, you may need to:
rpm --rebuilddb

That could take a while. If it seems to be hanging (after 20 minutes or so), then...

5. Reboot the server as a last resort.