1 impaire Dec 28, 2005 20:36
3 impaire Dec 29, 2005 01:49
This is what I was thinking about, some kind of memory limitations/restrictions by my provider.
But it changes also from time to time (related to server load?).
I've quickly installed AppServer 2.4.3 and it works localy with a similar environment:
Date: Thu, 29 Dec 2005 00:40:43 GMT
Server: Apache/1.3.33 (Win32) PHP/4.3.10
X-Powered-By: PHP/4.3.10
I'll drop a mail to support and will let you know if I get more informations.
Thanks!
4 impaire Dec 29, 2005 02:04
Something happened...
Fatal error: Allowed memory size of 6291456 bytes exhausted (tried to allocate 239 bytes) in _db.class.php on line 514
Fatal error: Allowed memory size of 6291456 bytes exhausted (tried to allocate 107 bytes) in _db.class.php on line 514
/admin/antispam.php?action=poll
Yesterday I used the same feature which worked but that was on another box.
So, to be clarified with my provider.
Locally, where it seems to work, I've checked the limit, 8M:
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
max_execution_time = 30 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)
Regards
5 blueyed Dec 29, 2005 06:07
impaire, hte antispam update requires quite a few memory. (AFAIK it's the page which requires the most).
Ask your host to set memory_limit to 8M (with (fast-)cgi you cannot override it in .htaccess)).
I'm not sure, but perhaps you can forde it in /conf/config.php by using
ini_set( 'memory_limit', '8M' );
6 impaire Dec 29, 2005 13:08
This could be the solution but I won't have access to this.
I think my provider will have to figure out what to do.
He should have two domains/boxes working the same and stable way, don't he? ;)
I'll push the latest antispam list in using any another way.
Thanks for your inputs!
7 impaire Dec 29, 2005 18:26
The answer are:
- memory limit fixed to 6 megs
- this morning other customers complained and they rebooted the box.
did I kill it, I just changes skin scripts? :D
Server logs would be quite important to solve this.
Anyway, I'm running the demo site also with mod_fastcgi, but on Apache2. I've not seen such issues. It may be related to exhausted PHP memory_limit for example, but the default of 8MB should be enough for b2evo.