Many Failure Notice During Cpanel Update

[bangjampang]

hello cpanel, i just got email from my server that notice my server got many of failure during the cpanel update with message like below :

An error was detected which prevented updatenow from completing normally.
Please review the enclosed log for further details

----------------------------------------------------------------------------------------------------

[20121002.044604] Detected version '11.32.4.15' from version file.
[20121002.044604] Target version set to '11.32.5.10'
[20121002.044604] Switching to version '11.32.5.10' of updatenow to perform sync.
[20121002.044604] Updating to '11.32.5.10'
[20121002.044604] Syncing themes
[20121002.044604] Starting sync of x3 ...
[20121002.044604] Retrieving /cpanelsync/11.32.5.10/x3/.cpanelsync.bz2
[20121002.044604] Using mirror: 216.12.197.42
[20121002.044605] Retrieving /cpanelsync/11.32.5.10/x3/.locale.help/es/addoncgi/cpaddons.html.bz2
[20121002.044605] Retrieving /cpanelsync/11.32.5.10/x3/addoncgi/oldaddonshandler.html.bz2
[20121002.044606] Retrieving /cpanelsync/11.32.5.10/x3/css/cgi-min.css.bz2
[20121002.044606] Retrieving /cpanelsync/11.32.5.10/x3/css/cgi-min.css.gz
[20121002.044606] Retrieving /cpanelsync/11.32.5.10/x3/css/combined_optimized.css.bz2
[20121002.044606] Retrieving /cpanelsync/11.32.5.10/x3/css/combined_optimized.css.gz


also attach you the scrintshoot



my question is what is this, why this happen, is there any relativity with vulnerability or malware script?

 

[mobcdi]

I have a similar message when my update was triggered for the same upgrade (11.32.4.15 -> 11.32.5.10)
If you check the output do you see a message similar to

Retrieving /cpanelsync/11.32.5.10/cpanel/base/images/awstats/icon/flags/gr.png.bz2
E md5sum mismatch (actual: md5sumOutput) (expected: md5sumOutput) (size: 0)

Its the only thing I've found so far in the output that looks like an error that might cause the update to fail

 

[Toliman]

Happens to me as well.

[20121002.004324] Retrieving /cpanelsync/11.32.5.10/cpanel/base/images/awstats/icon/flags/gr.png.bz2
[20121002.004324] E md5sum mismatch (actual: d41d8cd98f00b204e9800998ecf8427e) (expected: b15bb41e6a85b78e1c44f99de1bce677) (size: 0)

 

[l00ph0le]

Same Here:
[20121002.015435] Retrieving /cpanelsync/11.32.5.10/cpanel/base/images/awstats/icon/flags/gr.png.bz2
[20121002.015435] E md5sum mismatch (actual: d41d8cd98f00b204e9800998ecf8427e) (expected: b15bb41e6a85b78e1c44f99de1bce677) (size: 0)

Happens to me as well.

 

[Infopro]

Has any of you opened a ticket to cPanel?
http://go.cpanel.net/bugs

Please do if you don't mind, thanks!

 

[turbo2ltr]

Same here.

[20121002.004111] Retrieving /cpanelsync/11.32.5.10/cpanel/base/images/awstats/icon/flags/gr.png.bz2
[20121002.004111] E md5sum mismatch (actual: d41d8cd98f00b204e9800998ecf8427e) (expected: b15bb41e6a85b78e1c44f99de1bce677) (size: 0)

 

[mobcdi]

I opened a ticket and cPanel support say they have an internal ticket open. Its not a high priority for me given the update appears to have only minor changes according to the change log available via WHM

 

[bangjampang]

wow im surprise many people have same problems like me

- - - Updated - - -

is there anyone have solved this problems?

 

[mobcdi]

I'm just posting this for information purposes as I haven't tried it myself

cPanel support suggested rerunning upcp as not every user encountered the problem of the md5mismatch and the file that tripped up those that did encounter problems hasn't changed in years i.e. it isn't a new file

 

[Eric]

Howdy,

Please submit a ticket on this. We would like to take a look.

Thanks!

 

[bangjampang]

ticket opened request id is [3246063]

 

[cPanelTristan]

Hello,

The ticket opened (3246063) appeared to show no issues with the update that is now occurring.

Next, the internal case opened on the issue (61544) indicates we couldn't reproduce any md5sum mismatches for that specific file either and that the error doesn't appear to be occurring now any longer.

If anyone else does show the same error, please submit a ticket to us and reference case 61544 in the ticket opened along with this forum thread.

Thanks!