I wanted to mail back and explain what the solution was here. I had mistakenly put the 'home' configuration variable in the config pointing at the base directory of the django project. Once I removed that everything worked fine.
Thanks for the help Roberto! On Jun 22, 2011, at 8:47 AM, Roberto De Ioris wrote: > >> Hi, I tried to send this before but it doesn't seem to have ever been >> posted to the list. If I'm double posting, please excuse me - I couldn't >> find it in the archives. >> >> Hi, I'm using the following uwsgi.ini: >> >> [uwsgi] >> home=/data/syseng/ebadmin >> module=ebadmin >> socket=127.0.0.1:10000 >> pythonpath=/data/syseng/ebadmin/wsgi >> processes=1 >> max-requests=1000 >> listen=256 >> master=false >> reload-on-as=512 >> reload-on-rss=128 >> #logto=/var/log/uwsgi/uwsgi.log >> buffer-size=32768 >> >> When I launch uwsgi, it cannot find the os library. Running an strace, it >> appears that uwsgi seems to believe that the only paths it has are the >> paths specified by the pythonpath attributes. Is that expected? Does >> uwsgi not load the default python paths, so I need to load them manually >> in order to access modules like os and sys? >> >> I'm running uwsgi 0.9.7.2 on Ubuntu 10.04LTS with Python 2.6.5. >> >> Thanks! >> >> -- >> Michael Barrett >> [email protected] >> >> >> > > There should be no differences in pythonpath between a standard python > invocation and a uwsgi one (except for the --no-site option). > > Probably there is something wrong with your venv. > > Can you post the full uWSGI startup log ? > > Thanks > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi -- Michael Barrett [email protected] _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
