MYSQL database grew up too big?

**oddnews** · 06-24-2007, 10:19 AM

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 41689207 bytes) in /home/public_html/libs/ez_sql_core.php on line 370

I get this error. This is so frustrating because I can't even upgrade to 9.6 I get error as well:
When I upgrade from 9.5 to 9.6 I see this:
This will upgrade the database for Pligg Beta v9.0 and above to the latest version.

Note: this is just a database upgrade, you still need to upload the new files.

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 41689207 bytes) in /home/public_html/libs/ez_sql_core.php on line 370

I'm about to switch to joomla ! Please convince me otherwise,

**AshDigg** · 06-24-2007, 10:57 AM

Try deleting the contents of the cache folder and see if that fixes the problem.

**argh2xxx** · 06-24-2007, 05:22 PM

Is it possible though that mysql file can grow too big? Then Pligg probably is for serious player, because virtual host will not do it? In truth do you need dedicated server just for mysql only?

I mean I do see my mysql growing bigger fast!

I always thought if Pligg has a function/feature where admin can flush old links and stories from mysql, clean up mysql from getting clogged up. That can be nice. Though this is an option if admin wants to use, otherwise admin can just leave it alone, and let mysql grows as big as the admin wants. In this way old links and stories can be save!

**jessy** · 10-22-2007, 05:04 PM

some solution for this problem, i have the same problem, i'm using pligg 9.5 !

atal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 33043343 bytes) in /mounted/public/www/libs/ez_sql_core.php on line 370

Thanks for the help

**ChuckRoast** · 10-22-2007, 05:45 PM

Originally Posted by jessy

some solution for this problem, i have the same problem, i'm using pligg 9.5 !

atal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 33043343 bytes) in /mounted/public/www/libs/ez_sql_core.php on line 370

Thanks for the help

Try this post http://forums.pligg.com/bug-report/7...exhausted.html

**jessy** · 10-23-2007, 05:00 AM

it's resolved, i clean the template_c directory and forget the cache dir.

Thanks.

**wwwOLIONDORcom** · 10-24-2007, 11:03 AM

Originally Posted by AshDigg

Try deleting the contents of the cache folder and see if that fixes the problem.

Hello, my error was this one:

Fatal error: Out of memory (allocated 524288) (tried to allocate 37497571 bytes) in /libs/ez_sql_core.php on line 374

I deleted the content of CACHE folder and it works again, but what can I do to avoid having this problem next time again?

I'm using the latest version, 9.8.2

Thanks.

**jessy** · 10-24-2007, 11:29 AM

nice question :applaud:

may be creating a cron script to delete the content of the directory CACHE every 24 hours !

**omy** · 10-24-2007, 02:40 PM

Maybe you should take a look in the database with tools like database ants or stuff like that

**jessy** · 10-24-2007, 02:47 PM

As i see with my website, when the MySQL server falls down, we get this error, so we have to empty the CACHE's directory, i don't think we get this error because the database grow up.