Error compiling easyapache

[Who is it]

I am currently testing CPanel 11 from the install OVH, I encounter a problem with EasyApache.
If I use WHM
-> Service Configuration
-> Configure PHP and Suexec
I then selected "To take advantage of new features thesis, click here to upgrade your Apache installation with EasyApache 3." it nothing happens, I landed on a white screen. I do not disassemble, I cast a glance at the doc, is launching an SSH session and then the command:

/ Scripts / easyapache 

Of course, I try to locate the missing file as announced loadCpConf.pm but in vain. can anyone already encountered this problem? Please help.
Thanks in advance.

[MindSpace]

It is not possible to disable it because the log file of the is placed at the time of compilation. You should recompile manually because easyapache always will define the fine grading (see the / usr / local / cpanel / logs / easy / apache /) and grep for "suexec_log" and you will see were it is defined. If you want to compile it manually just go to the dir of easyapache left in / home and you can get the source after it has been connected. A simpler solution is just the echo cron> notation every few minutes.

[Zecho]

If you want compile Apache with additional php modules which are not implemented in Easyapache type:
~# touch /var/cpanel/easy/apache/rawopts/all_php5
edit your file
~# nano /var/cpanel/easy/apache/rawopts/all_php5
and add the modules
–enable-module1
–enable-module2

check and reply.

[opaper]

Check the steps:

* Apache Update
* Check / Repair a Perl Script
* Install a Perl Module
* Install a RPM
* Module Installers
* Rebuild RPM Database
* Software Update Server
* Update System Software

[Reegan]

You need to turn off register_globals. register_globals will inject your scripts with all sorts of variables, such as an HTML form variables. Link to the fact that PHP does not require variable initialization means writing insecure code is that much simpler.
register_globals = We
Replace with:
register_globals = Off

[absolute55]

The biggest problem with PHP is that the cPanel servers operate as "nobody" (nobody). When defining the permissions of a PHP script to 777, which means it can be read, written and performed a pro, or that the file belongs to anyone. So if someone in the same server to create a script to find files with the permission of 777, that person can inject whatever you want in this case, committing to the user account that has the "attack .

[Anirvinya]

The phpsuexec PHP is running so that the permissions of 777 are not allowed. There are some points phpsuexec cons, but its use is recommended on servers and security of all. The PHP Safe Mode does not prevent a user commits the files of another user. This is where the phpsuexec enter, preventing a user in bad faith in order to read and write files from other users.