A note to Zoom users that use the PHP or CGI version of Zoom on servers that run Apache.
Several users have reported a problem where they do a search and get no results. In some cases the search form is still displayed at the top of the page, in other cases you get a completely blank page.
After investigation it seems that some shared hosting companies are severly limiting the amount of RAM and CPU available to PHP and CGI scripts.
They can do this by setting the "RLimitMEM" & "RLimitCPU" directives in the Apache configuration for the server. Setting these values will cause Apache to kill any script after it uses more than a certain amount of RAM or CPU time.
These values are normally set in the Apache httpd.conf file. (but can also appear in the srm.conf, access.conf and virtual host files)
See,
http://www.apacheref.com/ref/http_core/RLimitMEM.html
http://www.apacheref.com/ref/http_core/RLimitCPU.html
The timeout setting is also worth looking at.
http://www.apacheref.com/ref/http_core/Timeout.html
The solution is to get you hosting company to set reasonable limits for these values. Of course they might not like this becuase it means you are going to be using more of their CPU time and RAM.
The larger your index files in Zoom, the higher these limits will need to be. Example limits for a medium sized site might be,
RLimitMEM 32097152 32097152 #32 Meg of RAM
RLimitCPU 20 60 #60 seconds of CPU time
But before you start sending your hosting company nasty E-Mails check everthing else is correct.
- Check the the indexing process was successful
- Check that all files are on the server
- Check that you can run other small PHP scripts.
Note that if you have this problem, then there will be no error message of any sort, but you will see the search form. This is becuase the script was suddenly terminated. If you see an error message then these settings are probably not the cause of your problem.
--------
David
Wrensoft
Update: Oct 2005: If you are able to confirm with your hosting company that CPU run time is the problem and you are using PHP, then consider switching to the CGI option which will use less CPU time and give faster searching.
Several users have reported a problem where they do a search and get no results. In some cases the search form is still displayed at the top of the page, in other cases you get a completely blank page.
After investigation it seems that some shared hosting companies are severly limiting the amount of RAM and CPU available to PHP and CGI scripts.
They can do this by setting the "RLimitMEM" & "RLimitCPU" directives in the Apache configuration for the server. Setting these values will cause Apache to kill any script after it uses more than a certain amount of RAM or CPU time.
These values are normally set in the Apache httpd.conf file. (but can also appear in the srm.conf, access.conf and virtual host files)
See,
http://www.apacheref.com/ref/http_core/RLimitMEM.html
http://www.apacheref.com/ref/http_core/RLimitCPU.html
The timeout setting is also worth looking at.
http://www.apacheref.com/ref/http_core/Timeout.html
The solution is to get you hosting company to set reasonable limits for these values. Of course they might not like this becuase it means you are going to be using more of their CPU time and RAM.
The larger your index files in Zoom, the higher these limits will need to be. Example limits for a medium sized site might be,
RLimitMEM 32097152 32097152 #32 Meg of RAM
RLimitCPU 20 60 #60 seconds of CPU time
But before you start sending your hosting company nasty E-Mails check everthing else is correct.
- Check the the indexing process was successful
- Check that all files are on the server
- Check that you can run other small PHP scripts.
Note that if you have this problem, then there will be no error message of any sort, but you will see the search form. This is becuase the script was suddenly terminated. If you see an error message then these settings are probably not the cause of your problem.
--------
David
Wrensoft
Update: Oct 2005: If you are able to confirm with your hosting company that CPU run time is the problem and you are using PHP, then consider switching to the CGI option which will use less CPU time and give faster searching.
Comment