Last modified: 2014-03-19 19:35:14 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 398 - Improve MediaWiki:Dberrortext to link to a config-defined status page
Improve MediaWiki:Dberrortext to link to a config-defined status page
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
PC All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy, i18n
: 3785 18824 (view as bug list)
Depends on:
Blocks: messages
  Show dependency treegraph
Reported: 2004-09-06 10:48 UTC by Addicted
Modified: 2014-03-19 19:35 UTC (History)
7 users (show)

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


Description Addicted 2004-09-06 10:48:28 UTC
If the german wikipedia (webserver?) can't connect to the database it brings the message "Konnte keine Verbindung 
zur Datenbank auf $1 herstellen." (says "Could not establish connection to database on $1" or so.).
On the "noticed problems" page of the german section a user asks for a more descriptive message for not so 
experienced users.
Comment 1 Antoine "hashar" Musso (WMF) 2005-12-03 15:51:50 UTC
*** Bug 3785 has been marked as a duplicate of this bug. ***
Comment 2 Antoine "hashar" Musso (WMF) 2005-12-03 15:52:21 UTC
From #3785:

Initial comment from Christopher Beland <>, at 2005-10-23
21:04 UTC:

The past few days, I've occasionally been getting an error message that ends in
the diagnostic "(Can't contact the database server: )". It would be
considerably more helpful if this message contained the IP address or name of
the server it was attempting to contact, if not also the IP address or name of
the squid that produced the error. People seem to be reluctant to check all of
the servers just on the off chance there might still be a problem, especially
since the error is quite transient.
Comment 3 Christopher Beland 2005-12-04 03:27:57 UTC
Today, I got one error that said:


If reporting this error to the Wikimedia System Administrators, please include
the following details:
Request: GET, from
via (squid/2.5.STABLE12) to ([unknown])
Error: ERR_CANNOT_FORWARD, errno (104) Connection reset by peer at Sat, 03 Dec
2005 23:49:16 GMT


And another that said:


The requested URL could not be retrieved

While trying to retrieve the URL:

The following error was encountered:

    * Connection Failed 

The system returned:

    (110) Connection timed out

The remote host or network may be down. Please try the request again.

Your cache administrator is
Generated Sat, 03 Dec 2005 23:50:06 GMT by


If the IP address of the MySQL server which is down is known, it should be
included in these messages. -B.
Comment 4 Happy-melon 2009-07-24 14:12:49 UTC
LATER per Brion at bug18824c3.
Comment 5 Happy-melon 2009-07-24 14:13:10 UTC
*** Bug 18824 has been marked as a duplicate of this bug. ***
Comment 6 Chad H. 2009-07-24 14:15:22 UTC
Better summary than "Mediawiki:"
Comment 7 Happy-melon 2009-07-24 14:48:03 UTC
I think I got distracted... :D

What I was *trying* to write was that this only applies to [[MediaWiki:dberrortext]]...
Comment 8 Brion Vibber 2011-11-29 20:18:18 UTC
Is this even necessary? Would simply improving the default message (especially if it can link to a config-defined status page) help here?
Comment 9 Christopher Beland 2012-06-02 23:46:21 UTC
Makes sense to me, if the default message both contains useful diagnostic information and an introductory message friendly to non-technical users.
Comment 10 Andre Klapper 2012-11-17 13:56:13 UTC
[Reopening "RESOLVED LATER" as lowest priority.]

Strings are around "# General errors" in;a=blob;f=languages/messages/MessagesEn.php#l973
Comment 11 Sucheta Ghoshal 2013-02-13 10:48:58 UTC
Is this bug really relevant anymore? Because I can not really find the message that had been posted at first, maybe it has changed or something?
Comment 12 Nemo 2013-02-13 10:56:39 UTC
Key is the same:

A database query syntax error has occurred.
This may indicate a bug in the software.
The last attempted database query was:
from within function "<code>$2</code>".
Database returned error "<samp>$3: $4</samp>".
Comment 13 Sucheta Ghoshal 2013-02-14 13:11:34 UTC
So, the German message says the same thing, I suppose ( Pardon me, if I am too wrong. I don't really know German). If it does not have any problem with the message - maybe we should close this bug?
Comment 14 Nemo 2013-02-14 13:31:56 UTC
The message is always the same and the same still applies...

Brion's bug 18824 comment 3
> I'm pretty sure we deliberately don't use the site-customized messages in the
> DB error since by definition if our DB access is broken it may not be safe to
> pull from the DB. You don't necessarily know what the problem was or what
> further attempts to access the backend might cause. Probably not worth the
> effort of poking at it, but we can LATER it for prettification.

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