vb.org Archive - Strange error message that I do not understand

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- vB3 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=111)

- - Strange error message that I do not understand (https://vborg.vbsupport.ru/showthread.php?t=180234)

Strange error message that I do not understand

Hi,

I'm getting this strange error:

Code:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 363321 bytes) in /var/www/html/forum/includes/vba_cmps_include_top.php(526) : eval()'d code on line 343

The rest of the forum works fine

This is the link that generates the error

Any idea what this means?

thanks
remoras

Ask your host to increase the memory limit, or disable the modifications that are causing this problem.

As your forum isnt open to guests, its kinda useless to post a link.

This is typically a mysql issue as a result of not being able to allocate enough ram to execute the query.

If this is a dedicated server, adjust your my.cnf settings and restart mysql.

Quote:

Originally Posted by snakes1100 (Post 1528796)

Sorry, I always forget that some parts of the forum are closed for guests.
Should I contact my host? Or is this something I can do myself?

As i said, if its a dedicated server you can, if its a virtual hosted site, then the host needs to address the issue and resolve it for you.

Typically that error is the fact that mysql tried to allocate more ram than the system has for it to use.

This is not a MySQL error.

ok thanks, I'll mail my host.
cheers

Unfortunately Marco, i would disagree with you, it is a mysql issue and not a memory_limit issue with php.

Then please point me to the place in the MySQL manual where this error is discussed.

(I can always be wrong, but this is not a MySQL error, but a webserver/PHP error).

Sorry Snakes, but you are wrong - that's a PHP memoery error, nothing to do with mysql.

ok, how do I solve it?

Quote:

Originally Posted by Paul M (Post 1528862)

Sorry Snakes, but you are wrong - that's a PHP memoery error, nothing to do with mysql.

Look, I don't want to argu with either of you, but saying that snakes is wrong, is also wrong Paul.

you are BOTH correct in that his issue can be resolved and it can be resolved in two different ways.

Everyone is always quick to resolve it by upping the PHP memory limit, but this isn't the only way to resolve the issue. It can also be resolved by upping the memory limit for mysql itself without upping the PHP memory limit. This is often done for for systems with little memory..

here is an example of a my.cnf for upping the memory limit for MySQL without having to up the PHP limit ...

Code:

# Example mysql config file for small systems.

#

# This is for a system with little memory (<= 64M) where MySQL is only used

# from time to time and it's important that the mysqld deamon

# doesn't use much resources.

#

# You can copy this file to

# /etc/my.cnf to set global options,

# mysql-data-dir/my.cnf to set server-specific options (in this

# installation this directory is /usr/local/mysql/var) or

# ~/.my.cnf to set user-specific options.

#

# One can in this file use all long options that the program supports.

# If you want to know which options a program support, run the program

# with --help option.



# The following options will be passed to all MySQL clients

[client]

#password        = your_password

port                = 3306

socket                = /tmp/mysql.sock



# Here follows entries for some specific programs



# The MySQL server

[mysqld]

port                = 3306

socket                = /tmp/mysql.sock

skip-locking

set-variable        = key_buffer=128K

set-variable        = max_allowed_packet=1M

set-variable        = thread_stack=64K

set-variable        = table_cache=4

set-variable        = sort_buffer=64K

set-variable        = net_buffer_length=2K

server-id        = 1



# Uncomment the following if you want to log updates

#log-bin



# Uncomment the following if you are NOT using BDB tables

#skip-bdb



# Uncomment the following if you are using Innobase tables

#innodb_data_file_path = ibdata1:100M

#innodb_data_home_dir = /usr/local/mysql/var/

#innodb_log_group_home_dir = /usr/local/mysql/var/

#innodb_log_arch_dir = /usr/local/mysql/var/

#set-variable = innodb_mirrored_log_groups=1

#set-variable = innodb_log_files_in_group=3

#set-variable = innodb_log_file_size=5M

#set-variable = innodb_log_buffer_size=8M

#innodb_flush_log_at_trx_commit=1

#innodb_log_archive=0

#set-variable = innodb_buffer_pool_size=16M

#set-variable = innodb_additional_mem_pool_size=2M

#set-variable = innodb_file_io_threads=4

#set-variable = innodb_lock_wait_timeout=50



[mysqldump]

quick

set-variable        = max_allowed_packet=16M



[mysql]

no-auto-rehash

# Remove the next comment character if you are not familiar with SQL

#safe-updates



[isamchk]

set-variable        = key_buffer=8M

set-variable        = sort_buffer=8M



[myisamchk]

set-variable        = key_buffer=8M

set-variable        = sort_buffer=8M

@bobster

MySQL can also give memory errors, but the error message looks different.

The error as posted in the first post is not a MySQL error!

My name is Floris and I approve of post #2. ;)

Quote:

Originally Posted by Marco van Herwaarden (Post 1528879)

@bobster

MySQL can also give memory errors, but the error message looks different.

The error as posted in the first post is not a MySQL error!

I agree... this isn't an ERROR its an ISSUE and its an issue that can be resolved in two different ways. Snakes never once used the word error, he simply pointed out that this is a known issue with MySQL and can be resolved without upping the PHP memory limit :)

It can be resolved by upping the php memory limit and it can also be resolved by upping the MySQL Memory limit.

I've had dealt with this exact issue and have resolved it and test it both ways and both work just fine.

I just wanted to chime in to say that its not right to say someone is wrong when they did bring up something that is in fact correct. The "Popular" answer is to up the PHP Mem limit, that doesn't mean its the "correct" way or "only" way..

ok, I'll mail our host and show them this post.
Hopefully they can fix this.

What if they refuse to increase the memory?

It is not correct. You can not resolve the issue/error as posted in the first post of this thread by changing your MySQL configuration.

Quote:

Fatal error: Allowed memory size of

This is an error mesage, not an "issue" message (never even heard of that one before).

I am getting confused :|

--------------- Added [DATE]1211548774[/DATE] at [TIME]1211548774[/TIME] ---------------

Something strange happened. I opened the forum for public so you guys could see the error but the error does not appear when you're a guest. I logged back in and the error came back.

Forum is open for public, see here:

http://www.pokerclub.be/forum/showthread.php?t=7904

And here is the error again, maybe it changed.

Code:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 364196 bytes) in /var/www/html/forum/includes/vba_cmps_include_top.php(526) : eval()'d code on line 343

Quote:

Originally Posted by Marco van Herwaarden (Post 1528893)

It is not correct. You can not resolve the issue/error as posted in the first post of this thread by changing your MySQL configuration.

This is an error mesage, not an "issue" message (never even heard of that one before).

Actually Marco, I just tested it (AGAIN) on one of my Dev servers.. Lowered the PHP Memory Limit so that when I was in the ACP and tried to update a style, It error'd out with the same exact error as above, then upped the MySQL Memory Limit and guess what?, it worked. Upping the MySQL Memory limit WILL resolve the issue. You can keep on telling me that I am wrong tho.

@bobster, this is the reason i didnt reply back to marco or pauls post, let it go, no need to argue with either of those two, they think they are right and nothing will change their minds.

I see this a lot when im optimizing servers, especially on a vps, no matter how high you set php's memory_limit, mysql is just using to much of the memory, then its back to readjusting mysql memory use.

Well your free to believe what you like. Im glad you dont support any of my servers. :)

As a silent observer of this thread, I must say it's some very interesting reading - I'm not placing any 'right' or 'wrong' on anyone, it's just interesting information.

Quote:

Originally Posted by Paul M (Post 1529087)

Well your free to believe what you like. Im glad you dont support any of my servers. :)

Im glad as well. :)

Phrase Groups Available:

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01676 seconds Memory Usage 1,791KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (3)bbcode_code_printable (6)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)post_thanks_navbar_search (1)printthread (24)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: