Warning after migrating from local machine to server

.
Yes, that is quite odd.
BUT, "MySQL server has gone away" means the connection has been lost with the MySQL server.
This is usually because the MySQL server times-out while running a query.
The time-out time period is set in the MySQL server configuration.

This can also be affected by the MySQL server load.
So the time-out issue can be intermittent.

If this is your own server instance then you should be able to change the settings (I would assume).

.

I can change the settings but the time-out is already set at 60 seconds, not sure what else to change!
Here is as it's set right now:


#
# Base Container
#

[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
max_heap_table_size = 8M
skip-name-resolve

#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
bind-address = 0.0.0.0

# For compatibility
old_passwords = 1

back_log=20
max_connections=60

# due to mysql internally considering connections from 'user@host1' as a separate user from 'user@host2', max_user_connections is largely irrelevant in a clustered situation
max_user_connections=16
max_connect_errors=100000


key_buffer_size=24M
max_heap_table_size=4M
read_buffer_size=128K
read_rnd_buffer_size=128K
sort_buffer_size=256K
table_cache=1024
thread_cache_size=4
tmp_table_size=4M
join_buffer_size=4M
wait_timeout=60
thread_concurrency=4
innodb_file_per_table

max_allowed_packet = 16M
thread_stack = 128K

# query cache
query_cache_limit = 1048576
query_cache_size = 12M
query_cache_type = 1

# slow query log
log-slow-queries = /var/log/mysql/mysql-slow.log
long_query_time = 1

# memory trimming
#skip-bdb

[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
no-auto-rehash

[isamchk]
key_buffer = 16M

[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

.
wait_timeout=60 is low for a general purpose website.
You (and other users) may see some timeouts while working on things.

Try wait_timeout=120 or more.

There are also a couple PHP settings which directly affect the MySQL database connection.
Check these on your server (try these settings):
default_socket_timeout=120
mysql.connect_timeout=120

If you still have problems increase these three again (240, 300).

Also a number of your other MySQL settings seem low.
A poorly tuned MySQL server will run slower, take longer on queries, and thus potentially time-out more often.
How much memory do you have available on the MySQL server?

.

Hi ken,
I tried changing the php.ini and the mySql settings but no change at all.

I have 125megs of ram for mySql at the moment which, although it's a large site, seems OK for now as I only launched a few days ago so am not busy.

Everything alse runs perfectly in the back end and the 'items' folder was fine on my local host which seemed to flag up either a conflict or perhaps something not copying over to the new server properly (a few image links had been changed to lower case on transfer which I had to change).

One thing that might be important is that even though I get these errors, the 'items' load below them.

Also when I try to change the amount of items per page to 5 I can, but when I leave the page then return it's 50 again.

Thanks to all for helping me out with this, I'd like to get this sorted before installing flexiaccess.

Here is the my.cnf from the xampp install I was running the site on in localhost, as you can see it is MUCH more conservative than the config file for the present install on-line and everything worked fine:

# 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 daemon
# doesn't use much resources.
#
# You can copy this file to
# /xampp/mysql/bin/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /xampp/mysql/data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
# password = your_password
port = 3306
socket = "/xampp/mysql/mysql.sock"

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3306
socket= "/xampp/mysql/mysql.sock"
basedir="/xampp/mysql"
tmpdir="/xampp/tmp"
datadir="/xampp/mysql/data"
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M



# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
# commented in by lampp security
#skip-networking
skip-federated

# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin


# Point the following paths to different dedicated disks
#tmpdir = "/xampp/tmp"
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir = "/xampp/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "/xampp/mysql/data"
#innodb_log_arch_dir = "/xampp/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

I tried combining some of the more conservative settings on the xampp my.cfg with the server cfg plus a few other settings thinking that it might be a case of over-using resources, but still doesn't work.

I smell a conflict here but having un-installed most components/modules/templates I'm getting a bit frustrated.

I might just get drunk and fiddle with the settings whilst listening to some good jazz, that might work!