WBB3 fehler bei der Installation

DerFalk

Registered User
Guten Morgen!

Ich habe folgendes Problem bei der Installation von WBB3:

Code:
 Fatal error: Invalid SQL: SELECT GROUP_CONCAT(DISTINCT groups.groupID ORDER BY groups.groupID ASC SEPARATOR ',') AS groupIDs, GROUP_CONCAT(DISTINCT languages.languageID ORDER BY languages.languageID ASC SEPARATOR ',') AS languageIDs,user_option.*, user.* FROM wcf1_user user LEFT JOIN wcf1_user_to_groups groups ON (groups.userID = user.userID) LEFT JOIN wcf1_user_to_languages languages ON (languages.userID = user.userID) LEFT JOIN wcf1_user_option_value user_option ON (user_option.userID = user.userID) WHERE user.userID = 1 GROUP BY user.userID LIMIT 1
    You get more information about the problem in our knowledge base: http://www.woltlab.com/help/?code=2013 Information:
error message: Invalid SQL: SELECT GROUP_CONCAT(DISTINCT groups.groupID ORDER BY groups.groupID ASC SEPARATOR ',') AS groupIDs, GROUP_CONCAT(DISTINCT languages.languageID ORDER BY languages.languageID ASC SEPARATOR ',') AS languageIDs,user_option.*, user.* FROM wcf1_user user LEFT JOIN wcf1_user_to_groups groups ON (groups.userID = user.userID) LEFT JOIN wcf1_user_to_languages languages ON (languages.userID = user.userID) LEFT JOIN wcf1_user_option_value user_option ON (user_option.userID = user.userID) WHERE user.userID = 1 GROUP BY user.userID LIMIT 1
 error code: 2013
 sql type: MySQLDatabase
sql error: Lost connection to MySQL server during query
sql error number: 2013
sql version: 5.0.58
file: /var/www/vhosts/XXX.de/httpdocs/start/wcf/lib/system/database/MySQLDatabase.class.php (116)
 php version: 5.2.8
 wcf version: 1.0.10 (Horizon)
 date: Fri, 09 Jan 2009 05:51:47 +0000
 request: /start/install.php?step=installPackages
 referer: http://www.XXX.de/start/install.php
   Stacktrace:
#0 /var/www/vhosts/XXX.de/httpdocs/tmp/17219a86_Database.class.php(116): MySQLDatabase->sendQuery('SELECT ??GROUP_...', 1, 0)
#1 /var/www/vhosts/XXX.de/httpdocs/tmp/17219a86_User.class.php(61): Database->getFirstRow('SELECT ??GROUP_...')
#2 /var/www/vhosts/XXX.de/httpdocs/tmp/17219a86_UserSession.class.php(31): User->__construct(1, NULL, NULL, NULL)
#3 /var/www/vhosts/XXX.de/httpdocs/tmp/17219a86_WCFSetup.class.php(868): UserSession->__construct(1)
#4 /var/www/vhosts/XXX.de/httpdocs/tmp/17219a86_WCFSetup.class.php(292): WCFSetup->installPackages()
#5 /var/www/vhosts/XXX.de/httpdocs/tmp/17219a86_WCFSetup.class.php(60): WCFSetup->setup()
#6 /var/www/vhosts/XXX.de/httpdocs/start/install.php(744): WCFSetup->__construct()
#7 {main}

In der MySQL.log taucht folgendes auf:
Code:
090109  6:51:47 - 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=15728640
read_buffer_size=16384
max_used_connections=4
max_connections=100
threads_connected=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 20160 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xa0d4ae8
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=0xb1632dd8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81b2ac8
0x851c02c
0x822f668
0x8200207
0x82044b3
0x820dc0d
0x820dcbc
0x820df44
0x821977c
0x821b55d
0x821bded
0x81cb8d6
0x81cfbeb
0x81d016e
0x81d1f98
0x57045b
0x4c7e5e
New value of fp=(nil) 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 0x9fc22c0 = SELECT GROUP_CONCAT(DISTINCT groups.groupID ORDER BY groups.groupID ASC SEPARATOR ',') AS groupIDs,
					GROUP_CONCAT(DISTINCT languages.languageID ORDER BY languages.languageID ASC SEPARATOR ',') AS languageIDs,user_option.*,
					user.*
				FROM 	wcf1_user user
					 	LEFT JOIN wcf1_user_to_groups groups ON (groups.userID = user.userID)
LEFT JOIN wcf1_user_to_languages languages ON (languages.userID = user.userID) LEFT JOIN wcf1_user_option_value user_option ON (user_option.userID = user.userID)
				WHERE 	user.userID = 1 	GROUP BY user.userID  LIMIT 1
thd->thread_id=3548
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
090109 06:51:47  mysqld restarted
090109  6:51:47 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
090109  6:51:47 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
090109  6:51:47 [Warning] option 'sort_buffer_size': unsigned value 32768 adjusted to 32776
090109  6:51:47 [Warning] option 'sort_buffer_size': unsigned value 32768 adjusted to 32776
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090109  6:51:48  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...
090109  6:51:48  InnoDB: Started; log sequence number 0 2033706765
090109  6:51:48 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.58'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution

Und hier meine my.cnf:
Code:
[mysqld]
bind-address=127.0.0.1 
set-variable=local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
key_buffer = 15M
net_buffer_length = 8K
sort_buffer_size = 32K
myisam_sort_buffer_size = 32K
read_buffer_size = 16K
read_rnd_buffer_size = 32K
join_buffer_size = 512K
query_cache_size = 4M
thread_cache = 32
table_cache = 512
max_allowed_packet = 10M
max_connections = 100
low_priority_updates = 1
long_query_time = 2
skip-bdb
set-variable =  innodb_buffer_pool_size=2M
[mysql.server]
user=mysql
basedir=/var/lib

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

Hat einer eine Idee an welcher Stelle ich eine sinnvolle Änderung vornehmen muß, damit ich das Forum installieren kann?


Gruß
DerFalk
 
Hallo,

Nutzt du einen Rootserver oder einen Vserver? Scheint so, als sei dein Server mit den Installationsquerrys überfordert.

EDIT: Mit welchen Werten du runspielen solltest sagt dir MySQL:
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 20160 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Sieht so aus als schafft dein Server die 20160 K Speicher nicht. Versuch das mal zu verringern.
 
Ist ein RootDS mit 1GB Ram, komisch ist halt nur, das es nur bei dem WBB3 bis dato aufgetreten ist. Der Support von WBB meinte dazu, das ich mal auf die aktuelle Version vom MySQL updaten sollte, da es sich um einen Bug in der Version handelt... hm
 
Hallo,

kann ich unter der Version 3.0.8 pl1 nicht bestätigen.
Ich Nutze php 5.2.8 als fcgi dazu apache 2.2.9 und MYSQL Server Version: 5.1.30 - MySQL-Client-Version: 5.0.75

läuft alles sauber und ohne Probs durch.


the_condor
 
Hallo,

in meinem Fall ist es ein Rootserver, kann das gerne aber nochmal auf einem kleinen vps testen.

mfg
the_condor

edit://

Also das ganze schnell mal unter vps getestet, funktioniert auch ohne Probs.
System ein Mem von 512 MB ohne Swap
 
Last edited by a moderator:
So, es liegt DEFINITIV an der Version 5.0.58 vom MySQL ... die ist buggy. Hab auf einem Testsystem auf die 5.0.66 geupdated und dann ging es 1a!

:cool:
 
Back
Top