Last modified: 2010-05-15 14:36:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 650 - Detect MySQL 4.1 errors and either work around or notify user of problem
Detect MySQL 4.1 errors and either work around or notify user of problem
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
unspecified
All All
: Normal major with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://mail.wikipedia.org/pipermail/w...
:
: 2491 3052 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-06 00:09 UTC by Brion Vibber
Modified: 2010-05-15 14:36 UTC (History)
2 users (show)

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


Attachments

Description Brion Vibber 2004-10-06 00:09:59 UTC
There are problems when installing with with MySQL 4.1 due to changes in the 
protocol. We need to either detect this condition and work around it, or notify the user 
how to fix it.
Comment 1 Ike Bottema 2005-03-20 19:48:57 UTC
Brings up Database Error page with a "internal error" message.
Comment 2 Richard J. Holton 2005-03-20 20:37:32 UTC
(In reply to comment #1)
> Brings up Database Error page with a "internal error" message.

Can you provide any details?
Comment 3 Ike Bottema 2005-03-20 21:53:18 UTC
I didn't perform the actual install so can't vouch for any errors observed
during that time.  We're running MySQL 4.1.x and PHP 5.  Apparently mediawiki is
not fully setup to work with mysql 4.1.x?

The '''Database Error''' page is arrived at when attempting to restore a deleted
page and thus following a deleted file link at the '''View and restore deleted
pages''' special page.  The same '''Database Error''' page is arrived at when
attempting to follow a Deletion Log link at the '''Recent Changes''' page.
Comment 4 Brion Vibber 2005-03-20 22:29:59 UTC
If this is not related specifically to the installation issue with the MySQL authentication 
protocol, please file a separate bug. This however sounds like the log bug which has been 
fixed already. Upgrade to 1.4.0 final when it is released later today, and run the updater to fix 
the logging table.
Comment 5 Brion Vibber 2005-03-27 02:22:36 UTC
1.4.0 released; kicking back to 1.5 blockers.
Comment 6 Brion Vibber 2005-06-12 13:54:29 UTC
Fixed in CVS HEAD for 1.5.

Now prominently warns about MySQL 4.1 problems if old libraries detected.
Key length is shorter so create works.
Comment 7 Brion Vibber 2005-06-23 09:13:06 UTC
*** Bug 2491 has been marked as a duplicate of this bug. ***
Comment 8 Benjamin Melançon 2005-07-03 20:57:43 UTC
I guess re-opening this bug is too drastic a measure, but despite listing this bug (and mine, <a href="http://bugzilla.wikimedia.org/
show_bug.cgi?id=2491">2491</a>, as a duplicate) the recommendation from Ike Bottema "to either detect this condition and work 
around it, or notify the user how to fix it" has not been implemented at all.  Using the latest stable version, 1.4.5, I first get a happy 
message about the database:

	• 	Connected to database... 4.1.10-standard; enabling MySQL 4 enhancements

And then the installation ends with this:

<code>Sorry! The wiki is experiencing some technical difficulties, and cannot contact the database server.</code>

So this fix for 1.5 doesn't do people much good yet:

"Fixed in CVS HEAD for 1.5.

Now prominently warns about MySQL 4.1 problems if old libraries detected.
Key length is shorter so create works."

If I remember how I successfully installed last time, the error message just needs to be extended to tell installers to create the mysql 
user accounts and passwords themselves.
Comment 9 Brion Vibber 2005-07-04 06:44:51 UTC
The fix is for 1.5 and doesn't appear in 1.4.5.

Have you tried installing the current version pulled from CVS HEAD, or at least 1.5beta1?
Can you confirm correct or incorrect behavior there?
Comment 10 Benjamin Melançon 2005-07-04 11:56:18 UTC
(In reply to comment #9)
> The fix is for 1.5 and doesn't appear in 1.4.5.
> 
> Have you tried installing the current version pulled from CVS HEAD, or at least 1.5beta1?
> Can you confirm correct or incorrect behavior there?

Sorry, after I was mostly done with my comment I realized the fix referred to 1.5 only.  And 
no, I haven't checked the CVS... I take it that it really is fixed there, but the thing is that the 
current error message in the stable release is so unhelpful that even though I'd worked 
around the bug a week or two ago, when I hit it again I was back at square one, looking at 
my own bug report to try to remember how I worked around it-- simple really, the 
databases and database user with password have to be created manually, even if root 
access appears to work.

My point is that simply adding the below text to the current error message (a ten second fix)
would make it an easy work-around, instead of a "what the hell do I do now / file an 
annoying duplicate bug report" moment. 

Something like, "You'll have to create a database user yourself and enter the details here."

If 1.5 will be out soon forget it, but the Beta warnings scared me from putting it straight on 
my site, despite the very attractive increased Sysop features, and I don't have the time to 
have fun.
Comment 11 Brion Vibber 2005-08-05 07:33:58 UTC
*** Bug 3052 has been marked as a duplicate of this bug. ***

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


Navigation
Links