I believe you only get the per-request logs when you're running the development server (runserver). When you're running in fastcgi mode (and its been a while since I have), you'll only get entries in outlog and errlog if you actually send stuff to stdout and stderr yourself. And THAT will require fiddling with the LOGGING settings.
On Tuesday, December 4, 2012 10:17:59 AM UTC-8, Gontran Magnat wrote: > > Hello, > > I'm running a django app on lighttpd with fastcgi. > For debugging matters I would need the output logs that usually are > displayed on the console. > Because I run my application in a daemonize mode I tried to use the outlog > and errlog options but it did not work. > > Here is the command I run: > > python manage.py runfcgi method=threaded host=127.0.0.1 port=3033 workdir= > /mydir/finderauto_dj/ outlog=out.log errlog=err.log > > > The out.log and err.log files are created but when I access my website, > this should produce this kind of logs: > [03/Dec/2012 23:09:11] "GET /admin/recherches/alert/4/ HTTP/1.1" 200 11844 > > However, both out.log and err.log files remain empty. > > Then I tried to use the daemonize=false option in order to have directly > the output: > > python manage.py runfcgi method=threaded host=127.0.0.1 port=3033 > daemonize=false > > > I get nothing either... > > Anybody for helping me? > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/H5awKm5jdsEJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
