|
Mark Gilbert
|
Sunday 25 April 2004 9:04:39 am
Here is the server information page:
System information
eZ publish
Site:
localhost
Version
3.3-3 (3.3)
SVN revision
5019
Extensions
PHP
Version
4.3.6
Extensions
xslt, xml, tokenizer, standard, session, posix, pcre, overload, odbc, mysql, ldap, imap, gd, ftp, domxml, ctype, zlib, openssl, apache, java
Safe mode is off.
Basedir restriction is on and set to /home/web/f/fbenew/.
Global variable registration is off.
File uploading is enabled.
Maximum size of post data (text and files) is 8M.
Script memory limit is .
Maximum execution time is 30 seconds.
PHP Accelerator There is no known PHP accelerator active.
|
|
Vidar Langseid
|
Monday 26 April 2004 6:57:43 am
Try this:
- Enable memory_limit in PHP
eZ publish needs more than 8Mb (which is default), but should do fine with about 20Mb. Enabling memory_limit will stop php processess that starts "run away"
- Decrease MaxClients in httpd.conf. You run out of memory. It is better to queue incomming requests than to start swapping.
- Try a PHP accelerator. Apache's memory footprint will increase because of this, but eZ publish will be less CPU intesive so you will be able to server more requests.
|
|
Mark Gilbert
|
Monday 26 April 2004 7:12:31 am
Vidar Thank you for your reply. I noticed that my ISP turned the safe mode back on. They turned it off when I asked themn to for eZ Publish. But with the problems over the weekend it looks like they decided to turn it back on. I know that at one time "Safe Mode" did not work with eZ Publish. I also noticed that thier used to be a contribution that had a work around for those ISP's that require safe mode to be on. Does "Dafe Mode" still need to be turned off with version 3.3-3 and later? Are thier plans to build a permanent work around or is this going to be a permanent requirement for eZ Publish?
|