lensowiki:Installation caveats - Revision history

Lensovet: /* Updating MySQL on Mac OS X */ formatting and typo fixes

2010-06-13T21:58:10Z

‎Updating MySQL on Mac OS X: formatting and typo fixes

Lensovet: /* Short article URLs */ mysql crap

2010-06-13T21:49:24Z

‎Short article URLs: mysql crap

Lensovet: /* References */ +navbox

2008-04-19T23:22:37Z

‎References: +navbox

Lensovet: /* New installations */ up the version

2007-12-11T10:37:22Z

‎New installations: up the version

Lensovet: /* References */ formatting

2007-11-15T08:27:27Z

‎References: formatting

Lensovet: updates

2007-11-15T08:27:03Z

updates

195.251.253.108 at 05:51, 13 June 2007

2007-06-13T05:51:03Z

Lensovet: rvv

2007-04-12T04:13:24Z

rvv

200.238.102.162 at 15:11, 11 April 2007

2007-04-11T15:11:04Z

Lensovet: +interwiki info, new headings

2006-09-16T19:25:15Z

+interwiki info, new headings

@@ Line 60: / Line 60: @@
 ==Updating MySQL on Mac OS X==
-I just went through a prolonged ordeal to upgrade MySQL from 5.1.30 to 5.1.47, so I'm going to write down some steps so that I don't hit so many dead-ends in the future.
+I just went through a prolonged ordeal to upgrade MySQL from 5.1.30 to 5.1.47, so I'm going to write down some steps so that I don't hit so many dead-ends in the future. Note that this presumes that you have already done a DB dump of your wiki database (i.e. SequelPro's Export… command).
 The installer does not detect the presence of an older installation, and as a result, leaves the old data directory untouched. In retrospect, you could probably just move it and all would be well. Alternatively, you can recreate your databases as well. Here's what I did.
-# First, to run the mysql_upgrade script, enable the root user in Directory Utility (which is now in CoreServices, or accessible from the Account prefs prefpane).
+* First, to run the <tt>mysql_upgrade</tt> script, enable the root user in Directory Utility (which is now in CoreServices, or accessible from the Accounts prefpane).
-# <tt>su -</tt>
+* <tt>su -</tt>
-# <tt>su _mysql -c "/usr/local/mysql/mysql_upgrade"</tt>
+* <tt>su _mysql -c "/usr/local/mysql/mysql_upgrade"</tt>
-# <tt>logout</tt>
+* <tt>logout</tt>
-# Restart MySQL
+* Restart MySQL
-Now, [http://dev.mysql.com/doc/refman/5.1/en/default-privileges.html secure the root/guest accounts], [http://dev.mysql.com/doc/refman/5.1/en/create-user.html create the wiki user] and [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki#MySQL the wiki db and grant privileges]. Go into LocalSettings.php and change the connection settings so that it doesn't try to connect to the DB until you are done with the rest. Then
+Now, [http://dev.mysql.com/doc/refman/5.1/en/default-privileges.html secure the root/guest accounts], [http://dev.mysql.com/doc/refman/5.1/en/create-user.html create the wiki user], and [http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki#MySQL create the wiki db and grant privileges]. Go into LocalSettings.php and change the connection settings so that it doesn't try to connect to the DB until you are done with the rest. Then
-# <tt>sudo mkdir /usr/local/mysql/etc</tt>
+* <tt>sudo mkdir /usr/local/mysql/etc</tt>
-# <tt>sudo mkdir /usr/local/mysql/etc</tt>
+* <tt>sudo chown -R mysql /usr/local/mysql/etc</tt>
-# <tt>su -</tt>
+* <tt>su -</tt>
-# <tt>su -m _mysql -c "touch /usr/local/mysql/etc/my.cnf"</tt> (you can safely ignore the <tt>getcwd</tt> error)
+* <tt>su -m _mysql -c "touch /usr/local/mysql/etc/my.cnf"</tt> (you can safely ignore the <tt>getcwd</tt> error)
-# <tt>logout</tt>
+* <tt>logout</tt>
-# Turn off root user
+* Turn off root user
-# Add this to the <tt>my.cnf</tt> file:
+* Add this to the <tt>my.cnf</tt> file:
 :<code>[mysqld]<br/>max_allowed_packet=10737418</code>
-# Restart MySQL again
+* Restart MySQL again
-# Fire up SequelPro and import the SQL dump made earlier. Errors related to disallowed <tt>DROP</tt> operations are fine.
+* Fire up SequelPro and import the SQL dump made earlier. Errors related to disallowed <tt>DROP</tt> operations are fine.
 {{cs projects}}
 [[Category:MediaWiki User's Guide]]

@@ Line 58: / Line 58: @@
 ===References===
 *http://bugzilla.wikimedia.org/show_bug.cgi?id=11428
 {{cs projects}}
 [[Category:MediaWiki User's Guide]]

@@ Line 58: / Line 58: @@
 ===References===
 *http://bugzilla.wikimedia.org/show_bug.cgi?id=11428
 [[Category:MediaWiki User's Guide]]

@@ Line 6: / Line 6: @@
 The obvious solution to this is to encode your tables in a different encoding. But what if you want to still use UTF8? There is a solution.
-As of 1.7.1, there are two tables affected by this problem: '''categorylinks''' and '''jobs''' (The key is 2 * (255   255  8) = 1032). Both of these changes need to be made in '''/maintenance/tables.sql''' ''before'' running the initial configuration.
+As of 1.11.0, there are two tables affected by this problem: '''categorylinks''' and '''jobs''' (The key is 2 * (255   255  8) = 1032). Both of these changes need to be made in '''/maintenance/tables.sql''' ''before'' running the initial configuration.
 In categorylinks, you need to change the following line:

@@ Line 57: / Line 57: @@
 ===References===
-http://bugzilla.wikimedia.org/show_bug.cgi?id=11428
+*http://bugzilla.wikimedia.org/show_bug.cgi?id=11428
 [[Category:MediaWiki User's Guide]]

@@ Line 2: / Line 2: @@
 ==MySQL table field lengths==
 ===New installations===
-The current MediaWiki install, 1.7.1 · 2006-07-08, will run into two problems upon trying to initialize all the initial MySQL tables if those tables are encoded in UTF8. The reason this happens is that KEY fields are limited to 1000 bytes, and each character takes up 3 bytes in UTF. When the key fields contain a combination of columns whose combined number of bytes exceeds 1000, the installation will bail.
+The current MediaWiki install, 1.11.0, will run into two problems upon trying to initialize all the initial MySQL tables if those tables are encoded in UTF8. The reason this happens is that KEY fields are limited to 1000 bytes, and each character takes up 3 bytes in UTF. When the key fields contain a combination of columns whose combined number of bytes exceeds 1000, the installation will bail.
 The obvious solution to this is to encode your tables in a different encoding. But what if you want to still use UTF8? There is a solution.
@@ Line 9: / Line 9: @@
 In categorylinks, you need to change the following line:
-   KEY cl_sortkey(cl_to,cl_sortkey),
+   KEY cl_sortkey(cl_to,cl_sortkey,cl_from),
 to
-   KEY cl_sortkey(cl_to(253),cl_sortkey),
+   KEY cl_sortkey(cl_to(160),cl_sortkey,cl_from),
 To find the line, open the file in your favorite text editor, and search for '''/cat'''. Scroll down until you see the original line as shown above.
@@ Line 19: / Line 19: @@
    KEY (job_cmd(166), job_namespace, job_title(166))
 To find the line, search for '''/jobs'''. Scroll down until you see the original line as shown above.
 This guarantees that they keys are short enough so that the install won't bail.
 ===Upgrades===
-Upgrades are plagued by the same problem and require a similar workaround. However, the files to patch are '''/maintenance/archives/patch-categorylinks.sql''' and '''/maintenance/archives/patch-job.sql''', respectively.
+Upgrades are plagued by the same problem and require a similar workaround. However, the files to patch are '''/maintenance/archives/patch-categorylinksindex.sql''' and '''/maintenance/archives/patch-job.sql''', respectively. You might also need to change <code>KEY cl_sortkey(cl_to,cl_sortkey)</code> to <code>KEY cl_sortkey(cl_to(253),cl_sortkey)</code> in '''/maintenance/archives/patch-categorylinks.sql'''.
 ===References===
@@ Line 37: / Line 32: @@
 ==Interwiki links==
 The initial interwiki table does not include the shorthand keys <code>w</code>, <code>m</code>, and <code>mw</code>; you have to add them manually. However, even after you add them, you have to create at least one new interwiki link for the MediaWiki software to "re-read" the interwiki prefix table and actually make the links functional. You only need to do this once as an administrator, and the newly-created link can then be immediately deleted.
 ===References===
 *http://meta.wikimedia.org/wiki/Help:Guide_for_system_administrators_for_setting_up_interwiki_linking#Admin_tips
 [[Category:MediaWiki User's Guide]]

@@ Line 1: / Line 1: @@
-==New installations==
+Upon installing the Mediawiki software, I ran into a few problems. Here, I document fully functional workarounds and solutions to the problems I encountered.
 The current MediaWiki install, 1.7.1 · 2006-07-08, will run into two problems upon trying to initialize all the initial MySQL tables if those tables are encoded in UTF8. The reason this happens is that KEY fields are limited to 1000 bytes, and each character takes up 3 bytes in UTF. When the key fields contain a combination of columns whose combined number of bytes exceeds 1000, the installation will bail.
@@ Line 21: / Line 23: @@
 This guarantees that they keys are short enough so that the install won't bail.
-==MySQL 5==
+===MySQL 5===
 If you turn on experimental MySQL 5 UTF-8 handling, the file you need to patch is  '''/maintenance/mysql5/tables.sql'''. In addition, the <code>cl_sortkey</code> key in <code>categorylinks</code> is apparently too big. Therefore, instead of the change posted above, use
    KEY cl_sortkey(cl_to(247),cl_sortkey),
-==Upgrades==
+===Upgrades===
 Upgrades are plagued by the same problem and require a similar workaround. However, the files to patch are '''/maintenance/archives/patch-categorylinks.sql''' and '''/maintenance/archives/patch-job.sql''', respectively.
-==References==
+===References===
 These bugs are actually filed on the MediaWiki bugzilla. See
 *http://bugzilla.wikimedia.org/show_bug.cgi?id=4445
 *http://bugzilla.wikimedia.org/show_bug.cgi?id=1322
 [[Category:MediaWiki User's Guide]]