em - there was a message today when I logged into whm under root urging me to update my version as a security issue had been discovered so I click it and it began to update. The server then reboot for changes to take effect and I can get into whm or cpanel (/whm or /cpanel or via there ports) any advice?

I just started fighting with this on one server. Don't know the answer . . . . . yet.

ok - please keep me posted :).

What is this? I didn't see anysuch thing on our 5 boxen, and am not sure what a reboot would do that a restart of the process wouldn't....

Care to enlighten dennis?

Originally posted by thedavid
What is this? I didn't see anysuch thing on our 5 boxen, and am not sure what a reboot would do that a restart of the process wouldn't....

Care to enlighten dennis? Did you update today? :)

http://forums.cpanel.net/search.php?s=&action=showresults&searchid=468290&sortby=lastpost&sortorder=descending

Originally posted by Dennis
Did you update today? :)

http://forums.cpanel.net/search.php?s=&action=showresults&searchid=468290&sortby=lastpost&sortorder=descending

Ohhh I see. Manual updates only on the 'current' version here.. Mighta just escaped it.

Carry on then :D

-David

Right. We have manual updates. But I was looking at WHM, for some reason, and heeded the big red warning to update on one server. :mad:

Ahh I see - gave in to temptation, then ;)

Since it's a problem with binding to ports that are already in use by the webmaild and whatnot, wouldn't this command fix 'er?

'service cpanel stop; killall -9 cpaneld whostmgrd webmaild; service cpanel start;'

Assuming you're running RH, of course...Haven't been following this issue today. Off to check and make sure everything's working.. ;)

I tried that. Didn't work.

Hmm...

Just tempted fate by /scripts/upcp on a test box with current set as the update preference.. Still on this version:

WHM 9.1.0 cPanel 9.1.0-C71
RedHat Enterprise 3 - WHM X v2.1.2

Are you trying edge? If not on current, try downgrading to that (this version was released after the accounting pm was updated) at least till the storm passes.

edge??

:D

Stable.

:P

This seemed to have helped out quite a few people that had problems with this update;


rm -f /usr/local/cpanel/cpanel
/scripts/installgd
/scripts/cleanmd5
/scripts/upcp


Was posted at CPanel at;

http://forums.cpanel.net/showthread.php?s=&threadid=21485

that worked well :).

however cpsrvd has failed (thats it tho) any thoughts?

sup now - thanks for your help everyone.

Originally posted by Watcher_TVI
This seemed to have helped out quite a few people that had problems with this update;


rm -f /usr/local/cpanel/cpanel
/scripts/installgd
/scripts/cleanmd5
/scripts/upcp


Was posted at CPanel at;

http://forums.cpanel.net/showthread.php?s=&threadid=21485


Thank You! This did the trick.

TP

never a dull moment with Cpanel :stickout:

okay, I have a couple servers running slightly different cpanel setups (purposely) thanks to some fun I've had in the past..

here's the issue.

1) NEVER set Cpanel to automatically update itself!
2) ONLY do STABLE or RELEASE updates on production servers, and only after testing it in a non-production environment.

so here is how this problem seems to affect people:

1 - if your running RH 7.3 and using an EDGE version of cpanel (worst affected)
2 - if your running RH 9 and Cpanel 9 Release or Edge (affected)
3 - if your running RH 9 and Cpanel 8 Release (least affected)

to fix case 1 and 2, do the following:

rm -f /usr/local/cpanel/cpanel
/scripts/installgd
/scripts/cleanmd5
/scripts/upcp

to fix case 3, just restart cpanel:

service cpanel restart

these recommendations fixed any problems I noticed.

I had the Cpanel set to automatically update Security and Packages.... NO MORE! I think most of us learned a valuable lesson in not letting CPanel do ANYTHING on it's own.

This last update was forced even if you had your preferences set to manual updates only. The only way you could have avoided this update would have been to CHMOD the upcp to 0

From this thread http://www.webhostingtalk.com/showthread.php?s=&postid=1923766#post1923766 . It seem like cpanel use the exploit to force update the server. It is pretty nifty of them to think of this idea.