Strange error message that I do not understand

[remoras]

ok, how do I solve it?

[Marco van Herwaarden]

See post #2

[bobster65]

Originally Posted by Paul M

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 ...

# 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

[Marco van Herwaarden]

@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!

[Floris]

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

[bobster65]

Originally Posted by Marco van Herwaarden

@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..

[remoras]

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

What if they refuse to increase the memory?

[Marco van Herwaarden]

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.

Fatal error: Allowed memory size of

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

[remoras]

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.

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

[bobster65]

Originally Posted by Marco van Herwaarden

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.