Lost connection to MySQL server / MySQL server has gone away

saccade · 2010-01-09 16:30:01

Hi
I wish a good new year to everyone!

On a new host I have problems with textpattern 4.2.0:

Installation worked (fresh 4.2.0 install),
creating articles also is ok,
but now when accessing articles on the write tab I get lots of error messages:

Warning: Lost connection to MySQL server during query select ID from v2_textpattern as textpattern where Posted < from_unixtime(1262822945) order by Posted desc limit 1 in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away select ID from v2_textpattern as textpattern where Posted > from_unixtime(1262822945) order by Posted asc limit 1 in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away select privs from v2_txp_users as txp_users where name = 'saccade' in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85

Warning: MySQL server has gone away SELECT custom_1,custom_2 FROM `v2_textpattern` WHERE `ID`='4' in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away SELECT `value` FROM `v2_custom_fields` WHERE `name` = 'custom_1_set' ORDER BY id ASC in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away SELECT `value` FROM `v2_custom_fields` WHERE `name` = 'custom_2_set' ORDER BY id ASC in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85

Warning: MySQL server has gone away select name from v2_txp_form as txp_form where type = 'article' and name != 'default' order by name in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85

Other tabs work (e.g. images and files)

On the public side I had “database unavailable” for a number of times.

I already searched the forum, but spam blacklist isn’t set, it’s empty.

Here my Diagnosis:

Textpattern-Version: 4.2.0 (r3275)
Letzte Aktualisierung: 2009-12-14 16:05:53/2010-01-07 00:30:27
Document Root: /srv/www/vhosts/ebw-rosenheim.de/httpdocs
$path_to_site: /srv/www/vhosts/ebw-rosenheim.de/httpdocs
Textpattern-Pfad: /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern
Schema der URLs: section_id_title
open_basedir: /srv/www/vhosts/ebw-rosenheim.de/httpdocs:/tmp
upload_tmp_dir: /tmp
Temporäres Verzeichnis: /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/tmp
Seiten-URL: ebw-rosenheim.de
PHP-Version: 5.2.6
GD-Graphikbibliothek: bundled (2.0.34 compatible); Unterstützte Grafikformate: GIF, JPG, PNG.
Server TZ: Europe/Berlin
Lokale Serverzeit: 2010-01-08 12:41:44
Sommerzeit: 0
Sommer-/Winterzeit automatisch umstellen?: 1
Zeitzone: Europe/Berlin (3600)
MySQL: 5.0.45
Regionale Einstellungen: de_DE.UTF-8
Server: Apache/2.2.4 (Linux/SUSE)
Apache-Version: Apache/2.2.4 (Linux/SUSE)
PHP Server API: apache2handler
RFC-2616-Header: 
Betriebssystem des Servers: Linux 2.6.27.9rootserver-20081216a
Aktive Plugins: zem_contact_reborn-4.0.3.20, pap_contact_cleaner-0.1, zem_contact_lang-de-4.0.3.6, yab_shop_core-0.8.0, yab_shop_3rd_party-0.7.0, smd_calendar-0.42c, yab_shop_admin-0.8.0, glz_custom_fields-1.2.2, rss_admin_db_manager-4.3m
Admin-Oberfläche: classic 4.2.0

Inhalt der .htaccess-Datei: 
------------------------
#DirectoryIndex index.php index.html

#Options +FollowSymLinks
#Options -Indexes

<IfModule mod_rewrite.c>
	RewriteEngine On
	#RewriteBase /relative/web/path/

	RewriteCond %{REQUEST_FILENAME} -f [OR]
	RewriteCond %{REQUEST_FILENAME} -d
	RewriteRule ^(.+) - [PT,L]

	RewriteCond %{REQUEST_URI} !=/favicon.ico
	RewriteRule ^(.*) index.php

	RewriteCond %{HTTP:Authorization}  !^$
	RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization}]
</IfModule>

#php_value register_globals 0

------------------------

And here another error message in Debug-Mode:

Warning: Lost connection to MySQL server during query select ID from v2_textpattern as textpattern where Posted < from_unixtime(1262822945) order by Posted desc limit 1 textpattern/include/txp_article.php:959 safe_field() in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away select ID from v2_textpattern as textpattern where Posted > from_unixtime(1262822945) order by Posted asc limit 1 textpattern/include/txp_article.php:959 safe_field() in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away select privs from v2_txp_users as txp_users where name = 'saccade' textpattern/lib/txplib_head.php:19 safe_field() in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85

Warning: MySQL server has gone away SELECT custom_1,custom_2 FROM `v2_textpattern` WHERE `ID`='4' textpattern/lib/txplib_misc.php(594) : eval()'d code:285 getRow() in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away SELECT `value` FROM `v2_custom_fields` WHERE `name` = 'custom_1_set' ORDER BY id ASC textpattern/lib/txplib_db.php:318 getRows() in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85 Warning: MySQL server has gone away SELECT `value` FROM `v2_custom_fields` WHERE `name` = 'custom_2_set' ORDER BY id ASC textpattern/lib/txplib_db.php:318 getRows() in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85

My host provider sent me this log:

----------------------- example 1 ---------------------

100108 08:33:39  mysqld restarted
100108  8:33:39  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100108  8:33:39  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 20449561.
InnoDB: Doing recovery: scanned up to log sequence number 0 20449561
100108  8:33:40  InnoDB: Started; log sequence number 0 20449561
100108  8:33:40 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  SUSE MySQL RPM
100108  9:03:11 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=16777216
read_buffer_size=258048
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x21ce740
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x44ca7fe0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x21ce740 failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x2288940 = select *,
				ID as thisid,
				unix_timestamp(Posted) as uPosted,
				unix_timestamp(Expires) as uExpires,
				unix_timestamp(LastMod) as uLastMod from v2_textpattern as textpattern where Status=4 and Posted <= now() and Section != 'about' and Section != 'seitenstruktur' and Section != 'search'  order by Posted desc limit 5
thd->thread_id=27
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0

----------------------- example 2 ---------------------

100108 11:33:20  mysqld restarted
100108 11:33:20  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
100108 11:33:20  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 20449621.
InnoDB: Doing recovery: scanned up to log sequence number 0 20449621
100108 11:33:20  InnoDB: Started; log sequence number 0 20449621
100108 11:33:20 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  SUSE MySQL RPM
100108 11:53:11 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=16777216
read_buffer_size=258048
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x21ce740
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x41bcefe0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x21ce740 failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x22e1e20 = select ID from v2_textpattern as textpattern where Posted < from_unixtime(1262822945) order by Posted desc limit 1
thd->thread_id=50
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0

Thanks for any hint!

Edit The problem has been the same with a 4.0.8 install I tried for solving.
And it is identical with all plugins deactivated.
Database isn’t huge: 4 articles so far. 1 new section.
I’ll provide a screenshot ~~in a few minutes~~ here.

Last edited by saccade (2010-01-09 17:15:55)

saccade · 2010-01-09 17:27:56

Sometimes there is a change between error messages, maybe this helps tracking down what’s happening:

Warning: mysql_query(): Unable to save result set in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 79 Warning: Unknown error select ID from v2_textpattern as textpattern where Posted < from_unixtime(1262223626) order by Posted desc limit 1 in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85

the same in debug-mode:

Warning: mysql_query(): Unable to save result set in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 79 Warning: Unknown error select ID from v2_textpattern as textpattern where Posted < from_unixtime(1262223851) order by Posted desc limit 1 textpattern/include/txp_article.php:959 safe_field() in /srv/www/vhosts/ebw-rosenheim.de/httpdocs/textpattern/lib/txplib_db.php on line 85

colak · 2010-01-09 19:08:40

Hi Michael,

No expert here but:

What are your diagnostics like?
Would your tables need any repairing?

saccade · 2010-01-09 19:34:36

Hi Yiannis,

Diagnostics are ok.
And tables too.

Even the public side is ok so far (but with only one article). Even in debug mode.
Also: Every admin side tab seems to be ok save the Write one when opening an existing article.

But I can’t continue work in a normal way because category and section fields cannot be chosen when editing.

colak · 2010-01-09 19:49:34

Hi michael,

there is one phrase you have to check with your host: This error can also be caused by malfunctioning hardware.

saccade · 2010-01-09 22:18:36

Hi Yiannis,

thank you, I’ll do so.
But he’s been very sure that textpattern is to blame, so I want to be sure it isn’t. :)

I’ve done a lot of installs on different machines – never something like that happened.

els · 2010-01-10 00:22:58

Michael, have you seen the FAQ?

saccade · 2010-01-10 20:15:25

Els,
I’ve seen it. I repaired the tables, but no change. I installed in new tables, no change.

Now I’ll try some more placec on the server. But even a clean install done by the host showed the same behaviour.

Is it possible that a hardware malfunction only affects the write tab’s function?

MySQL crahes happen more often when I’m active on the admin side, but obviously they don’t happen directly or with every opening of the write tab.
Only the warnings are constantly there :(

saccade · 2010-01-26 21:41:22

Problem solved (today in the morning).
I didn’t get any details yet, but the reason was obviously following:

Not really the hardware, but in my eyes nearby:
Obviously in the server’s 64-bit-setup a 32-bit module was missing or didn’t work (or the 64-bit one?)

After some changes of the host my txp worked like a charm without any change from my side.
Who is to blame? Maybe the parent hosting provider (bad setup) or maybe an openSUSE-Package?
I don’t know, my hosting provider doesn’t either (hope he’ll figure out),
but it wasn’t txp’s fault :)

I’ll post more details as soon as I’ll know – in case someone runs into the same problem one day.

Last edited by saccade (2010-01-26 21:44:20)

els · 2010-01-26 22:49:47

But he’s been very sure that textpattern is to blame, so I want to be sure it isn’t. :)

Go, Txp, go! Glad your site’s working again :)

Textpattern CMS

Textpattern CMS support forum

#1 2010-01-09 16:30:01

Lost connection to MySQL server / MySQL server has gone away

#2 2010-01-09 17:27:56

Re: Lost connection to MySQL server / MySQL server has gone away

#3 2010-01-09 19:08:40

Re: Lost connection to MySQL server / MySQL server has gone away

#4 2010-01-09 19:34:36

Re: Lost connection to MySQL server / MySQL server has gone away

#5 2010-01-09 19:49:34

Re: Lost connection to MySQL server / MySQL server has gone away

#6 2010-01-09 22:18:36

Re: Lost connection to MySQL server / MySQL server has gone away

#7 2010-01-10 00:22:58

Re: Lost connection to MySQL server / MySQL server has gone away

#8 2010-01-10 20:15:25

Re: Lost connection to MySQL server / MySQL server has gone away

#9 2010-01-26 21:41:22

Re: Lost connection to MySQL server / MySQL server has gone away

#10 2010-01-26 22:49:47

Re: Lost connection to MySQL server / MySQL server has gone away

Board footer