Script is set to be executable and the owner the same as Lighty, I assume? Can you post the excerpt of the lighty config where you call that part? Can you re-check the paths?
On Thu, Aug 23, 2012 at 3:32 PM, Adam Bengtsson <[email protected]> wrote: > Problem with paths in what way? The paths I've entered in lighttpd.conf > looks in order and all files are owned by the lighttpd user. > > I've tried putting my non-working web.py-app in the folder of the working > web.py-app (hiding the error-free app) and restarting the server, but I > still get the 127 exit status, so perhaps I've made some mistake in my > Python code? As mentioned previously the app works fine in development, and > the project is really nothing more than the hello world-example... > > //Adam > > Den torsdagen den 23:e augusti 2012 kl. 14:43:49 UTC+2 skrev Primoz Anzur: >> >> From what I gather; error 127 in lighty means problem with paths... Have >> you checked your environment? Does your http user have access to the script? >> >> On Thu, Aug 23, 2012 at 1:20 PM, Adam Bengtsson <[email protected]> wrote: >> >>> I simply cannot get my new web.py app running from lighttpd. I had this >>> problem earlier and wrote about it in a previous post and after some help I >>> discovered my shebang-lines where wrong. >>> >>> This time however the shebangs aren't off, and the error code is also >>> not the same as before (when the shebang was off I got "child exited with >>> status 2", now it's "child exited with status 127"), so I'm really at my >>> wits end as to what the problem might be. >>> >>> The application is the basic Hello World-example, it runs fine from the >>> development server, the lighttpd user is the owner of the file and it is >>> chmoded to be an executable. >>> >>> Is there anyone with some insight into what these different status codes >>> means, particularly 127? >>> >>> //Adam >>> >>> Error log output: >>> >>> 2012-08-23 14:52:15: (log.c.166) server started >>> 2012-08-23 14:52:15: (mod_fastcgi.c.1104) the fastcgi-backend /var/www/ >>> mydomain.com/webpy/**index.py <http://mydomain.com/webpy/index.py>failed to >>> start: >>> 2012-08-23 14:52:15: (mod_fastcgi.c.1108) child exited with status 127 >>> /var/www/mydomain.com/webpy/**index.py<http://mydomain.com/webpy/index.py> >>> >>> 2012-08-23 14:52:15: (mod_fastcgi.c.1111) If you're trying to run your >>> app as a FastCGI backend, make sure you're using the FastCGI-enabled >>> version. >>> If this is PHP on Gentoo, add 'fastcgi' to the USE flags. >>> 2012-08-23 14:52:15: (mod_fastcgi.c.1399) [ERROR]: spawning fcgi failed. >>> 2012-08-23 14:52:15: (server.c.938) Configuration of plugins failed. >>> Going down. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "web.py" group. >>> To view this discussion on the web visit https://groups.google.com/d/** >>> msg/webpy/-/oIJ461dyl2YJ<https://groups.google.com/d/msg/webpy/-/oIJ461dyl2YJ> >>> . >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to webpy+un...@** >>> googlegroups.com. >>> >>> For more options, visit this group at http://groups.google.com/** >>> group/webpy?hl=en <http://groups.google.com/group/webpy?hl=en>. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/webpy/-/KkrviEjg8ekJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/webpy?hl=en. > -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
