cpanel upgrade hangs at 20% progress

newbies

Active Member
Jul 9, 2004
31
1
156
When I tried to upgrade cpanel in WHM, it progresses to 20% and then stops there without further porgress. I have two servers which have the same problem.

Is this a known issue?
 

rikgarner

Well-Known Member
Mar 31, 2006
75
1
158
/dev/null
Hi,
Unfortunately we need a few more details to be able to help you with this:

1. Which distro are your servers running
2. Which release tree are you currently running
3. Are you trying to move from one release tree to another
4. What is the last line before it hangs?

You could also try doing it from an SSH session: /scripts/upcp

Rich
 

javitox

Member
Dec 17, 2005
5
0
151
hi

hello ,

Do you give some time to process the update ??? you only need give some time more to process the update , it normaly take 20 - 30 minuts , but if your server have a lot of account it could be take 1 hour

Bye
 

newbies

Active Member
Jul 9, 2004
31
1
156
Thank you guys for reply.

My version is as follows:
WHM 10.8.0 cPanel 10.9.0-R50
RedHat Enterprise 3 i686 - WHM X v3.1.0

Before it hangs, the last line of message disappears too fast to be seen.

I only have 5-10 accounts on both server. It hangs for over 20 mins.

I did an update in shell by running upcp, it went smoothly.

Thanks again.
 

SageBrian

Well-Known Member
Jun 1, 2002
416
2
318
NY/CT (US)
cPanel Access Level
Root Administrator
javitox said:
hello ,

Do you give some time to process the update ??? you only need give some time more to process the update , it normaly take 20 - 30 minuts , but if your server have a lot of account it could be take 1 hour

Bye
20-30min?
Why would it take that long? Is there something special in the latestestGreatest?

I've never had an update take that long, with over 100 accounts.

I'm on C43 now, going to C48
 

maggy

Active Member
Jun 9, 2004
25
0
151
for me it shows a blank screen when it reached 20%, i think thats what o.p. means
if you monitor top in ssh you can see when it finishes because the load drops
in any case yes this is a bug