ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

"Fatal error: Allowed memory size" on imgsizer plugin after move to new server

June 22, 2012 5:19pm

Subscribe [1]
  • #1 / Jun 22, 2012 5:19pm

    aleklisefski

    24 posts

    Hello Community!

    URL for this problem is here: http://weddingbands.co.nz.s140887.gridserver.com/
    Running EE v2.1.3

    I am in the process of moving a site from one server to another. The new server is a MediaTemple grid-server. I have successfully moved all of the files, imported the database and changed file permissions where necessary. I had to manually set some URLs and server paths in config.php, but am able to access the control panel on the new server. I changed all other URLs and paths using the Deploy Helper module.

    However, when I try to view the site, I’m getting the following error:

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 10368 bytes) in /nfs/c09/h04/mnt/140887/domains/weddingbands.co.nz/html/admin/expressionengine/third_party/imgsizer/pi.imgsizer.php on line 463

    What doesn’t make sense to me is that the path referenced here is not correct. The new full server path is “/home/140887/domains/weddingbands.co.nz/html” I have double-checked that all paths were changed in the EE control panel. However, this error originates from a file at “/nfs/c09/h04/mnt/140887/domains/weddingbands.co.nz/html/” which does not exist on this server. I have gone so far as to search the database via phpMyAdmin for “/nfs/c09/h04/mnt/140887/domains/weddingbands.co.nz/html/” and it doesn’t appear anywhere in the database anymore. So when this error refers to that server path, I have no idea where that is coming from?

    Ignoring the fact the server path makes no sense, and thinking it might actually be a memory issue, I tried adjusting the memory allocated to the plugin in the plugin file itself using info at the bottom of this thread: http://devot-ee.com/add-ons/support/image-sizer/viewthread/2628#12422 - this had no effect, so I returned it to how it was originally.

    Any ideas on how this error is even possible? Where this old server path is coming from? Here is the pertinent part of my config file for reference. I added a few lines specifying the new URL and server path for site URL and themes directory that were needed in order to login in once I moved the site to the MT server.

    /*
    |--------------------------------------------------------------------------
    | ExpressionEngine Config Items
    |--------------------------------------------------------------------------
    |
    | The following items are for use with ExpressionEngine.  The rest of
    | the config items are for use with CodeIgniter.
    |
    */
    
    $config['app_version'] = '213';
    $config['install_lock'] = "";
    $config['license_number'] = "6354-9615-3137-8540";
    $config['debug'] = "1";
    $config['cp_url'] = "http://weddingbands.co.nz.s140887.gridserver.com/admin/index.php";
    $config['doc_url'] = "http://ellislab.com/expressionengine/user-guide/";
    $config['site_url'] = "http://weddingbands.co.nz.s140887.gridserver.com";
    $config['tmpl_file_basepath'] = "/home/140887/domains/weddingbands.co.nz/html/admin/expressionengine/templates/";
    $config['theme_folder_url'] = "http://weddingbands.co.nz.s140887.gridserver.com/themes/";
    $config['theme_folder_path'] = "/home/140887/domains/weddingbands.co.nz/html/themes/";
    $config['is_system_on'] = "y";
    $config['site_label'] = 'Wedding Bands';
    $config['cookie_prefix'] = '';
    
    $config['allow_extensions'] = "y";
    
    // END EE config items
  • #2 / Jun 23, 2012 8:05am

    Rob Allen

    3105 posts

    Imgsizer can be a bit memory hungry, especially when processing larger images. The solution is to increase the amount of available memory on your server, 64mb is usually more than ample.

    Alternatively switch to CEImage which seems a lot less memory hungry than Imgsizer.

  • #3 / Jun 25, 2012 4:11pm

    Dan Decker

    7338 posts

    Hi aleklisefski,

    As Rob notes, you need to request a memory increase from your host.

    64MB is a good place to start, but 128 would be groovy.

    Cheers,

  • #4 / Jun 25, 2012 4:18pm

    aleklisefski

    24 posts

    Thanks Guys. I’ll give that a try and see if it solves it.

  • #5 / Jun 28, 2012 12:38pm

    Dan Decker

    7338 posts

    Hi aleklisefski,

    Let us know if there is anything else we can do to help.

    Cheers,

  • #6 / Jun 28, 2012 12:51pm

    aleklisefski

    24 posts

    Thanks Guys,

    This solved it. You can close this thread.

  • #7 / Jun 29, 2012 5:47pm

    Dan Decker

    7338 posts

    Hi aleklisefski,

    Fantastic!

    If you need anything else, just let us know.

    Cheers!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases