as a follow up. are their any issues if i run cherokee as "cherokee-worker"??? IF so what is the command to start it and return back to the main prompt?
If there are issues any other ideas or direction to look in? Thanks, Todd On Wed, Oct 20, 2010 at 6:00 AM, <[email protected]> wrote: > Send Cherokee mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.octality.com/listinfo/cherokee > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cherokee digest..." > > > Today's Topics: > > 1. Re: ror application on cherokee (James) > 2. Re: index.php explicitly required (James) > 3. Re: Cherokee PHP not working -- Using Plugbox Linux a variant > of Arch (Todd Goodman) > 4. Re: Cherokee PHP not working -- Using Plugbox Linux a variant > of Arch (Stefan de Konink) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Oct 2010 17:15:38 -0400 > From: James <[email protected]> > To: [email protected] > Subject: Re: [Cherokee] ror application on cherokee > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > 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 >> > > > ------------------------------ > > Message: 2 > Date: Tue, 19 Oct 2010 17:54:25 -0400 > From: James <[email protected]> > To: Sergio Aguilar Guerrero <[email protected]> > Cc: cherokee <[email protected]> > Subject: Re: [Cherokee] index.php explicitly required > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > You're correct -- it was a combination of both restarting the daemon > (oops! -- I'm off my game today :)) and the browser cache. > > Many thanks! > > -james > > On Tue, Oct 19, 2010 at 5:10 PM, Sergio Aguilar Guerrero > <[email protected]> wrote: >> It maybe your browser cache, try closing the browser and do a reload. >> The Web Developer Toolbar for Firefox has a disable Cache option, that is >> really convenient for these cases. >> >> Sergio >> >> On Tue, Oct 19, 2010 at 2:05 PM, James <[email protected]> wrote: >>> >>> Actually, that fix it. >>> >>> I turned "Final" off and I'm still getting prompted to download the file. >>> >>> -j >>> >>> On Tue, Oct 19, 2010 at 4:56 PM, James <[email protected]> wrote: >>> > Thanks Taher -- forgot to 'reply to all'. >>> > >>> > I appreciate the help! >>> > >>> > -james >>> > >>> > On Tue, Oct 19, 2010 at 3:45 PM, Taher Shihadeh <[email protected]> >>> > wrote: >>> >> Please respond through the mailing-list so that others can search for >>> >> similar problems in the future ;-) >>> >> >>> >> Your problem is that you have defined the PHP rule as final, so the >>> >> List&Send rule can't ever kick in. Thats the rule type that looks for >>> >> indexes. >>> >> >>> >> Regards >>> >> >>> >> On 19/10/10 20:02, James wrote: >>> >>> >>> >>> vserver!1!directory_index = index.html,index.php >>> >>> vserver!1!document_root = /var/www/default.vhost >>> >>> vserver!1!error_writer!filename = /var/log/cherokee/cherokee.error >>> >>> vserver!1!error_writer!type = file >>> >>> vserver!1!logger = combined >>> >>> vserver!1!logger!access!buffsize = 16384 >>> >>> vserver!1!logger!access!filename = /var/log/cherokee/cherokee.access >>> >>> vserver!1!logger!access!type = file >>> >>> vserver!1!nick = default >>> >>> vserver!1!rule!60!encoder!gzip = 1 >>> >>> vserver!1!rule!60!handler = fcgi >>> >>> vserver!1!rule!60!handler!balancer = round_robin >>> >>> vserver!1!rule!60!handler!balancer!source!1 = 1 >>> >>> vserver!1!rule!60!handler!error_handler = 1 >>> >>> vserver!1!rule!60!match = extensions >>> >>> vserver!1!rule!60!match!check_local_file = 1 >>> >>> vserver!1!rule!60!match!extensions = php >>> >>> vserver!1!rule!60!match!final = 1 >>> >>> vserver!1!rule!60!timeout = 30 >>> >>> vserver!1!rule!50!encoder!gzip = allow >>> >>> vserver!1!rule!50!handler = server_info >>> >>> vserver!1!rule!50!handler!type = just_about >>> >>> vserver!1!rule!50!match = directory >>> >>> vserver!1!rule!50!match!directory = /about >>> >>> vserver!1!rule!40!document_root = /usr/lib/cgi-bin >>> >>> vserver!1!rule!40!handler = cgi >>> >>> vserver!1!rule!40!match = directory >>> >>> vserver!1!rule!40!match!directory = /cgi-bin >>> >>> vserver!1!rule!30!document_root = /usr/share/cherokee/themes >>> >>> vserver!1!rule!30!handler = file >>> >>> vserver!1!rule!30!match = directory >>> >>> vserver!1!rule!30!match!directory = /cherokee_themes >>> >>> vserver!1!rule!20!document_root = /usr/share/cherokee/icons >>> >>> vserver!1!rule!20!handler = file >>> >>> vserver!1!rule!20!match = directory >>> >>> vserver!1!rule!20!match!directory = /icons >>> >>> vserver!1!rule!10!handler = common >>> >>> vserver!1!rule!10!handler!iocache = 1 >>> >>> vserver!1!rule!10!match = default >>> >>> >>> >> >>> >> >>> >> -- >>> >> [email protected] >>> >> http://unixwars.com/ >>> >> >>> >> >>> > >>> _______________________________________________ >>> Cherokee mailing list >>> [email protected] >>> http://lists.octality.com/listinfo/cherokee >> >> > > > ------------------------------ > > Message: 3 > Date: Tue, 19 Oct 2010 21:32:37 -0400 > From: Todd Goodman <[email protected]> > To: [email protected] > Subject: Re: [Cherokee] Cherokee PHP not working -- Using Plugbox > Linux a variant of Arch > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Team, Thanks for the direction. > > I called the server with this command..... cherokee-worker rather > than cherokee and now it works! Thanks so much. > > As a nooobe can someone one help me understand why? I am new to > cherokee and php..... Pointing me an any direction or a good > resource is helpful. > > Again, thanks, Todd > > > > On Tue, Oct 19, 2010 at 3:02 AM, Stefan de Konink <[email protected]> wrote: >> If that plugbox is an ARM processor, he might hit de same bug as someone on >> IRC. The main issue is that if you start PHP manually everything works, but >> if you make cherokee start PHP it basically never launches. >> >> http://code.google.com/p/cherokee/issues/detail?id=970&q=reporter:stefan%40konink.de >> >> On Tue, 19 Oct 2010, Dennis Clayton wrote: >> >>> From my experience, PHP is not auto configured... Go into the admin and >>> into >>> the config for the default host and make sure PHP is setup in there. ?If >>> not, make sure PHP is installed and you can add support for it using the >>> wizard. >>> >>> On Mon, Oct 18, 2010 at 11:42 PM, Todd Goodman <[email protected]> wrote: >>> >>>> Greetings, >>>> >>>> I am attempting to install the cherokee server and php on a server >>>> using plugbox linux a variant of arch. ? It is a small plugbox >>>> server.... >>>> >>>> >>>> >>>> I get cherokee up fine and can access its splash page as well as the >>>> Cherokee-admin page.... >>>> >>>> However when I attempt to browses a php info page I only get a 503 >>>> error... >>>> >>>> ?.... 503 Service Unavailable ?Cherokee web server 1.0.8 (Arch >>>> Linux), Port 80 .... >>>> >>>> >>>> I beleive php is fine. ?From the terminal when I issue this command: >>>> php-cgi /srv/http/phpinfo.php .... I get a valid PHP page. returned... >>>> >>>> >>>> I am at a loss as to what to look at next? ?Any help would be >>>> appreciated. >>>> >>>> >>>> >>>> -- >>>> TAGoodman.Com >>>> _______________________________________________ >>>> Cherokee mailing list >>>> [email protected] >>>> http://lists.octality.com/listinfo/cherokee >>>> >>> >> > > > > -- > TAGoodman.Com > > > ------------------------------ > > Message: 4 > Date: Wed, 20 Oct 2010 08:36:27 +0200 (CEST) > From: Stefan de Konink <[email protected]> > To: Todd Goodman <[email protected]> > Cc: [email protected] > Subject: Re: [Cherokee] Cherokee PHP not working -- Using Plugbox > Linux a variant of Arch > Message-ID: <[email protected]> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > On Tue, 19 Oct 2010, Todd Goodman wrote: > >> Team, Thanks for the direction. >> >> I called the server with this command..... cherokee-worker rather >> than cherokee and now it works! Thanks so much. >> >> As a nooobe can someone one help me understand why? I am new to >> cherokee and php..... Pointing me an any direction or a good >> resource is helpful. > > I wonder if it is related to a glibc or uclibc implementation without > shared memory/SYSVIPC. But last time I check, the problem was actually in > the forking code that 'mysteriously' failed on that platform. > > > Stefan > > > ------------------------------ > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > > > End of Cherokee Digest, Vol 28, Issue 33 > **************************************** > -- TAGoodman.Com _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
