Warning after migrating from local machine to server

Hi all,
I built a website on my local machine using the most recent, 1.5.3c stable (r354), copy of flexicontent.
All worked well using xampp with php 5.29 until I migrated to a web server (Media Temple grid server, php 5.2.14 and mySql 5.1.26) and got this error whenever I go into the 'items' tab of flexicontent:

Error Loading ModulesMySQL server has gone away SQL=SELECT id, title, module, position, content, showtitle, control, params FROM jos_modules AS m LEFT JOIN jos_modules_menu AS mm ON mm.moduleid = m.id WHERE m.published = 1 AND m.access <= 2 AND m.client_id = 1 ORDER BY position, ordering

plus another 14 lines of errors underneath like this one:

Warning: array_diff() [function.array-diff]: Argument #1 is not an array in /blah blahyippetyblah.com/html/administrator/components/com_flexicontent/models/items.php on line 182

The site seems to be working fine other than this.

I should have enough mySql power as, although I am on a grid server, I have a mySql container to run the database in.

Any ideas?

Cheers,

Dom

BTW Have cleared all caches (didn't have then on whilst building anyhow) and deleted a few flexicontent templates to see if it was a load issue and that didn't work!

with basique template does it work ? (just for test)
you do your migration with joomlapack or with ftp transfert ?

Hi Micker,

micker wrote: with basique template does it work ? (just for test)

Yes, it's the same, I just tried it

micker wrote: you do your migration with joomlapack or with ftp transfert ?

With Akeeba (joomlapack) using .jpa compression and kickstart.

.
"MySQL server has gone away" means the MySQL server has timed-out while running that query.

You should speak to your host about the MySQL configuration settings.

.

kenmcd wrote: .
"MySQL server has gone away" means the MySQL server has timed-out while running that query.

You should speak to your host about the MySQL configuration settings.
.

The page just loaded in 2 seconds with that error, that's pretty quick for a time-out!

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