Hi Jacco The stack is nginx -> apache with wsgi. nginx caching is turned for some url patterns.
Thanks On Fri, Jan 6, 2012 at 3:50 PM, Jacco Flenter <django-us...@putpixel.nl>wrote: > What kind of software stack are you running? Apache and... or nginx and...? > > > On Fri, Jan 6, 2012 at 10:51 AM, Arun P <arun....@gmail.com> wrote: > >> @Kevin: >> >> The backend used is the default Database backend. >> There are no other projects which share the same domain space. >> >> I guess will have to write a middleware to see what is happening to the >> cookies. >> >> Thanks. >> >> >> On Fri, Jan 6, 2012 at 2:26 PM, Kevin <kveron...@gmail.com> wrote: >> >>> Which backend is storing the session data? If session data is being >>> stored in the cache(which is normally the recommended way), what >>> caching backend are you using? If you are using locmem cache backend, >>> this might be your problem, change the cache backend to something more >>> stable for production. >>> >>> Do you have other Django projects you manage? If so, is this the only >>> project seeing this type of problem, or are other projects also having >>> issues like this as well? >>> >>> There are many variables in what could cause a session to fail. For >>> debugging purposes, write a simple middleware that keeps track of what >>> is going on with the session cookie. Create a debugging app which can >>> store this debugging info to a file or a database table. >>> >>> If all else fails, set-up a foolproof session set-up, store sessions >>> directly into the database or as files in the file system to a >>> directory which you know will not remove any of these files. If you >>> use file-based sessions, you can check the timestamps there to see >>> which ones are becoming stale easily. You can create a django view >>> which can list the directory and it's timestamps for easily watching >>> remotely(be sure to make the view superuser only). >>> >>> On Jan 5, 4:34 pm, Javier Guerra Giraldez <jav...@guerrag.com> wrote: >>> > On Thu, Jan 5, 2012 at 2:35 PM, Dennis Lee Bieber < >>> wlfr...@ix.netcom.com> wrote: >>> > >>> > > That would have to be a very erratic clock setting -- are >>> there >>> > > systems that don't use an NTP server to synchronize the clock? (I >>> think >>> > > all of my computers synchronize on a weekly basis). >>> > >>> > virtual machines can have terribly erratic clock behaviour. over a >>> > minute of error in an hour is not unheard of. of course, most >>> > hypervisors now specifically handle this problem and keep the VM's >>> > clock a lot more stable >>> > >>> > NTP is the solution, but it's not as trivial to do correctly enough as >>> > in real hardware. >>> > >>> > -- >>> > Javier >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> 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. >>> >>> >> >> >> -- >> Digitally, >> Arun Prabhakar >> https://www.facebook.com/digitalpbk >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> 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. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > 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. > -- Digitally, Arun Prabhakar <http://digitalpbk.com> <https://www.facebook.com/digitalpbk> -- You received this message because you are subscribed to the Google Groups "Django users" group. 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.
