Memory issues

benbaylis

Hi,

I have two different installs of epesi on one virtual server.

Install One - "TC" plays nice. The second "EC" always runs out of memory.

All I am trying to do is browse page by page (20 per page) of 300 "EC" contacts. Yet "TC" will let me page through 900+ contacts easily.

Initally the server was configured with 1gb of ram and php memory limit of 128mb

[Wed Jun 27 17:38:47 2012] [error] [client ...] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8379784 bytes) in /.../epesi/include/error.php on line 182, referer: http://.../epesi/index.php
[Wed Jun 27 17:38:47 2012] [error] [client ...] PHP Warning: Invalid callback DBSession::close, class 'DBSession' not found in Unknown on line 0, referer: http://.../epesi/index.php

next I tried with a memory size of 2gb and php memory limit of 256mb

[Wed Jun 27 17:40:38 2012] [error] [client ...] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 16761225 bytes) in /.../epesi/include/error.php on line 103, referer: http://.../epesi/index.php
[Wed Jun 27 17:40:38 2012] [error] [client ...] PHP Warning: Invalid callback DBSession::close, class 'DBSession' not found in Unknown on line 0, referer: http://.../epesi/index.php

So I finally try a php memory limit of 512mb I just get:
[Wed Jun 27 17:48:09 2012] [error] [client ...] PHP Warning: Invalid callback DBSession::close, class 'DBSession' not found in Unknown on line 0, referer: http://.../epesi/index.php

Both installs are running the same version "EPESI version 1.3 rev9190"

The server is a 1and1 dynamic virtual cloud server with a CentOS 5.5 install. How memory should i be allocating to php/the server?

ethnar

Hello and welcome to the forums,

The memory is not really the issue here. 128M is sufficient for even the most most demanding modules, even 64M should be enough to run EPESI.

The real problem is in the session handler. We've had reports earlier about this kind of error and it's strictly linked with various php accelerators.
One thing to try is to disable the accelerator and see if that resolve the problem.
But to really nail the problem, try editing the include/session.php file, fine the code

if(extension_loaded('apc') || extension_loaded('eaccelerator') || extension_loaded('xcache')) //fix for class DBSession not found

    register_shutdown_function('session_write_close');

and replace it with simply

    register_shutdown_function('session_write_close');

Can you please tell us what accelerator you're using and if the register_shutdown_function change resolves the problem?

Kind regards,
Arek

benbaylis

The register_shutdown_function change did not make any difference.

I disabled the apc extension which changed the error logged into:

[Thu Jun 28 13:10:55 2012] [error] [client ...] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 7751755 bytes) in /.../epesi/libs/adodb/drivers/adodb-mysql.inc.php on line 140, referer: http://.../epesi/index.php

jasiek

It seems that the problem is within your server configuration - you pointed our yourself that both instances are running in 1and1 cloud virtual server environment. What are differences in setup parameters for both servers? Can you run phpinfo on both and compare?
You can access phpinfo in http://yourepesiinstallation/admin tools.

Search on Google for
http://tinyurl.com/7tok4nj (1and1 virtual cloud server out of memory php)
returned for example this post:
http://wordpress.org/support/topic/fata ... d-30408704

See the path to your php.ini in phpinfo and see where the configuration is read from. Try to change settings in there.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge