I was able to install Cherokee 1.0.8 with ZERO issues tonight. One thing I noticed is when I run cherokee-admin -b I get this message:
Cherokee Web Server 1.0.8 (Aug 11 2010): Listening on port ALL:9090, TLS disabled, IPv6 enabled, using epoll, 4096 fds system limit, max. 2041 connections, caching I/O, single thread I know when I was trying to run cherokee-admin in 1.2.2.1 it was saying 80 threads, instead of single thread. Could that be the issue? On Wed, Apr 20, 2011 at 8:59 PM, Christopher McComas < [email protected]> wrote: > I'm totally baffled now. > > I did cherokee-admin -p=9191 to use a different port and I got the same > errors as before. > > [20/04/2011 17:54:44.374] (error) thread.c:247 - Could not create a system > > thread: 'Resource temporarily unavailable' | This is a extremely > unusual error. For some reason > your system could not create a thread while launching the server. You > might > have hit some system restriction. > > [20/04/2011 17:54:44.374] (critical) server.c:660 - Could not create an > > internal server thread | This is a extremely unusual error. For some > reason > the server could not create a thread while launching the server. > > I've been playing with Cherokee in development for a while now, being a > former Django guy. I really want to use it on my new (ve) at MediaTemple for > a successful blog I run, but I think it'd be much easier to run 1.2.2 > instead of pre 1.0 versions. Also, there are plenty of other (ve) and (dv) > customers at MT that would benefit in finding this solution. > > I can provide any info about my setup anyone needs. Running Ubuntu 10.10 > with the 512MB (ve) at MediaTemple. > > On Wed, Apr 20, 2011 at 8:47 PM, Tony Zakula <[email protected]> wrote: > >> Ah, well I am not sure on that. It sounds right, but I couldn't say if >> that is your Cherokee problem or not. A cherokee committer would be able to >> answer that better. It does seem like it is your resources though. >> >> >> On Wed, Apr 20, 2011 at 7:42 PM, Christopher McComas < >> [email protected]> wrote: >> >>> my ulimt -n is 1024, but if i'm doing math correctly (and multiplying the >>> correct things) 80 threads X 25 connections per thread is more than 1024, is >>> that the issue? >>> >>> >>> On Wed, Apr 20, 2011 at 8:41 PM, Tony Zakula <[email protected]>wrote: >>> >>>> You can edit the config file manually. Someone else on the list may >>>> have better advice, I never really ran into tis issue. As long as you are >>>> careful, you should be able to set the threads down. >>>> >>>> >>>> On Wed, Apr 20, 2011 at 7:34 PM, Christopher McComas < >>>> [email protected]> wrote: >>>> >>>>> When I shutdown Cherokee and run cherokee-admin -b -x I get: >>>>> >>>>> Cherokee Web Server 1.2.2 (Mar 23 2011): Listening on port ALL:9090, >>>>> TLS >>>>> disabled, IPv6 enabled, using epoll, 4096 fds system limit, max. 2041 >>>>> connections, 80 threads, 25 connections per thread, standard scheduling >>>>> policy >>>>> >>>>> Login: >>>>> User: admin >>>>> One-time Password: 03qrajd0acPEJMec >>>>> >>>>> >>>>> Web Interface: >>>>> URL: http://localhost:9090/ >>>>> >>>>> >>>>> I try to login and get a 503 Not Available Error. >>>>> >>>>> Is there a way to lower the 80 threads that's listed? Maybe that's it? >>>>> Isn't that really high? >>>>> >>>>> >>>>> On Wed, Apr 20, 2011 at 8:29 PM, Tony Zakula <[email protected]>wrote: >>>>> >>>>>> Weird. I have run Cherokee in a small ve with no problem. You can >>>>>> shutdown Cherokee and still run the admin. Did you try that? >>>>>> >>>>>> >>>>>> On Wed, Apr 20, 2011 at 7:25 PM, Christopher McComas < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Tony, >>>>>>> >>>>>>> Thanks, followed these instructions and saw this (so I know it's the >>>>>>> updated version) Setting up cherokee-admin (1.2.2-1~lucid~ppa1) ... >>>>>>> >>>>>>> I still get the error in the previous message. >>>>>>> >>>>>>> I've checked the (ve) settings and I should have sufficient room for >>>>>>> theads ~256 so that shouldn't be the issue. >>>>>>> >>>>>>> One thing is once I install Cherokee and it starts on the server my >>>>>>> memory jumps up to around 160% of my allotment. 0.9 did that as well, >>>>>>> but I >>>>>>> could run the admin and change the number of Threads in the advance to 3 >>>>>>> which brought it down to around 25%. >>>>>>> >>>>>>> On Wed, Apr 20, 2011 at 8:13 PM, Tony Zakula >>>>>>> <[email protected]>wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> See below. >>>>>>>> >>>>>>>> On Wed, Apr 20, 2011 at 7:07 PM, Christopher McComas < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Thanks Tony that makes sense. >>>>>>>>> >>>>>>>>> I didn't have anything of consequence on the server yet, so I just >>>>>>>>> wiped it clean back to just the original Ubuntu 10.10 OS. Just to >>>>>>>>> clarify >>>>>>>>> I'd do: >>>>>>>>> >>>>>>>>> apt-get update >>>>>>>>> apt-get upgrade >>>>>>>>> >>>>>>>>> apt-get install python-software-properties >>>>>>>>> >>>>>>>>> add-apt-repository ppa:cherokee-webserver >>>>>>>>> >>>>>>>> >>>>>>>> I do not have my notes with me, but usually, I have to do something >>>>>>>> like sudo apt-get dist-upgrade here to make sure Ubuntu pulls >>>>>>>> version 1.2 >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> apt-get install cherokee >>>>>>>>> >>>>>>>>> ...then get the modules for mod-mysql mod-rrd etc. >>>>>>>>> >>>>>>>>> That should do it? I'm getting ready to attempt it. >>>>>>>> >>>>>>>> >>>>>>>> Hopefully that does it. >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Apr 20, 2011 at 7:58 PM, Tony Zakula <[email protected] >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> When you install the latest version and you have had an older >>>>>>>>>> version installed, you need to make sure the old admin is not >>>>>>>>>> installed. I >>>>>>>>>> think it is something like lib-cherokee-admin and the new admin >>>>>>>>>> package is >>>>>>>>>> cherokee-admin. I had issues with that on a few Ubuntu servers. >>>>>>>>>> Does that >>>>>>>>>> make sense? Check your packages. >>>>>>>>>> >>>>>>>>>> Tony Z >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Apr 20, 2011 at 6:51 PM, Christopher McComas < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> I had installed 1.2.2 on my MediaTemple (ve) but when I had it >>>>>>>>>>> installed I got this error and could not figure out a solution for >>>>>>>>>>> it: >>>>>>>>>>> >>>>>>>>>>> In SHH when I try to start the admin, with Cherokee running I get >>>>>>>>>>> this >>>>>>>>>>> error: >>>>>>>>>>> >>>>>>>>>>> [20/04/2011 13:02:20.879] (error) thread.c:247 - Could not create a >>>>>>>>>>> system >>>>>>>>>>> thread: 'Resource temporarily unavailable' | This is a >>>>>>>>>>> extremely unusual >>>>>>>>>>> error. For some reason >>>>>>>>>>> your system could not create a thread while launching the >>>>>>>>>>> server. You >>>>>>>>>>> might >>>>>>>>>>> have hit some system restriction. >>>>>>>>>>> >>>>>>>>>>> [20/04/2011 13:02:20.879] (critical) server.c:660 - Could not >>>>>>>>>>> create an >>>>>>>>>>> internal server thread | This is a extremely unusual error. For >>>>>>>>>>> some >>>>>>>>>>> reason >>>>>>>>>>> the server could not create a thread while launching the server. >>>>>>>>>>> >>>>>>>>>>> When I run the service cherokee stop command, then run >>>>>>>>>>> cherokee-admin -b I >>>>>>>>>>> get this: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Login: >>>>>>>>>>> User: admin >>>>>>>>>>> One-time Password: N1YK9hGn8oveeJXS >>>>>>>>>>> >>>>>>>>>>> Web Interface: >>>>>>>>>>> URL: http://localhost:9090/ >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> When I go to that I get the login prompt, I enter the information >>>>>>>>>>> and then >>>>>>>>>>> just got a 503 error. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Apr 20, 2011 at 7:47 PM, Tony Zakula < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> You will be miles ahead if you go to the Cherokee site and >>>>>>>>>>>> upgrade to the latest version using the PPA. Look under install >>>>>>>>>>>> in the >>>>>>>>>>>> docs. On Ubuntu, you may have to do a dist upgrade after >>>>>>>>>>>> installing the >>>>>>>>>>>> PPA. It will be easier to answer your questions, and you will >>>>>>>>>>>> have the >>>>>>>>>>>> latest version which has lots of bug fixes and improvements. >>>>>>>>>>>> >>>>>>>>>>>> Tony Z >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Apr 20, 2011 at 6:43 PM, Christopher McComas < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I'm running Cherokee 0.99.39 on Ubuntu 10.10 with MediaTemple's >>>>>>>>>>>>> 512MB (ve). >>>>>>>>>>>>> >>>>>>>>>>>>> I have WordPress 3.1.1 up and running on my default Virtual >>>>>>>>>>>>> Server at mydomain.com. What I am trying to do is setup a >>>>>>>>>>>>> phpBB3 install on the same domain at mydomain.com/forums/. >>>>>>>>>>>>> >>>>>>>>>>>>> I tried to go to Virtual Servers > default > Wizards > Misc > >>>>>>>>>>>>> phpBB3 and enter this information... >>>>>>>>>>>>> >>>>>>>>>>>>> Web Directory: /forums >>>>>>>>>>>>> Source Directory: /var/www/phpBB3 >>>>>>>>>>>>> >>>>>>>>>>>>> It sets up the behavior as a Regular Expression rule type with >>>>>>>>>>>>> this as the Regular Expression: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ^/forums/(config.php|common.php|cache/.*|files/.*|images/avatars/upload/.*|store/.*) >>>>>>>>>>>>> >>>>>>>>>>>>> The Handler is set to HTTP error and the error is 403 Forbidden >>>>>>>>>>>>> >>>>>>>>>>>>> I thought this was wrong (I actually looked and it loaded the >>>>>>>>>>>>> WordPress Page Not found default), so I change it do Rule: >>>>>>>>>>>>> Directory >>>>>>>>>>>>> pointing to /forums and Handler: None with Document Root to >>>>>>>>>>>>> /var/www/phpBB3 >>>>>>>>>>>>> and did a graceful restart and I got a 405 Method Not Allowed >>>>>>>>>>>>> error. I >>>>>>>>>>>>> created Behavior's for /phpBB3/adm/images and /phpBB3/adm/styles >>>>>>>>>>>>> and got it >>>>>>>>>>>>> setup and the Administration Control Panel works, with images, >>>>>>>>>>>>> css, js. But >>>>>>>>>>>>> when I go to mydomain.com/forums I get a 405 Method Not >>>>>>>>>>>>> Allowed again. Do I have to go in manually and figure out which >>>>>>>>>>>>> directories >>>>>>>>>>>>> I need to create a Behavior for, or is there an easier way to do >>>>>>>>>>>>> it? >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Cherokee mailing list >>>>>>>>>>>>> [email protected] >>>>>>>>>>>>> http://lists.octality.com/listinfo/cherokee >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Cherokee mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> http://lists.octality.com/listinfo/cherokee >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Cherokee mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://lists.octality.com/listinfo/cherokee >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Cherokee mailing list >>>>>>>>> [email protected] >>>>>>>>> http://lists.octality.com/listinfo/cherokee >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Cherokee mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.octality.com/listinfo/cherokee >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Cherokee mailing list >>>>>>> [email protected] >>>>>>> http://lists.octality.com/listinfo/cherokee >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Cherokee mailing list >>>>>> [email protected] >>>>>> http://lists.octality.com/listinfo/cherokee >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Cherokee mailing list >>>>> [email protected] >>>>> http://lists.octality.com/listinfo/cherokee >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Cherokee mailing list >>>> [email protected] >>>> http://lists.octality.com/listinfo/cherokee >>>> >>>> >>> >> >> _______________________________________________ >> Cherokee mailing list >> [email protected] >> http://lists.octality.com/listinfo/cherokee >> >> >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
