Tuesday 13 April 2004 6:05:33 am

There are some issues with Apache 2. But there are some people using it. We however will continue with apache 1.x for the time being.

Reading
http://ez.no/ez_publish/documentation/configuration/troubleshooting/ez_publish_3_and_apache_2
http://uk.php.net/install.apache2
http://ez.no/community/forum/developer/ez_what_is_ripping_our_resources/re_ez_what_is_ripping_our_resources__6

I hope this helps you make the right decision for your site

-- tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

Wednesday 28 April 2004 4:08:42 pm

This is what our sysadmin says on the issue (we have been using apache 2 that comes with RHEL for a couple of months without trouble)

"
....
Completely depends on the Multi Processing Module (MPM) in use.

There are several MPMs available: the ones closely associated with linux are "prefork"
and "worker". "prefork" is the standard Redhat config and the one we are using. It makes apache effectively work like the 1.3 series.

The newer MPM, worker, is the one causing potential problems.

Good discussion started here with linked articles.

http://apache.slashdot.org/article.pl?sid=04/03/23/0237252&mode=thread&tid=148&tid=185
MPM docs here http://httpd.apache.org/docs-2.0/mpm.html
"

So the bottom line is that if apache is compiled with the "prefork" MPM then apache2 will be OK.

Hope this helps to clear the air.

Cheers
Bruce http://www.designit.com.au/

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Thursday 29 April 2004 4:44:15 pm

Hi Derick

"Even in prefork MPM I would (as PHP developer) say that it is NOT ready for production." Can you please elaborate on this and explain why?

My understanding is that
1) the RPM packages what come with RHEL have apache2 compiled with the prefork MPM which makes apache2 work like apache1 and bypasses the issues with non-thread safe modules.
2) The issue is not apache2 + php but apache2 + php + MPM + 3rd party php libraries - when using the prefork MPM this is not an issue.

Our reason for going with apache2 is not for any new features but to enable us to have stock RedHat machine (official RH RPMS) that are covered under a support agreement (as the initial posted asked about)

Cheers
Bruce http://www.designit.com.au/

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Friday 19 May 2006 1:29:32 pm

Dredging up an old discussion here, but I'm in the same situation. I want to use redhat supplied packages, however, the php packages do not appear to include the CLI binary. Any suggestions to remedy this?

RHES 4 Update 3
relevant apache and php packages:
httpd-2.0.52-22.ent
php-4.3.9-3.12
php-domxml-4.3.9-3.12
php-gd-4.3.9-3.12
php-mbstring-4.3.9-3.12
php-mysql-4.3.9-3.12
php-ncurses-4.3.9-3.12
php-odbc-4.3.9-3.12
php-pear-4.3.9-3.12
php-xmlrpc-4.3.9-3.12

Automation Technologies, Inc.
http://www.ati4it.com

Thursday 25 May 2006 12:18:29 pm

We are using he following config:

2 "app" servers configured stock that EzPublish 3.6.0 runs on:

RedHat ES4 Update 3
PHP 4.3.9 (apache2handler/CGI)
Apache 2.0.52 (ezpublish running in virtual host for security)
TurkMMCache (ok, this is not stock, but you can't count a php cache)

1 "database" server running Redhat ES4 Update 3 (same versions of Apache and PHP as above):

MySQL - EzPublish database using InnoDB
LDAP (used for user authentication and data exchange with another proprietary system)

Servers are load-balanced using Webmux dedicated load-balancer (3 seperate virtual farms: front-end website, admin/backend, ad server). Anything that doesn't get stored in the database gets rsynced every 10 minutes..

InnoDB use requires a lot of tweaking of my.cnf file to work with EzPublish on a Redhat ES4 system. We also had to do some changes to php.ini to compensate for long execution times and high memory loads.

So to answer your question, EzPublish runs just fine with Apache 2 (prefork) on a stock RedHat ES4 system. We are not using a CLI version of PHP. So despite what many argue, we have real-world experience that proves that using the apache2handler/CGI works just as well as the CLI version. Our system can handle 125,000 unique visitors a day.

I think that proves that you really can't always just go with the theoretical "don't do this because ... will not work with ...."

Stick with the stock RedHat ES4 installation of Apache and PHP and spend your time tweaking the php and MySql config files. That's a bigger issue than Apache 2 and PHP CGI versus CLI.

The only problem you may have is that you can't upgrade to EzPublish 3.8 because it requires PHP 4.4. Redhat ES4 Update 3 stops at 4.3.9 which is only compatible with EzPublish 3.6.x and nothing higher. I think this will be a big issue for many of us that use Redhat since RedHat is skipping 4.4 and moving to PHP 5 which no version of EzPublish supports (at least not yet).

EzPublish 4, where are you?

--Will Collins
http://insidehighered.com