Cherokee should be spawning them as user "rails" (as set in the source
config) -- as user rails it works fine being spawned manually from the
terminal. Cherokee doesn't seem to be spawning them at all. I've tried
changing all the permissions to www-data and changing everything in Cherokee
to the default, but Cherokee still doesn't spawn it.

At least I think that's what the problem is, I get Bad Gateway 502 but no
errors in the cherokee.errors log.

I'm fairly sure I must be missing something simple, I just can't see it for
all the tress.

On Tue, Jun 15, 2010 at 3:51 PM, Taher Shihadeh <[email protected]> wrote:

>  Did you try spawning it as the user under which Cherokee is running?
> Seems to me it isn't working that way.
>
>
> On 15/06/10 09:21, Alex Dunmow wrote:
>
>  That is what the information source is. If I copy & paste it into a
>> terminal (same user as it's running as from Cherokee) it works fine.
>
>
>
>>
>>
>> On Tue, Jun 15, 2010 at 3:19 PM, Alvaro Lopez Ortega <[email protected]
>> > wrote:
>>
>>> On 15/06/2010, at 04:11, Alex Dunmow wrote:
>>>
>>> > /usr/share/redmine/script/server mongrel -e production -p 36456
>>> > Which works fine when I run it myself. (And Cherokee uses it fine when
>>> I run it myself)
>>>
>>>  So, does it work if you configure an Information Source to user that
>>> same command?
>>>
>>> --
>>> Octality
>>> http://www.octality.com/
>>>
>>>
>>
>
> _______________________________________________
> Cherokee mailing 
> [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