Permissions.
It looks like the user under which  cherokee runs cannot spawn your RoR app.

On 20/10/10 16:25, James wrote:
Bump!

Any thoughts?

-james

On Tue, Oct 19, 2010 at 5:15 PM, James<[email protected]>  wrote:
I found some more interesting information ...hopefully this'll help us
narrow everything down.

If I run /usr/sbin/cherokee manually I can see that the process is
kicked off successfully:

-->8--

~ # /usr/sbin/cherokee
Cherokee Web Server 1.0.8 (Oct 15 2010): Listening on port ALL:80, TLS disabled,
IPv6 enabled, using epoll, 4096 fds system limit, max. 2041 connections,
caching I/O, 30 threads, 68 connections per thread, standard scheduling
policy
PID 5286: launched '/bin/sh -c exec /usr/bin/env
BUNDLE_GEMFILE=/stuff/teambox/Gemfile \ PWD=/stuff/teambox/script
/stuff/teambox/script/server -e development -p 52575' with uid=104,
gid=101, env=inherited

--8<--

So now I go to my.server.com:52575 and it works without any hitches.

It almost seems like the reverse proxy is broken and isn't routing my
HTTP traffic to 127.0.0.1:52575.

Thoughts?

-james

On Tue, Oct 19, 2010 at 4:56 PM, James<[email protected]>  wrote:
Hi,

I have a Ruby on Rails application (www.teambox.com) that keeps
failing with a 502 Gateway error.

Here's a rundown of the (many) hours of troubleshooting I've spent on this:

- runs fine when I'm in /stuff/teambox/script/ directory
- runs fine when I manually execute the Interpreter configuration in cherokee:

(/usr/bin/env BUNDLE_GEMFILE=/stuff/teambox/Gemfile \
PWD=/stuff/teambox/script /stuff/teambox/script/server -e development
-p 52576)

- I've tried using both /usr/bin/env and the Cherokee env variable, no go

- I've su'ed into cherokee user and then run the command (/usr/bin/env
BUNDLE_GEMFILE=/stuff/teambox/Gemfile \ PWD=/stuff/teambox/script
/stuff/teambox/script/server -e development -p 52576) and it works
fine with no issues

I can't really see what's going on in terms of why the application
fails. The logs don't show anything.

There's been a very very similar thread
(http://www.mail-archive.com/[email protected]/msg04278.html)
in the near past; unfortunately none of the solutions seem to work.

Any help would be greatly appreciated; I'm about to rip my hair out. ;)

-james

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee


--
[email protected]
http://unixwars.com/

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to