Hi @Azhao12345, thanks for taking the time to report this!

Which version is "the latest mediawiki" exactly?

After running php maintenance/importImages.php, did you also run php maintenance/update.php?

maintenance/update.php is for upgrading MediaWiki or adding a new extension that requires it, it shouldn't be used for this.

I'm a bit confused, you say the page contains both the text "No file by this name exists." and "Importing file"? Where in the page does "Importing file" appear?

By "cache=accel" do you mean setting $wgMainCacheType = CACHE_ACCEL?

Ah, thanks @Ciencia_Al_Poder! (and I'm sorry for having given wrong advice)

In T143852#2582237, @Ciencia_Al_Poder wrote:

maintenance/update.php is for upgrading MediaWiki or adding a new extension that requires it, it shouldn't be used for this.

I'm a bit confused, you say the page contains both the text "No file by this name exists." and "Importing file"? Where in the page does "Importing file" appear?

By "cache=accel" do you mean setting $wgMainCacheType = CACHE_ACCEL?

It is definitely an unusual error. The text "importing file" appears directly below "no file by this name exists"

these are the cache settings:

Shared memory settings

$wgMainCacheType = CACHE_ACCEL;
$wgMemCachedServers = [];
$wgSessionCacheType=CACHE_DB;

I'm using mediawiki 1.27

@Azhao12345 Are you using File Cache? Or some other static url cache via Nginx? Or a reverse-proxy like Squid or Varnish?

If so, then the issue may be related to one of these:

• T109214: File upload should clear parser and file cache on usage pages
• T26575: Purge Category and File description pages from HTTP/File cache when members/usage changes via LinkUpdate

If you could try again and that time also make sure it is not caused by your web browser's cache (e.g. use a force refresh, or enable "Disable cache" in the developer tools, or use Incognito mode the second time).

there is no cache, just a single apache server. as I said, restarting the php daemon or going to the individual page purge endpoint.

This really should be enough info to attempt to repro the problem.

CACHE_ACCEL is a cache. It resides only on the webserver and it can't be contacted from the outside, so maintenance scripts can't clear this cache.

However, I'm not sure if MediaWiki uses it to store this kind of information, given that it should be of low capacity, probably.

@Azhao12345 Does that still happen in a supported and more recent MediaWiki version (if yes, which one)?