I wasnt thinking about removing them permanently. If you can temporarily disable all other extensions and confirm that the issue is solely with Scribunto that would make troubleshooting easier. I know quite a few wikis that have it enabled without issue. Isolating the extension by disabling all others makes sure that there isnt some previously unknown compatiblity between Scribunto and another extension. From the error message you provided it sounds like its a RAM issue, which could be caused by either a server setting being set too low, or misconfigured extensions.
On Wed, Nov 13, 2013 at 11:40 PM, John Foster jfoster81747@verizon.netwrote:
On Thu, 2013-11-07 at 16:30 +1100, Tim Starling wrote:
On 07/11/13 10:59, John W. Foster wrote:
Still trying to get rid of these Lua/Scribunto errors: trying to import .xml files.
Import failed: Lua error: Internal error: The interpreter exited with status 2.
I rebuuilt the entire website from the ground up "AGAI" trying to get these to work with basically the same results.
Sure, do the same thing twice, get the same results. Computers are predictable like that.
Site was hacked and completely destroyed as in erased by a vandal. Had to rebuild & start over & I've added a crap load of protection. Just naive on my part.
Have you tried following the instructions at https://www.mediawiki.org/wiki/Extension:Scribunto#Troubleshooting ?
I have tried those instructions with no improvements.
"The interpreter exited with status 2" is not a very helpful error message. You need to set $wgScribuntoEngineConf['luastandalone']['errorFile'] to get useful error output, as described on that page.
This is the error messages in that log that I created per your suggestion. /var/www/extensions/Scribunto/engines/LuaStandalone/lua_ulimit.sh: xmalloc: ../bash/subst.c:3503: cannot allocate 381 bytes (32768 bytes allocated) /var/www/extensions/Scribunto/engines/LuaStandalone/lua_ulimit.sh: xmalloc: ../bash/subst.c:3503: cannot allocate 381 bytes (32768 bytes allocated)
On 07/11/13 14:57, John wrote:
I was talking a look, my first thought would be to comment out all extensions except Scribunto, reboot the webserver and see if the issue persists. Given the large number of extensions you have active the best thing to do is remove those as a source factor.
It's extremely unlikely that either of these measures would make any difference.
I'm with Tim on this. The other extensions are not responsible for the error messages that say Scribunto is the issue. Also I NEED those other extensions along with some that are yet to be installed, in order for the wiki to work as required. Please keep in mind that I already have this wiki running on a local server albeit on version 1.19xx SANS SCRIBUNTO & it works OK.
-- Tim Starling
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l