Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-17 Thread Bjoern Kahl
Am 13.08.14 um 18:20 schrieb C. Scott Ananian: On Tue, Aug 12, 2014 at 12:48 AM, Bjoern Kahl m...@bjoern-kahl.de wrote: + require_once ( 'extensions/BibTex/bibtex.php' ); + require_once ( 'extensions/MathJax/MathJax.php' ); + require_once('extensions/WikiEditor/WikiEditor.php'); +

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-17 Thread Bjoern Kahl
Am 13.08.14 um 16:54 schrieb Arlo Breault: Is this happening for all pages on the wiki, or just for this “TestPage”? It happens on all pages. I created the TestPage to rule out problems with complex WikiText. The TestPage is quite simple: only 35 lines, 83 words and 1493 characters

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-13 Thread Arlo Breault
Is this happening for all pages on the wiki, or just for this “TestPage”? On Monday, August 11, 2014 at 4:48 PM, Bjoern Kahl wrote: Dear Scott dear All, Am 11.08.14 um 11:54 schrieb C. Scott Ananian: What could cause this behavior and how should I configure my system to prevent

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-13 Thread C. Scott Ananian
On Tue, Aug 12, 2014 at 12:48 AM, Bjoern Kahl m...@bjoern-kahl.de wrote: + require_once ( 'extensions/BibTex/bibtex.php' ); + require_once ( 'extensions/MathJax/MathJax.php' ); + require_once('extensions/WikiEditor/WikiEditor.php'); +

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-11 Thread Bjoern Kahl
Dear Scott, Am 11.08.14 um 05:36 schrieb C. Scott Ananian: What seems like a deadlock may in fact be parsoid timing out while trying to connect to your local wiki's API end point. We have had some users report problems of this sort which were caused by their firewall or access control

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-11 Thread C. Scott Ananian
What could cause this behavior and how should I configure my system to prevent the deadlocks? If this is a Bug in either MediWiki or the VisualEditor or Parsoid, how to further investigate and fix it? Wikitech-l mailing list Wikitech-l@lists.wikimedia.org

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-11 Thread Bjoern Kahl
Dear Scott dear All, Am 11.08.14 um 11:54 schrieb C. Scott Ananian: What could cause this behavior and how should I configure my system to prevent the deadlocks? If this is a Bug in either MediWiki or the VisualEditor or Parsoid, how to further investigate and fix it? Wikitech-l

[Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-10 Thread Bjoern Kahl
Dear All, I need some help tracking down a DB deadlock on a single-server, private Wiki installation running latest MediaWiki download from http://www.mediawiki.org/wiki/Download I have been referred to this mailing list from #mediawiki at irc.freenode.org, thanks for the pointer!

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-10 Thread Gabriel Wicke
On 08/10/2014 04:10 PM, Bjoern Kahl wrote: What could cause this behavior and how should I configure my system to prevent the deadlocks? If this is a Bug in either MediWiki or the VisualEditor or Parsoid, how to further investigate and fix it? In case this is a private wiki: Did you set

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-10 Thread Bjoern Kahl
Am 10.08.14 um 20:52 schrieb Gabriel Wicke: On 08/10/2014 04:10 PM, Bjoern Kahl wrote: What could cause this behavior and how should I configure my system to prevent the deadlocks? If this is a Bug in either MediWiki or the VisualEditor or Parsoid, how to further investigate and fix it?

Re: [Wikitech-l] DB deadlock on Mediawiki 1.23.2 with VisualEditor and Parsoid

2014-08-10 Thread C. Scott Ananian
What seems like a deadlock may in fact be parsoid timing out while trying to connect to your local wiki's API end point. We have had some users report problems of this sort which were caused by their firewall or access control setup. You might want to verify that the API end point for your local