Last modified: 2006-12-03 15:35:28 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 659 - The database did not find the text of a page that it should have found
The database did not find the text of a page that it should have found
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: db-repl-track
  Show dependency treegraph
Reported: 2004-10-07 19:30 UTC by Anthony
Modified: 2006-12-03 15:35 UTC (History)
1 user (show)

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


Description Anthony 2004-10-07 19:30:22 UTC
The database did not find the text of a page that it should have found, named
"See this creative writing letter (Diff: 2793150, 2805840)".

If it is a recently changed page, trying again in a minute or two will usually
work. Alternatively, you may have followed an outdated diff or history link to a
page that has been deleted.

If this is not the case, you may have found a bug in the software. Please report
this to an administrator, making note of the URL.
Comment 1 JeLuF 2004-10-07 19:39:36 UTC
This message can also occur if the page, in this case 
[[See this creative writing]], does not exist. The text
should be updated to also mention this case.
Comment 2 Jamesday 2004-10-07 19:50:54 UTC
This is now usually caused by replication lag, which is why I updated the
message a week or so ago to suggest trying again in a minute or two if it is a
recently changed page. Lag is typically a second or two, rises to many minutes
while searchindex update or special pages update are running. The slaves can't
usally update searchindex fast enough and for the special pages they have to run
the query to update the special page themselves. For the spacial pages, using a
MyISAM table, updating with the option not to replicate and then using load
table from master on the slaves for all wikis is one alternative approach.
Faster special reports is the real solution, though.
Comment 3 Leah 2004-11-14 00:19:35 UTC
This may be occurring very frequently.

The database did not find the text of a page that it should have found, named

The database did not find the text of a page that it should have found, named
"Wikipedia:Village pump (miscellaneous),oldid=7437401".
Comment 5 Leah 2004-12-09 20:18:06 UTC
I guess that should be ''three''.  Isn't there any way to edit comments here?
Comment 6 JeLuF 2004-12-13 06:15:07 UTC
This kind of problem happens if DBs (master and slave) are out of sync.
This is monitored and most often fixed within a few minutes. 1.4 will
contain code to automatically detect delays and fall back to the master.
Comment 7 Zigger 2005-01-08 19:20:25 UTC
Same error message just occurred for
Later article version was from two weeks ago.
Repeating the request worked ok.
meta has been running 1.4beta4 for about one day.
Comment 8 Zigger 2005-01-08 19:34:40 UTC
The previous error occurred shortly after editing.
Updating an article causes the previous revision to be added to the "old" table
(with a generated "old_id" number), which is also subject to database
replication lag.
Comment 9 Rob Church 2006-12-03 12:47:29 UTC
I'm guessing that, since there aren't frequent reports of users screaming about
missing page text, this was fixed with the transition to the 1.4 branch, eons ago.

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