I came here to post about the same problem. It appears to have broken this morning. Did the API change again?
On 4 February 2016 at 07:33, Dr. Michael Bonert michael@librepathology.org wrote:
In September 2014, I described an intermittent recurrent problem associated with the InstantCommons images.
I hadn't seen the problem seen since April or May of 2015.
It is now back -- after I upgraded to MediaWiki 1.26.2. Unlike in the past, it hasn't resolved with a server re-boot.
I did have record traffic earlier in the week... but the problem --like in the past-- doesn't seem to be traffic related.
I cannot find a relation to memory. I'm not running out of memory. The underlying LAMP (Debian Linux Apache MySQL PHP) stack hasn't changed.
Product Versions Operating System: Debian (stable) MediaWiki 1.26.2 (f465524) PHP 5.6.13-0+deb8u1 (apache2handler) MySQL 5.5.44-0+deb8u1
The details of what is installed is here: http://librepathology.org/wiki/index.php/Special:Version
I do have git installed -- and am using it to upgrade.
Like in the past-- the image that is local to the site, i.e. non-InstantCommons, ( http://librepathology.org/wiki/index.php/File:Atypical_ductal_hyperplasia_-_... ) is still there-- and displays properly. At the same time, all the images from the InstantCommons are gone.
A list of previous posts I did can be found here: https://lists.wikimedia.org/pipermail/mediawiki-l/2014-September/043340.html https://lists.wikimedia.org/pipermail/mediawiki-l/2014-September/043345.html https://lists.wikimedia.org/pipermail/mediawiki-l/2014-September/043348.html https://lists.wikimedia.org/pipermail/mediawiki-l/2014-September/043349.html
Help on this would be much appreciated...
I have a testing site (pathologyprotocols.org) that is running the exact same set-up (behind a login). It is also failing suddenly in the same way; the InstantCommons images are gone.
I wonder whether...
- It is the InstantCommons server
- There is "talk" between the InstantCommons server and a MediaWiki install
(with the InstantCommons activated). I know this as images that are removed from the InstantCommons... are then removed on then MediaWiki install with InstantCommons activated.
I think the communication is governed by 'descriptionCacheExpiry' and
'apiThumbCacheExpiry' https://www.mediawiki.org/wiki/Manual:$wgUseInstantCommons ? I wonder whether setting those to infinity would solve anything.
- I suspect the thumb cache is purged... and then there is a bug preventing
the image from being confirmed as being the same as on the InstantCommons... or there a processing bottle neck as the thumbnails have to be re-created.
Thanks in Advance, Michael
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On Thu, Feb 4, 2016 at 11:39 AM, David Gerard dgerard@gmail.com wrote:
I came here to post about the same problem. It appears to have broken this morning. Did the API change again?
No, it was a change in the underlying image handling code that broke API prop=imageinfo in 1.27.0-wmf.12. Tracked as https://phabricator.wikimedia.org/T125804, and now resolved.
On 4 February 2016 at 17:14, Brad Jorsch (Anomie) bjorsch@wikimedia.org wrote:
No, it was a change in the underlying image handling code that broke API prop=imageinfo in 1.27.0-wmf.12. Tracked as https://phabricator.wikimedia.org/T125804, and now resolved.
yep, working for us now. Thanks!
- d.
wikitech-l@lists.wikimedia.org