Fatal Error

[Muzzy]

Hi All.

I have just upgraded from 0.13 to 1.0 beta 4 and seem to be getting some problems.

Since upgrading I cannot view my site, but keep getting this "Site down for mainenance".
If I try to login to the admin panel I get this message:
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 2554 bytes) in /home/sites/19sixtyone.co.uk/public_html/cms/modules/Album/lang/en_US.php on line 143

Any help would be useful.
Mike.

[Piratos]

You should wait until 1.0 is stable.

1.0 needs 12mb ram 16mb is  recommended, if you have 8 mb and have no chance to set it to 12 or 16 mb you can say bye bye to this cms.

[Muzzy]

You should wait until 1.0 is stable.

1.0 needs 12mb ram 16mb is  recommended, if you have 8 mb and have no chance to set it to 12 or 16 mb you can say bye bye to this cms.

Your reply is not very helpful, indeed it is rather off-putting.
Perhaps you could be so kind as to offer a suggestion such as what I should ask my host for with regard to what the 12 or 16mb is used for.

It would also be a good idea if the CMSMS team made people aware of such restrictions, just to save any heartache. It also makes CMSMS a restricitve package that obviously will not be available for all to use as their splurge says...

With regard to your comment about a stable release, I have used both 0.12 and 0.13 and I figured I could be of use by testing 1.0. I was trying to do this as a test-site on my server, before I ran into the problem.

If this is how CMSMS is going to be (for the elit only), then perhaps I should look elsewhere for a CMS package.

Regards.
Mike.

[tsw]

You can ask your hosting company to set php memory_limit higher.

1.0beta installers have checks for mem limits and it clearly tells how much memory one has and what is the required minimum (8mb which I think is the default for stock php install) and recommended (16m).

Ted is working on new hierarchy manager which should lover memory requirements and have some speed improvements.

hope this helps

[Elijah Lofgren]

You should wait until 1.0 is stable.

1.0 needs 12mb ram 16mb is  recommended, if you have 8 mb and have no chance to set it to 12 or 16 mb you can say bye bye to this cms.

Perhaps you could be so kind as to offer a suggestion such as what I should ask my host for with regard to what the 12 or 16mb is used for.

Sorry about your problem.

One thing you can do to try to get CMSMS working is to disable some of your modules. Each module you install makes CMSMS take additional memory. You could rename some of module folders in the "modules" directory to something else and that will keep them from loading. (For example rename ModuleManager to ModuleManager_disabled, nuSoap to nuSoap_disabled, Album to Album_disabled). That should help CMSMS stop running out of memory.

You may just have to use less modules unless you can persuade your web host to increase the memory limit for PHP.

Hope this helps,

Elijah

[Muzzy]

Thanks TSW and Elijah.

I have unlimited hosting, so I will contact them to see if they can make any adjustments.

Mike.

[Muzzy]

Hi Guys.

I have just received this reply from my hosting company:

++++++++++++++++
PHP has a built-in limit on the amount of memory it will allocate. If that limit is reached, the process will exit with this error message. This is usually the result of the PHP script trying to load a large file, such as an image, into memory all at once. While it is better if you can arrange for the script not to do such things, it is also possible to increase the memory limit some to avoid this problem. To do that, edit the php.ini file with your PHP sciprts (create it if it does not exist) and add the following line:

memory_limit=16M
You should replace the '16' with whatever value is appropriate. The default is 8M (8 megabytes, the 8388608 bytes from the error message).
++++++++++++++++

Could anyone tell me where this file is, I have searched everywhere. If I can't find it I need to create one. In which case where should I put this file. I guess I call it php.ini and create it with notepad in plain text?

Regards.
Mike.

[Elijah Lofgren]

Hi Guys.

I have just received this reply from my hosting company:

++++++++++++++++
PHP has a built-in limit on the amount of memory it will allocate. If that limit is reached, the process will exit with this error message. This is usually the result of the PHP script trying to load a large file, such as an image, into memory all at once. While it is better if you can arrange for the script not to do such things, it is also possible to increase the memory limit some to avoid this problem. To do that, edit the php.ini file with your PHP sciprts (create it if it does not exist) and add the following line:

memory_limit=16M
You should replace the '16' with whatever value is appropriate. The default is 8M (8 megabytes, the 8388608 bytes from the error message).
++++++++++++++++

Could anyone tell me where this file is, I have searched everywhere. If I can't find it I need to create one. In which case where should I put this file. I guess I call it php.ini and create it with notepad in plain text?

Regards.
Mike.

I think you'll have to ask your hosting company where to place the php.ini file. You could try looking in something like "etc/php.ini" or "/etc/php5/apache2/php.ini" to see if it is there.

There is also a way to up the memory limit with a .htaccess file (if allowed).
See the following posts:
http://forum.cmsmadesimple.org/index.ph ... l#msg33274
http://forum.cmsmadesimple.org/index.ph ... l#msg32720

Hope this helps,

Elijah

[Piratos]

Make a small script like this



copy this und your server and run it.

You can see  in this entry Configuration File (php.ini) Path  the path of your php.ini

[Piratos]

This is what a fresh installed 1b4 needs on the visitor side:


Generated in 0.322976 seconds by CMS Made Simple (not cached) using 20 SQL queries and 6071944 bytes of memory

And this is if i make an uninstall of

cmsmailer
news
nusoap
search

Generated in 0.213658 seconds by CMS Made Simple (not cached) using 15 SQL queries and 4448456 bytes of memory

But if you have a php with the function memory_get_peak_usage you can measure sometimes much more memory needed ( + 40  + 80%)  , if that happens the cms does not work at this moment if you have only 8 mb.

[calguy1000]

nuSOAP and CMSMailer now use lazy loading so their memory requirements should be much smaller in the  next beta.

[Piratos]

Here some values of needed memory with 1b4 - all modules installed - on the admin side:

Thememamanager open  6,23 MB
News open - 6,24 MB
Events open - 6,29 MB

and the Maximum is if you open the Modulemanager (no one needs this module)  7,84 MB  - it works not proper if you have 8 MB restriction.

[calguy1000]

In the latest beta considerable effort has again been made to improve performance and minimize memory footprint.  we've done the best we can do to a) provide functionality, and b) minimize memory usage, but there is a limit to all things and we are rapidly reaching a point where we are putting in alot of effort to reap minimal memory usage gains.

Of course we're always open to ideas to minimize memory footprints that dont' severly impact on functionality.  If you can find any dramatic improvements, please contribute.  I know there are probably alot of places in the code where we could be using references, and are not.  We can't find all of them.  That's why we have a user community like this, to help us.

Theme Manager and other modules have been optimized further and the memory footprint will be reduced in the next beta, which will help but will not eliminate the problem.

One cannot expect to "have their cake and eat it too".  With the considerable functionality that CMS has in it's core, and the fact that the amount of functionality never decreases, it just increases, there is a limit to the amount we can do to keep the minimum memory requirements under 8Mb.  To that end, more changes will be made,  but possibly not in the 1.0 series to devide the package up further, thus reducing the footprint.

As far as Module Manager..... This will become the preferred method in 1.0 for downloading and installing modules.  It eliminates the problems numerous people have with installing modules fia the .tar.gz method (bad ftp clients, permissions problems, general lack of knowledge as to how things work).  From our responses in channel, and via personal email, and messages I would guess that the module manager feature will be used by 90% of the people using CMS. 

Please, if you're going to make criticisms, please try to find ways to help with the problem as well.  You have provided some good solutions in the past, and all of these issues have been addressed in one way or another.  That is the way I think we would all like to see you contribute.  You have considerable skills, just cannot communicate that well without irritating the other users in the community.    Again, we value your input, just not your tone and demeanor.

[calguy1000]

The lazy loading (which is in use throughout CMS) means that the memory footprint is different on one request than it may be on another.  and yes, it is possible that depending upon which modules are loaded, which tags are used on a page, and the amount of data in the database, and/or in the page that yes, you will run out of memory if using 8Mb. 

nuSOAP and CMSMailer now use lazy loading so their memory requirements should be much smaller in the  next beta.

[calguy1000]

This is interesting, and it goes to show that not all php installs are created equally.  Ted has a considerably smaller default memory footprint on his new test server:  Here's a copy of some of his latest profiling efforts:

Debug display of 'Loading module CMSMailer':(0.086287) -- 3294296
Debug display of 'Loading module FCKeditorX':(0.091215) -- 3481120
Debug display of 'Loading module MenuManager':(0.097232) -- 3677304
Debug display of 'Loading module ModuleManager':(0.102333) -- 3796112
Debug display of 'Loading module News':(0.107141) -- 3967144
Debug display of 'Loading module nuSOAP':(0.115516) -- 4239776
Debug display of 'Loading module Search':(0.117086) -- 4291784
Debug display of 'Loading module ThemeManager':(0.123781) -- 4519528
Debug display of 'End of include':(0.129699) -- 4737256
Debug: (0.130557) -- 4700864

Here some values of needed memory with 1b4 - all modules installed - on the admin side:

Thememamanager open  6,23 MB
News open - 6,24 MB
Events open - 6,29 MB

and the Maximum is if you open the Modulemanager (no one needs this module)  7,84 MB  - it works not proper if you have 8 MB restriction.