grayloon

Well-Known Member
Oct 31, 2007
121
4
68
Evansville, IN
cPanel Access Level
Root Administrator
Twitter
I've upgraded four different cPanel servers in the last 24 hours from PHP 5.3.23 to 5.3.24. Each of them stalled on phar. I had to kill the EasyApache processes and start the builds again. Some servers are running CentOS 5 - others are running CentOS 6. The only thing that changed between the last working build and the failed build was the PHP version. The last output in the build window was:
Code:
Generating phar.php
Generating phar.phar
 

KurtN.

Well-Known Member
Jan 29, 2013
95
1
83
cPanel Access Level
Root Administrator
Hi grayloon,

I would encourage you to contact support. However, what is the relevant logging output from your build located in the /usr/local/cpanel/logs/easy/apache directory?
 

grayloon

Well-Known Member
Oct 31, 2007
121
4
68
Evansville, IN
cPanel Access Level
Root Administrator
Twitter
Here's what appeared in the log. It looks like the build continued after the output window froze...

Code:
Generating phar.php
Generating phar.phar
PEAR package PHP_Archive not installed: generated phar will require PHP's phar extension be enabled.
directorygraphiterator.inc
pharcommand.inc
clicommand.inc
directorytreeiterator.inc
invertedregexiterator.inc
phar.inc

Build complete.
Don't forget to run 'make test'.

        -- End step 'make php for apache and cli' --
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
Hello :)

We do have an internal case open (#68845) related to EasyApache hanging when generating the "phar.phar" file. It's only been reproduced with Web Host Manager using Chrome with Windows 8. Feel free to reply here or open a ticket if you are experiencing this issue on another environment or when using the command line.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
I just tried upgrading PHP from 5.3.24 to 5.3.25, and it hung on Phar again. I'm using Chrome with MacOS X Mountain Lion. I ran the build a second time, and it worked.
Feel free to go ahead and open a support ticket if you experience this issue again so we can try reproducing it.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
Hi Dear cPanel team,

I'm currently having the same problem. ticket is raised - 4379881

Regards
It looks like you closed this ticket before we were able to investigate the issue.
 

stingerman

Member
Nov 11, 2011
8
0
51
cPanel Access Level
Root Administrator
Hello :)

We do have an internal case open (#68845) related to EasyApache hanging when generating the "phar.phar" file. It's only been reproduced with Web Host Manager using Chrome with Windows 8. Feel free to reply here or open a ticket if you are experiencing this issue on another environment or when using the command line.

Thank you.
Same exact problem. Is there a fix?
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
Same exact problem. Is there a fix?
There is no update to report on this case. Feel free to go ahead and open a support ticket if you experience this issue so we can try reproducing it. Remember to post the ticket number here so we can update this thread with the outcome.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
I am having this same issue updating Apache from 2.2.x to 2.4.x running on Windows 7 x64 Pro, Chrome 32.0.1700.107 m.
To update, the issue was not reproducible on a test environment, and additional EasyApache builds are not hanging. The customer is planning to force kill the process that is hanging from the initial EasyApache build that failed.

Thank you.
 

asep

Registered
Jan 16, 2014
1
0
1
cPanel Access Level
Root Administrator
Hi,

I have same problem. Stuck on phar
Code:
--2014-02-16 15:43:30--  http://pear.php.net/install-pear-nozlib.phar]Source of ', htmlspecialchars($_GET['viewsource']), '
Resolving pear.php.net... 5.77.39.20
Connecting to pear.php.net|5.77.39.20|:80... connected.
no progress...
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,268
463
Could you open a support ticket and reference internal case 68845? We can investigate and tag that internal case with your ticket number if it's determined to be related.

Thank you.