Help - Search - Members - Calendar
Full Version: Out Of Memory Error
Movable Type Community Forum > Other Product Discussion > Bugs and Odd Behavior
jblayloc
I am running 4.23 on a Unix-based shared web hosting service (aplus.net's Business web hosting plan). I have several blogs running off the same installation, two of which I use frequently. In total, there are 2,500 entries and about 775 comments. I have been getting, with increasing frequency, an out of memory error when publishing entries off the larger blog (2,063 entries) and now cannot publish any more entries in that blog. The index templates publish okay, but publishing an entry gives me:

QUOTE
Out of memory during "large" request for 4198400 bytes, total sbrk() is 59566080 bytes


Oddly, this does not happen with the other blogs on the same installation. I can publish entries in all the other blogs without issue.

Having searched these forums and the Intarweb, I've found a few similar problems, and most advice points to the server/hosting company. And that may be true here, though I wonder why it's affecting just the one blog. I do not speak "server," so I am not sure what to ask my hosting company to do (I either do not have "root access" or wouldn't know what to do with it if I did.) or how to fix it.

In other threads about this type of error, helpful folks asked for the results of mt-check.cgi. Here they are (I've bolded ImageMagick as that seemed to be a solution to some of the problems.):

QUOTE
System Information

* Movable Type version: 4.23-en

* Current working directory: /home/u3/jblayloc/cgi-bin
* MT home directory: ./
* Operating system: freebsd
* Perl version: 5.8.8
* Perl include path:
plugins/feeds-app-lite/lib
plugins/OnThisDay/lib
plugins/WXRImporter/lib
plugins/WidgetManager/lib
plugins/TypePadAntiSpam/lib
plugins/Textile/lib
plugins/StyleCatcher/lib
plugins/spamlookup/lib
plugins/MultiBlog/lib
addons/Community.pack/lib
addons/Commercial.pack/lib
extlib
extlib
lib
/usr/local/lib/perl5/5.8.8/BSDPAN
/usr/local/lib/perl5/site_perl/5.8.8/mach
/usr/local/lib/perl5/site_perl/5.8.8
/usr/local/lib/perl5/site_perl
/usr/local/lib/perl5/5.8.8/mach
/usr/local/lib/perl5/5.8.8
.
* Web server: Apache/1.3.39 (Unix)
* (Probably) Running under cgiwrap or suexec

Checking for Required Modules
CGI::Cookie

Your server has CGI::Cookie installed (version 1.20).
File::Spec (version >= 0.8)

Your server has File::Spec installed (version 3.25).
Image::Size

Your server has Image::Size installed (version 2.93).
CGI

Your server has CGI installed (version 2.80).
Checking for Data Storage Modules

Some of the following modules are required by the various data storage options in Movable Type. In order run the system, your server needs to have DBI and at least one of the other modules installed.
DBI (version >= 1.21)

Your server has DBI installed (version 1.59).

DBD::mysql

Your server has DBD::mysql installed (version 4.005).

DBD::SQLite

Your server does not have DBD::SQLite installed, or DBD::SQLite requires another module that is not installed. The DBD::SQLite database driver is required to use SQLite Database. Please consult the installation instructions for help in installing DBD::SQLite.

DBD:: Pg (version >= 1.32)

Either your server does not have DBD:: Pg installed, the version that is installed is too old, or DBD:: Pg requires another module that is not installed. The DBD:: Pg database driver is required to use PostgreSQL Database. Please consult the installation instructions for help in installing DBD:: Pg.

DBD::SQLite2

Your server has DBD::SQLite2 installed (version 0.33).

Checking for Optional Modules

The following modules are optional. If your server does not have these modules installed, you only need to install them if you require the functionality that the module provides.
Scalar::Util

Your server has Scalar::Util installed (version 1.19).
Crypt::DSA

Your server has Crypt::DSA installed (version 0.14).
XML::SAX

Your server has XML::SAX installed (version 0.13).
Archive::Zip

Your server has Archive::Zip installed (version 1.20).
Storable

Your server has Storable installed (version 2.16).
SOAP::Lite (version >= 0.5)

Your server has SOAP::Lite installed (version 0.52).
List::Util

Your server has List::Util installed (version 1.19).
HTML::Entities

Your server has HTML::Entities installed (version 1.35).
Text::Balanced

Your server has Text::Balanced installed (version 1.95).
Digest::MD5

Your server has Digest::MD5 installed (version 2.36).
GD

Your server has GD installed (version 2.35).
Archive::Tar

Your server has Archive::Tar installed (version 1.34).
Safe

Your server has Safe installed (version 2.12).
IO::Uncompress::Gunzip

Your server has IO::Uncompress::Gunzip installed (version 2.006).
Digest::SHA1

Your server has Digest::SHA1 installed (version 2.11).
IO::Compress::Gzip

Your server has IO::Compress::Gzip installed (version 2.006).
Image::Magick

Your server has Image::Magick installed (version 6.3.3).

XML::Atom

Your server has XML::Atom installed (version 0.25).
LWP::UserAgent

Your server has LWP::UserAgent installed (version 2.001).
MIME::Base64

Your server has MIME::Base64 installed (version 3.07).
Mail::Sendmail

Your server does not have Mail::Sendmail installed, or Mail::Sendmail requires another module that is not installed. This module is required for sending mail via SMTP Server. Please consult the installation instructions for help in installing Mail::Sendmail.
File::Temp

Your server has File::Temp installed (version 0.12).
Movable Type System Check Successful

You're ready to go! Your server has all of the required modules installed; you do not need to perform any additional module installations. Continue with the installation instructions.


The publishing templates are standard stuff. Here's the blog that's having problems, and here's the one that's publishing just fine.

Any advice for this non-technical guy? Thanks in advance, jb
danwolfgang
Simply, publishing a bigger blog takes more resources. It sounds like your larger blog might be hitting the limit of the server resources available to you.

Some suggestions: use the publishing queue, template module caching, simplify complex template structures, remove slow plugins, etc. A more lean installation may improve things or completely eliminate problems, depending upon what your install looks like now.
jblayloc
QUOTE (danwolfgang @ Jan 11 2009, 06:09 PM) *
Simply, publishing a bigger blog takes more resources. It sounds like your larger blog might be hitting the limit of the server resources available to you.

Some suggestions: use the publishing queue, template module caching, simplify complex template structures, remove slow plugins, etc. A more lean installation may improve things or completely eliminate problems, depending upon what your install looks like now.


Thanks Dan. I've turned on caching for the template modules. That alone has made no difference. I am working on a new individual archive template design that should be leaner on initial build. There aren't many active plug-ins.

For whatever it's worth, the number of bytes associated with the sbrk() is growing, more or less each time I try to publish an entry in that blog:

QUOTE
Out of memory during "large" request for 4198400 bytes, total sbrk() is 61014016 bytes


The server folks (aplus.net) have a trouble ticket going.
jblayloc
So I took the category entry count and monthly entry count out of the sidebar, and limited the category archive template to the last 36 entries, and rebuilt. It took only about 6 1/2 minutes to rebuild the 2,000+ entry blog. The other good news is, I can now publish entries again.

The bad news is, every category, date-based archive, search result, and tag search result all show the same entry, repeated over and over again, in the exact number of entries that should be shown. It's the most recent entry in the blog. Obviously one of my edits did something unwanted. I have no idea what. I'm having to take the blog offline until I can rewrite the templates.
danwolfgang
It sounds like you may have enabled caching on an Entry Detail module. You need to pick and choose which modules and widgets get cached because some--like Entry Detail, Entry Summary and Comments--don't make sense to cache.
jblayloc
QUOTE (danwolfgang @ Jan 13 2009, 01:16 PM) *
It sounds like you may have enabled caching on an Entry Detail module. You need to pick and choose which modules and widgets get cached because some--like Entry Detail, Entry Summary and Comments--don't make sense to cache.


Thanks for the advice, Dan. I didn't have time to go through the module caching item-by-item, so I shut it off at the blog preference screen and republished. Though it took over 36 miuntes -- clearly uncached content comes at a performance price -- the archives, search results, and tagged entries results have been fully restored.

I also got a succinct email from the tech support at aplus.net telling me the script error has been fixed. No details were provided.

I made changes to my last entry and published it successfully, though it took awhile. Looks like I either need to cache content correctly or redesign the templates to use php includes instead of template modules.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.