Last modified: 2012-02-22 12:50:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T36571, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34571 - Installation is broken
Installation is broken
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.19
All FreeBSD
: Unprioritized blocker (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-21 20:21 UTC by Islam Ykov
Modified: 2012-02-22 12:50 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Islam Ykov 2012-02-21 20:21:43 UTC
MediaWiki 1.19 from svn.

Instllation failed at page=Install:

Warning: mysql_query() [function.mysql-query]: MySQL server has gone away in /var/www/mediawiki/includes/db/DatabaseMysql.php on line 31

Warning: mysql_query() [function.mysql-query]: Error reading result set's header in /var/www/mediawiki/includes/db/DatabaseMysql.php on line 31

Warning: Cannot modify header information - headers already sent in /var/www/mediawiki/includes/Exception.php on line 184

Connection refused (localhost)


Mysql 5.5.20 from ports, InnoDB, crash log:

120221 18:53:24 mysqld_safe mysqld restarted
120221 18:53:24 InnoDB: The InnoDB memory heap is disabled
120221 18:53:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120221 18:53:24 InnoDB: Compressed tables use zlib 1.2.3
120221 18:53:24 InnoDB: Initializing buffer pool, size = 32.0M
120221 18:53:24 InnoDB: Completed initialization of buffer pool
120221 18:53:24 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1643075
120221 18:53:24  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...
InnoDB: Doing recovery: scanned up to log sequence number 1649324
120221 18:53:24  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 7$
InnoDB: Apply batch completed
120221 18:53:24  InnoDB: Waiting for the background threads to start
120221 18:53:25 InnoDB: 1.1.8 started; log sequence number 1649324
120221 18:53:25 [Note] Recovering after a crash using mysql-bin
120221 18:53:25 [Note] Starting crash recovery...
120221 18:53:25 [Note] Crash recovery finished.
120221 18:53:25 [Note] Event Scheduler: Loaded 0 events
120221 18:53:25 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.5.20-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
Comment 1 Brion Vibber 2012-02-21 20:52:09 UTC
Sounds like MySQL crashed... report bug to mysql or try a different system?
Comment 2 Islam Ykov 2012-02-21 20:54:08 UTC
Error at line 130:

# mysql -u root -p wikidb < tables.sql 
Enter password: 
ERROR 2013 (HY000) at line 130: Lost connection to MySQL server during query


mysql> CREATE UNIQUE INDEX /*i*/user_name ON /*_*/user (user_name);
ERROR 2013 (HY000): Lost connection to MySQL server during query


It’s bug with MySQL, not MediaWiki?
Comment 3 Brion Vibber 2012-02-21 21:24:31 UTC
Your log extracts are showing that MySQL is crashing and restarting; this is consistent with the output you show most recently (server connection going away).

If MySQL is crashing, it's either a bug in MySQL, a bug in the compiler or libraries used to build and run MySQL, or a hardware bug in the computer that causes a software failure.

There is nothing in the SQL statements we're pushing that *should* be able to cause a crash, unless the above are true.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links