Fatal error: Allowed memory size of 8388608 bytes exhausted

[BieDdoS]

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to
allocate 156150 bytes) in
/home/elaborare/www/forum/vbulletin/admin/functions.php on line 507



What's this error??? Is it a Server problem??

[Kaizen]

Sounds like your host is limiting memory usuage.

Email them and see what they say?

[George L]

Re: Fatal error: Allowed memory size of 8388608 bytes exhausted

Originally posted by BieDdoS
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to
allocate 156150 bytes) in
/home/elaborare/www/forum/vbulletin/admin/functions.php on line 507



What's this error??? Is it a Server problem??

you need to increase your php.ini settings for memory allocation to php

what php version you're using

for php 4.x you need to edit php.ini on your server

;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 30  ; Maximum execution time of each script, in seconds
[b]memory_limit = 8M[/b]  ; Maximum amount of memory a script may consume (8MB)

change what's in bold memory_limit = 8M

to something like

memory_limit = 16M

restart apache

if you are on a shared server and not dedicated ask your host to do this..

[BieDdoS]

Thanks Eva
Ciao!!

[George L]

Originally posted by BieDdoS
Thanks Eva
Ciao!!

no probs

so it worked?

[Kaizen]

Originally posted by eva2000
no probs

so it worked?

hehehehehhe - no it didn't.

I am quite pleased i got it half right - I will have to be more specific and detailed in future.

[randychase]

I have been running into this same problem. We upped the php.ini setting to 32megs and that helped for a while. What I found was I had to reboot the server every 30 days or I would start getting that error message and the forums would slow way down.

Then it got worse and I had to reboot every week or so, and we increased the script memory size to 64megs and that helped I think. But in the last few weeks, I have had to reboot the server every 3 days to keep the forums from getting that same memory error and so this morning I increased the memory to 128megs in my php.ini file.

I am running a few forums, but none are *that* popular, mostly 20 or so users or less at any one time. Any guesses as to what is going on with my dedicated server?

Thanks!

[tribedude]

We did optimization enhancements as described in this forum by eva2000 last year and the board was running fine until recently.

I am getting these errors too. The last time was a few weeks ago...

I increased the size to 16 and it was fine. Now it is happening again.

There are a lot of threads about this problem on this site but no answers... So saying the answers are in other threads is wrong because I have read them all on this subject in the vB forum...

Our site has over a million posts on it. I have clamped down on the search frequency to every 30 seconds and that doesn't seem to do anything.

When it was happening, I did a top and looked at all the memory resource allocations for mysqld and there were about a dozen running at 3.9 each. Now, after a reboot of the server the resource allocation for each has gone down to .3 and the same amount are running.

Our server is pretty robust: Dual 1.26 with 2 gigs of ram and a 15krpm scsi scratch disk even..

The board is the only thing running on the server...

What more can we do to stop these memory errors?

[tribedude]

After the reboot an hour ago, in top as I said the memory usage was .3 for each mysqld service... In a half hour it went to .5, now it is at .6... For some reason the mysqlds are getting bigger and it seems if they continue to grow, this will be the source of the memory errors. Can someone help me with this?

CPU0 states: 5.0% user, 1.1% system, 0.0% nice, 93.2% idle
CPU1 states: 4.2% user, 0.1% system, 0.0% nice, 95.1% idle
Mem: 2059536K av, 845880K used, 1213656K free, 4220K shrd, 80540K buff
Swap: 2096440K av, 0K used, 2096440K free 547252K cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
1719 apache 14 0 9396 9396 8016 S 4.7 0.4 0:14 httpd
1586 apache 9 0 10860 10M 8288 S 2.3 0.5 0:12 httpd
2590 apache 9 0 9332 9332 7876 S 1.3 0.4 0:01 httpd
1938 mysql 9 0 12436 12M 1212 S 0.9 0.6 0:20 mysqld
1949 mysql 9 0 12436 12M 1212 S 0.7 0.6 0:32 mysqld
1730 mysql 9 0 12436 12M 1212 S 0.5 0.6 0:50 mysqld
2271 root 10 0 1056 1056 756 R 0.1 0.0 0:10 top
1 root 8 0 508 508 440 S 0.0 0.0 0:06 init
2 root 8 0 0 0 0 SW 0.0 0.0 0:00 keventd
3 root 18 19 0 0 0 SWN 0.0 0.0 0:00 ksoftirqd_CPU0
4 root 19 19 0 0 0 SWN 0.0 0.0 0:00 ksoftirqd_CPU1
5 root 9 0 0 0 0 SW 0.0 0.0 0:00 kswapd
6 root 9 0 0 0 0 SW 0.0 0.0 0:00 kreclaimd
7 root 9 0 0 0 0 SW 0.0 0.0 0:01 bdflush
8 root 9 0 0 0 0 SW 0.0 0.0 0:00 kupdated
9 root -1 -20 0 0 0 SW< 0.0 0.0 0:00 mdrecoveryd
17 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald
130 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald
131 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald
132 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald
133 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald
134 root 9 0 0 0 0 SW 0.0 0.0 0:00 kjournald
731 root 9 0 788 788 648 S 0.0 0.0 0:00 syslogd
736 root 9 0 1136 1136 448 S 0.0 0.0 0:00 klogd
754 rpc 9 0 568 568 484 S 0.0 0.0 0:00 portmap
782 rpcuser 9 0 828 828 708 S 0.0 0.0 0:00 rpc.statd
928 root 9 0 1280 1280 1152 S 0.0 0.0 0:00 sshd
962 root 4 0 996 996 928 S 0.0 0.0 0:00 xinetd
1003 root 8 0 1944 1944 1400 S 0.0 0.0 0:00 sendmail
1022 root 8 0 14208 13M 1820 S 0.0 0.6 0:01 spamd
1040 root 9 0 484 484 416 S 0.0 0.0 0:01 gpm
1063 root 8 0 6536 6536 6072 S 0.0 0.3 0:00 httpd
1089 root 8 0 652 652 564 S 0.0 0.0 0:00 crond
1096 root 9 0 928 928 760 S 0.0 0.0 0:00 safe_mysqld
1130 mysql 9 0 12436 12M 1212 S 0.0 0.6 0:00 mysqld
1172 mysql 9 0 12436 12M 1212 S 0.0 0.6 0:00 mysqld
1173 mysql 9 0 12436 12M 1212 S 0.0 0.6 0:00 mysqld
1194 mysql 9 0 12436 12M 1212 S 0.0 0.6 0:46 mysqld
1201 xfs 9 0 3208 3208 872 S 0.0 0.1 0:00 xfs
1219 mysql 9 0 12436 12M 1212 S 0.0 0.6 0:51 mysqld
1220 mysql 9 0 12436 12M 1212 S 0.0 0.6 1:11 mysqld
1239 daemon 9 0 552 552 480 S 0.0 0.0 0:00 atd
1263 root 9 0 516 516 452 S 0.0 0.0 0:00 rhnsd
1272 root 9 0 3264 3264 2732 S 0.0 0.1 0:00 miniserv.pl
1273 root 9 0 3168 3168 2692 S 0.0 0.1 0:00 miniserv.pl
1276 root 9 0 436 436 372 S 0.0 0.0 0:00 mingetty
1277 root 9 0 436 436 372 S 0.0 0.0 0:00 mingetty
1278 root 9 0 436 436 372 S 0.0 0.0 0:00 mingetty
1279 root 9 0 436 436 372 S 0.0 0.0 0:00 mingetty
1280 root 9 0 436 436 372 S 0.0 0.0 0:00 mingetty
1281 root 9 0 436 436 372 S 0.0 0.0 0:00 mingetty
1329 root 9 0 2008 2008 1652 S 0.0 0.0 0:00 sshd
1330 root 9 0 1300 1300 956 S 0.0 0.0 0:00 bash
1585 apache 9 0 10356 10M 8136 S 0.0 0.5 0:13 httpd
1587 apache 9 0 9544 9544 8112 S 0.0 0.4 0:14 httpd
1588 apache 9 0 9708 9708 8208 S 0.0 0.4 0:14 httpd
1589 apache 9 0 9976 9976 8328 S 0.0 0.4 0:11 httpd
1590 apache 9 0 9948 9948 8188 S 0.0 0.4 0:11 httpd
1591 apache 9 0 9972 9972 8392 S 0.0 0.4 0:12 httpd
1592 apache 9 0 9472 9472 8084 S 0.0 0.4 0:12 httpd
1669 apache 9 0 9364 9364 7804 S 0.0 0.4 0:13 httpd

[Scott MacVicar]

sounds like a memory leak.

Especially if its working fine and slowly gets worse. What version of PHP are you using?

[tribedude]

sounds like a memory leak.

Especially if its working fine and slowly gets worse. What version of PHP are you using?

PHP Version 4.1.2


SystemLinux stripples.devel.redhat.com 2.4.18-11smp #1 SMP Thu Aug 15 06:41:59 EDT 2002 i686 unknownBuild DateSep 26 2002

[tribedude]

% memory is up to .9 now

[Scott MacVicar]

any chance you can upgrade to PHP 4.3.4

There is alot of Memory leaks in previous versions of PHP.

[tribedude]

I will have to ask my tech guy to do it for me. Will that newer version of php work with our existing mysql 3.23.49a? Or is it all inter-related and will we have to upgrade the mysql as well?

[Scott MacVicar]

Its not related but if he's going to upgrade try MySQL 4.0.16 it has many performance increasing features such as the Query Cache.