Nope! On Wed, Jan 26, 2011 at 3:29 PM, Roberto De Ioris <[email protected]> wrote:
> > Il giorno 26/gen/2011, alle ore 10.51, km ha scritto: > > > > > > So I tried to setuid to www-data (33) and then run the same > > The dir permissions of my django project dir, "/home/km/myproject" are > km:www-data recursively. > > > > $ sudo uwsgi --uid www-data -x /home/km/myproject/uwsgi.xml > > [uWSGI] parsing config file /home/km/myproject/uwsgi.xml > > > > The /var/log/cherokee.error log says > > ################################ > > *** Starting uWSGI 0.9.6.6 (32bit) on [Wed Jan 26 15:04:04 2011] *** > > compiled with version: 4.4.5 > > Python version: 2.6.6 (r266:84292, Sep 15 2010, 16:02:57) > > [GCC 4.4.5] > > uWSGI running as root, you can use --uid/--gid/--chroot options > > setuid() to 33 > > your memory page size is 4096 bytes > > allocated 412 bytes (0 KB) for 1 request's buffer. > > binding on TCP port: 3009 > > your server socket listen backlog is limited to 64 connections > > initializing hooks...done. > > application 0 () ready > > setting default application to 0 > > spawned uWSGI master process (pid: 11479) > > spawned uWSGI worker 1 (pid: 11481) > > all ok here, uWSGI has started successfully > > > invalid request block size: 21573...skip > > ############################### > > (I have also tried to access 127.0.0.1:3009 in browser with no display > but at the end of the logs, I notice "invalid request block size: 21573... > skip" line.) > > uWSGI does not speak http by default so you cannot connect to it with a > browser. > If you want do do it add <http>:port</http> to the configuration (but this > is useful > only for testing) > > Now you configuration is right and you can move to the cherokee side: > > add a new REMOTE (not local) source pointing to the uWSGI address and it > should work. > > yes, having the command like invokation of wsgi (above), I have set Source Type to Remote. It fails!. After that remove the REMOTE source and a LOCAL one with the uwsgi command > line. > > ya i have tried copying the same command (uwsgi -x /home/km/myproject/uwsgi.xml) to the Interpreter field and then update and run. but no change have even tried setting "Execute as User" to www-data OR even uwsgi to /usr/local/bin/uwsgi also fails. somehow the uwsgi fails to get started from cherokee-admin interface as I dont see any output for ps -e |grep uwsgi when I use Local/Remote Interpreter modes. (I am using django 1.2.4 + cherokee 1.0.18 + uswgi 0.9.6.6) > If it does not work it is a simple permission problem you can easily so regards, KM > lve. > > -- > Roberto De Ioris > http://unbit.it > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
