multiple users running into phantom "page does not exist" errors
Closed, ResolvedPublic


Author: rickblock

There have been numerous reports lately at various help pages on en about encountering pages that mysteriously don't exist (latest
at Village Pump (misc), see URL attached). Various folks have suggesting adding "?action=purge" to the page request URL which
does indeed seem to "fix"the issue instance by instance. However, this has happened often enough that there's clearly some sort of
bug in the caching or DB lookup or something causing pages that do exist to not be found.

Version: unspecified
Severity: normal


bzimport set Reference to bz7401.
bzimport added a subscriber: Unknown Object (MLST).
bzimport created this task.Sep 24 2006, 5:31 PM

rickblock wrote:

Also see the thread at, and the
very next thread at VPT.

Has this continued to happen in the last day?

I would greatly appreciate seeing a screen shot of such a problem page
*BEFORE* it is purged. This could help narrow down the issue by indicating
which other UI elements mark it.

Reminder: WE CANNOT DO ANY DIAGNOSIS after the page has been purged.

rickblock wrote:

The page shown (from a link) is [[MediaWiki:Noarticletext]] (I don't have a screenshot, but I do remember this). At en, [[solar radius]]
displayed the noarticletext page until I purged it (at about 17:30 Sept 24 UTC). If I see anyone complaining about this I'll let you

garstonian wrote:

The page is showing the same fault, didn't
change anything, mainly because I don't know how to :)

garstonian wrote:

screenshot for the above is at hope this helps

brion added a comment.Oct 2 2006, 4:14 PM

(In reply to comment #5)

Not quite the same symptom, but

List_of_environment_topics_on_one_page is acting weird (as reported

Totally unrelated; not even vaguely similar.

(In reply to comment #6)

The page is showing the same fault, didn't
change anything, mainly because I don't know how to :)

Thanks. There was a bad parser cache entry for default user options,
saved to the cache on September 19. This may have been due to some
older problem that's been corrected, or a temporary fault. Can't be
very certain without more information.

Have purged that page after saving the info.

brion added a comment.Mar 30 2009, 9:47 PM

Going to assume this one-off issue was resolved. If similar continuing, please add info. :)

Add Comment