Extension talk:Scribunto

Jump to: navigation, search

About this board

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL

Cannot create process: proc_open: failed to open stream: Permission denied

2
Summary last edited by Jamal22066 02:12, 20 September 2017 1 day ago

The parent directory needs write permissions.

If you do not want to give the entire parent directory write permissions for security reasons, change the errorlog file path to /tmp/errorfile.log. It should look like this:

$wgScribuntoEngineConf['luastandalone']['errorFile'] = "C:/tmp/errorFile";
Stromoxpage (talkcontribs)

I'm trying to use Scribunto for Template:Navbox

The error I'm getting:

Lua error: Cannot create process: proc_open(/usr/share/webapps/mediawiki/extensions/Scribunto/errorFile): failed to open stream: Permission denied

The LocalSettings.php lines:

require_once "$IP/extensions/Scribunto/Scribunto.php";

$wgScribuntoDefaultEngine = 'luastandalone';

$wgScribuntoEngineConf['luastandalone']['errorFile'] = "$IP/extensions/Scribunto/errorFile";

And the permissions:

$ ls -l extensions/Scribunto/

total 96

-rw-r--r-- 1 root root 19917 Nov 18 19:15 COPYING

-rw-r--r-- 1 root root   609 Nov 18 19:15 Gruntfile.js

-rw-r--r-- 1 root root  2793 Nov 18 19:15 Scribunto.magic.php

-rw-r--r-- 1 root root  8111 Nov 18 19:15 Scribunto.namespaces.php

-rw-r--r-- 1 root root  9437 Nov 18 19:15 Scribunto.php

drwxr-xr-x 2 root root  4096 Nov 18 19:15 common

-rw-r--r-- 1 root root   702 Nov 18 19:15 composer.json

-rw-r--r-- 1 root root  3945 Nov 18 19:15 composer.lock

drwxr-xr-x 5 root root  4096 Jan  9  2016 engines

-rwxrwxrwx 1 root root     0 Feb 26 23:44 errorFile

-rw-r--r-- 1 root root   278 Nov 18 19:15 gitinfo.json

drwxr-xr-x 2 root root  4096 Nov 18 19:15 i18n

drwxr-xr-x 2 root root  4096 Nov 18 19:15 modules

-rw-r--r-- 1 root root   276 Nov 18 19:15 package.json

-rw-r--r-- 1 root root   505 Nov 18 19:15 phpcs.xml

drwxr-xr-x 3 root root  4096 Jan  9  2016 tests

drwxr-xr-x 3 root root  4096 Nov 18 19:15 vendor

-rw-r--r-- 1 root root    48 Nov 18 19:15 version

Do you know what's wrong?

Stromoxpage (talkcontribs)

Setting the parent directory permissions to 777 will work. Maybe moving the log to a directory owned by the web server's process owner also?

Reply to "Cannot create process: proc_open: failed to open stream: Permission denied"
2002:43F4:3186:1234:4D53:5039:7DA7:BDF7 (talkcontribs)

I am trying to update from LuaSandbox 2.0.14-alpha to 2.0.15-alpha. I updated the code using git and than ran

phpize && ./configure && make && sudo make install

but it still shows that I'm on 2.0.14-alpha. How can I fix this? I did restart apache.

Legoktm (talkcontribs)

How did you install LuaSandbox originally? Did you put the newly generated luasandbox.so file in the right place?

24.39.1.139 (talkcontribs)

I followed the instructions on this page.

Alex Mashin (talkcontribs)

Check, if PHP loads the extension from the directory, where it was compiled to.

MacFan4000 (talkcontribs)

It seems to be loaded correctly. Any other ideas?

Reply to "LuaSandbox Update"

How to nominate a module for speedy deletion?

2
Liuxinyu970226 (talkcontribs)

I doubt just inserting {{delete}} in "the header of" codes shall be helpful...

Maybe I should create its /doc subpage with that?!

Mr. Stradivarius (talkcontribs)

You're right - leaving the template on the module itself won't add the module page to the relevant category, so doing that won't help. Instead you could put it on the /doc page or the talk page, and explain that it is the module itself that you want deleted. Or you could leave a request on the relevant admin noticeboard. As far as I'm aware, those are the best solutions available at the moment.

Reply to "How to nominate a module for speedy deletion?"
Negative24 (talkcontribs)

So I'm getting the very common error "The lua binary (/home/u249147388/public_html/testing/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua) is not executable" but I did mark the executable as executable (with chmod code 755). For some reason the error still keeps coming up when the executable does have the executable flag. Any ideas? Could it be an annoying noexec flag somewhere? I'm running MediaWiki version 1.22.7 and Scribunto for MW 1.22. Thanks.

Wmat (talkcontribs)

What does

ls -l 

say for that file?

Negative24 (talkcontribs)

ls -l output:

-rwxr-xr-x 1 u249147388 u249147388 195476 Jun  4 17:18 lua
Anomie (talkcontribs)
Could it be an annoying noexec flag somewhere?

That would be my guess.

Negative24 (talkcontribs)

I guess it is. I'll be switching to a new hosting company anyways because this one also doesn't support proc_open which is needed for many scripts.

Elia1995 (talkcontribs)

I got the same error, although I even set "executable" to the whole extensions folder and subfolders.

Alex Mashin (talkcontribs)

Try to run your /home/u249147388/public_html/testing/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua from command line.

Also, check if the partition where this file is situated is mounted with noexec option (/etc/fsab).

Reply to "Lua not executable"

Anyone could help me out with Scribunto? (Windows 10)

6
Justgabs (talkcontribs)

Hello. I am completely new to this, and do not have much experience on this matter, I know you are required to install Scribunto in order to implement infoboxes such as personality, country, organization etc.

I believe that someone who has already used Scribunto could help me out with the installation much better than the already given guideline.

Everything I have set up for now is the Wiki itself, added the CSS and the JS to their respective pages. Nothing more.

Thanks!

PS: I have installed and added the extension to the extensions folder, and have added the code at the end of LocalSettings.

require_once "$IP/extensions/Scribunto/Scribunto.php"; $wgScribuntoDefaultEngine = 'luastandalone';

Anything else must be done?

Justgabs (talkcontribs)

So after doing this, I have downloaded the Template:infobox and tried to import it through Special:Import.

It wouldn't load it and it showed me this error.

Fatal error: Maximum execution time of 120 seconds exceeded in C:\xampp\htdocs\mediawiki\extensions\Scribunto\engines\LuaStandalone\LuaStandaloneEngine.php on line 510

Why so?

42.99.164.54 (talkcontribs)

Hi,

I am having the same issue. May I know how did you solve the issue?

Many thanks.

207.250.18.198 (talkcontribs)

Same issue here, but I am running Windows Server 2012 with Apache 2.4

216.187.65.149 (talkcontribs)

I'm having a similar problem as well on server 2008R2 running IIS. Unfortunately, it looks like nobody knows the answer. :(

Alex Mashin (talkcontribs)

Is Lua installed at all? Also, is $wgScribuntoEngineConf['luastandalone']['luaPath'] equal to the path to your Lua binary? And does that binary run when started manually?

Also, you could try to compile and use luasandbox.

Reply to "Anyone could help me out with Scribunto? (Windows 10)"

Importazione non riuscita: The lua binary (/membri/themagotuxwiki/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua) is not executable with all permissions set as "executable"

7
Elia1995 (talkcontribs)

Hello, today I created my brand new wiki and everything went fine until I created my first character page.

I looked on Google on how to import templates and I tried to import the Template:Infobox from wikipedia, but it gave me an error asking me for some scrubunto extension, so I looked on Google and found a guide here on how to install it, I downloaded the one for my version, wich is 1.29, I then extracted it with 7zip and uploaded on altervista with Filezilla.

I then set up the LocalSetting.php file to make it load up and when I tried to import the template again I got this error:

"Importazione non riuscita: The lua binary (/membri/themagotuxwiki/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua) is not executable."

at that point I went on my Filezilla and I changed the permissions of the whole folder structure of "Extensions" to enable execute, at that point I thought "well, since now the permissions are ok, it must work, right ?" No, wrong, when I tried to import the template again, I got that same error again !!!

I checked the permissions of the extensions folder and everything, "read", "write" and "execute" are checked as well as "recursive" and "all files and subfolders".

I created my wiki on the host Altervista, on which I've been making sites for a lot of years now (but I never created a wiki there until today).

I basically want the template:infobox to work so I can make the characters pages with the character's name, role and all other stuff on the right as well as the picture with the description, you know, that rectangular thing with all the character's info that is on every wikipedia page of any character.

Elia1995 (talkcontribs)

[http://themagotuxwiki.altervista.org/index.php?title=TheMagoTux|This is the page], as you can see it says "Missing module "infobox" in the beginning.

EDIT: now the page just gives away the error directly.

Here's a screenshot of the permissions of that lua file in particular: https://image.prntscr.com/image/Esib92WcTISvhNt2aTOiyQ.png

DHillBCA (talkcontribs)

It sounds like you need to add something like the following to your wiki: https://en.wikipedia.org/wiki/Module:Infobox

Elia1995 (talkcontribs)

That's exactly what I'm trying to import: Template:Infobox and the module:infobox, but when I try to import them, I get that lua execution error nonetheless I have the "execute" permissions on that file.

Here's a screenshot: https://image.prntscr.com/image/ZDHA_4ZgQzSF0WJ9WMxIjQ.png

Jackmcbarn (talkcontribs)

Check that exact file. Don't count on the folder to propagate the settings down. If you check that and it's executable too, make sure you're not on a noexec filesystem or under SELinux restrictions.

Elia1995 (talkcontribs)

The actual exact file is set as "executable".

How do I check if the host uses a noexec filesystem ?

Alex Mashin (talkcontribs)

Check mount options in /etc/fstab.

Reply to "Importazione non riuscita: The lua binary (/membri/themagotuxwiki/extensions/Scribunto/engines/LuaStandalone/binaries/lua5_1_5_linux_64_generic/lua) is not executable with all permissions set as "executable""
80.182.12.56 (talkcontribs)

It is possible install lua on shared host?

Reply to "Lua on shared host"

Intensively used Module:Syrian_Civil_War_detailed_map stops displaying villages from +- line 2700

3
Niele~enwiki (talkcontribs)

Hi,

I had to split the intensively used Module:Syrian_Civil_War_detailed_map into a detailed map and an overview map.

Because the huge middle eastern conflict map could no longer include the whole detailed map because it had become to large.

After a lot of work Module:Syrian_Civil_War_detailed_map now successfully inlcudes Module:Syrian_Civil_War_overview_map with all the large towns and strategic places and the huge middle eastern conflict map succesfully includes the new Module:Syrian_Civil_War_overview_map instead of the Module:Syrian_Civil_War_detailed_map

Yet a new problem occured with the Module:Syrian_Civil_War_detailed_map that I don't understand can't solve.

All villages after +- line 2700 won't display. While before it displayed more than 7000 lines.

Can anyone look at it and try to solve it?

The module is intensively monitored by large amount of people and it should be remain out of fully working order for to long.

Kind regards,

Anomie (talkcontribs)

You'd probably get better help asking at en:Wikipedia talk:Lua.

Niele~enwiki (talkcontribs)

Thanx, I posted it there and emailed some users.

Reply to "Intensively used Module:Syrian_Civil_War_detailed_map stops displaying villages from +- line 2700"
Gharryh (talkcontribs)

I am trying to import a xml and get this error screen message:

Warning: require_once(/home/harry-arends.nl/public_html/mat54_Wiki/extensions/AdaptiveThumb/AdaptiveThumb.php): failed to open stream: No such file or directory in /home/harry-arends.nl/public_html/mat54_Wiki/LocalSettings.php on line 305

Fatal error: require_once(): Failed opening required '/home/harry-arends.nl/public_html/mat54_Wiki/extensions/AdaptiveThumb/AdaptiveThumb.php' (include_path='/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/pear_exception:/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/console_getopt:/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/pear-core-minimal/src:/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/mail_mime:/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/mail_mime-decode:/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/net_socket:/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/net_smtp:/home/harry-arends.nl/public_html/mat54_Wiki/vendor/pear/mail:.:/usr/share/php') in /home/harry-arends.nl/public_html/mat54_Wiki/LocalSettings.php on line 305

Following your instructions i downloaded the zip and moved the unpacked files in the extension folder and added this:

##added 24042017

require_once "$IP/extensions/Scribunto/Scribunto.php";

$wgScribuntoDefaultEngine = 'luastandalone';

to my localsettings file. And then the wiki produces only erors and stops working. Had to remove localsetting entry to get it working again GRMBLE GRMBLE NOT FUNNY

What could be wrong as i am not a programmer but just a guy to get a wiki up and running

PS I am using MW1.

Jackmcbarn (talkcontribs)

Those errors seem to be about the AdaptiveThumb extension. Why do you think they are related to Scribunto?

Reply to "Simple user gets stuck"
CalNation (talkcontribs)

Giving the length of this page and how recurring the problems that exist here, are the extension devs (all from WMF I believe) working on a way to make it easier (not by way of a colossal tool like vagrant)?

Mr. Stradivarius (talkcontribs)

Judging from Scribunto's board on Phabricator, I don't believe there's any such effort at the moment. Patches welcome. :)

Jackmcbarn (talkcontribs)

Most of the problems people have here are either from not correctly following the instructions we already have, or from trying to use a stupidly locked-down Web host. Neither of those are really things that we can fix.

Reply to "Scrabblunto"