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. Scribunto is a problem child to work thru. If i didn't need the template support from Wikipedia I would scrub it completely, that , however is not an option. What info can I supply that will illuminate this situation. I really need some help. I'll post what ever you need or mail it directly. Also the site is up so you may look at it directly, though it is very incomplete at present. Thanks John
Your wiki has some serious spam issues.
On Wed, Nov 6, 2013 at 6:59 PM, John W. Foster jfoster81747@gmail.comwrote:
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. Scribunto is a problem child to work thru. If i didn't need the template support from Wikipedia I would scrub it completely, that , however is not an option. What info can I supply that will illuminate this situation. I really need some help. I'll post what ever you need or mail it directly. Also the site is up so you may look at it directly, though it is very incomplete at present. Thanks John
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On Wed, 2013-11-06 at 19:50 -0500, John wrote:
Your wiki has some serious spam issues.
WOW. Thanks for the tip. I actually am setting up this wiki for the first time on a remotely hosted server that is actually open to the public. I recon I have a lot to learn. I had no idea there was all the crap that was put on the wiki by spammers. I've cleared off several thousand of the inactive accounts, BUT I still have several thousand of them that are still active that need to be removed. I also set up a series of verifications that require e-mail and captchas to get involved as an editor and to join the wiki as a member. I will refine these as best as I can before I reopen it to membership. Any other pointers are really appreciated.
Thanks John
On 11/13/2013 11:27 PM, John Foster wrote:
On Wed, 2013-11-06 at 19:50 -0500, John wrote:
Your wiki has some serious spam issues.
Any other pointers are really appreciated.
Could you please try out the extension I'm working on: https://www.mediawiki.org/wiki/Extension:BlockandNuke.
It will mass delete pages created by non-whitelisted users, block their IP addresses, and, if you have UserMerge installed, it will merge their account into the "Spammer" user.
Let me know if you try it or if you have trouble with it.
Mark.
On Thu, 2013-11-14 at 09:37 -0500, Mark A. Hershberger wrote:
On 11/13/2013 11:27 PM, John Foster wrote:
On Wed, 2013-11-06 at 19:50 -0500, John wrote:
Your wiki has some serious spam issues.
Any other pointers are really appreciated.
Could you please try out the extension I'm working on: https://www.mediawiki.org/wiki/Extension:BlockandNuke.
It will mass delete pages created by non-whitelisted users, block their IP addresses, and, if you have UserMerge installed, it will merge their account into the "Spammer" user.
Let me know if you try it or if you have trouble with it.
Mark.
----------------------------------- I already tried to download & install it, but all I got was an empty directory. I'm not comfortable with downloading the separate files from the git hub but I will try it. The extension distributor does not send the complete series of files, just the empty directory. Update: Well that was a bust; it inserted a copy of the git hub page into my main page and into the top of the Special:Pages page also I noticed the whitelist.txt was an HTML page that seemed to be a form of some kind. At any rate I'll try it out when its a bit farther along.
Now about scripy--ban.php-- any tips.
On 11/14/2013 02:41 PM, John Foster wrote:
Well that was a bust
Well, your comments are helpful. I'll put the extension in gerrit so those links work.
I noticed the whitelist.txt was an HTML page that seemed to be a form of some kind.
As the filename implies, this is just a plain text file with usernames that you want whitelisted one per line. I do need to create a Special page as well as a couple of way to make it easy to update the whitelist.
Now about scripy--ban.php-- any tips.
This script provides a command-line equivilant to the functionality you'll find on [[Special:Blockandnuke]]. I just committed some fixes to github for this special page. You can get a fresh download from here: https://github.com/hexmode/mediawiki-block-and-nuke/archive/master.zip
Mark.
On Thu, 2013-11-14 at 21:59 -0500, Mark A. Hershberger wrote:
On 11/14/2013 02:41 PM, John Foster wrote:
Well that was a bust
Well, your comments are helpful. I'll put the extension in gerrit so those links work.
I noticed the whitelist.txt was an HTML page that seemed to be a form of some kind.
As the filename implies, this is just a plain text file with usernames that you want whitelisted one per line. I do need to create a Special page as well as a couple of way to make it easy to update the whitelist.
Now about scripy--ban.php-- any tips.
This script provides a command-line equivilant to the functionality you'll find on [[Special:Blockandnuke]]. I just committed some fixes to github for this special page. You can get a fresh download from here: https://github.com/hexmode/mediawiki-block-and-nuke/archive/master.zip
Mark
Thanks!!!! OK I have it installed and went thru the process of using it with these results. It did seem to locate and identify all the users except those that I placed in the whitelist.txt file..good so far. Then the second part the actual banning seems to be still running after about 7 hours. I ran top and seems apache2 owner www-data has recurring processes so I guess its still running. I'm just gonna leave it as there were actually thousands of these crap members with a User: page for each of them and actual pages/crap articles for some. John
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.
On Wed, Nov 6, 2013 at 6:59 PM, John W. Foster jfoster81747@gmail.comwrote:
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. Scribunto is a problem child to work thru. If i didn't need the template support from Wikipedia I would scrub it completely, that , however is not an option. What info can I supply that will illuminate this situation. I really need some help. I'll post what ever you need or mail it directly. Also the site is up so you may look at it directly, though it is very incomplete at present. Thanks John
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
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.
Have you tried following the instructions at https://www.mediawiki.org/wiki/Extension:Scribunto#Troubleshooting ?
"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.
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.
-- Tim Starling
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
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
On 14/11/13 15:40, John Foster wrote:
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)
Have you set the memory limit to something lower than the default?
-- Tim Starling
On Fri, 2013-11-15 at 10:05 +1100, Tim Starling wrote:
On 14/11/13 15:40, John Foster wrote:
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)
Have you set the memory limit to something lower than the default?
-- Tim Starling
Currently I have the php memory limit set at 1.5 Gb. The system has more than that in real hardware memory. I don't know of any other memory limit settings for mediawiki. If I'm missing something let me know. OS is Debian Linux old stable running on a remotely hosted VPS server with only command line access. Apache2, MySql, Xeon quad CPUs with 2048MB ram allocated to the VPS.
BTW: with Scribunto commented out of LocalSettings.php the server/mediawiki seems to run fine. Except of course where I've imported a template with {{invoke..... in it. I would disable it entirely if I knew what to replace that call with LOL. John
On 15/11/13 12:01, John Foster wrote:
On Fri, 2013-11-15 at 10:05 +1100, Tim Starling wrote:
On 14/11/13 15:40, John Foster wrote:
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)
Have you set the memory limit to something lower than the default?
-- Tim Starling
Currently I have the php memory limit set at 1.5 Gb. The system has more than that in real hardware memory. I don't know of any other memory limit settings for mediawiki. If I'm missing something let me know.
The relevant setting is $wgScribuntoEngineConf['luastandalone']['memoryLimit']. It is 50MB by default. But it's a virtual memory limit, not a physical memory limit, which means that it needs to include enough space for shared libraries. The error message you gave suggests that it is hitting the memory limit while bash is starting up, it doesn't even get as far as running Lua.
Could you try running this under bash:
ps -o vsize $$
And tell us what the result is?
-- Tim Starling
mediawiki-l@lists.wikimedia.org