Before the problem I was using port 8010. The day the problem started I used port 8000. But I've changed ports before without problem.
There was also a kernel upgrade, but I can't imagine that would cause this. Version 1.99.4 from the start. Checked permissions. Cleared browser cache, cookies and remembered passwords. Changed session repository from file to db with "session.connect(request, response, db)" Problem still there this AM. No session file when using a file repository, no record in the db when using the db repository. Any more ideas? On Jan 26, 10:11 pm, Bruno Rocha <[email protected]> wrote: > web2py version was updated? > > permission to /sessions have changed? > > try to clean your browser cache, cookies etc and test again > > > > > > > > > > On Thu, Jan 26, 2012 at 11:55 PM, Cliff <[email protected]> wrote: > > My application was working yesterday. I was able to log in and test. > > > Today, Web2py is not writing a session file. Looking in the sessions > > directory, I have a session file dated the 17th and one dated > > yesterday. > > > No session file dated today, though I am able to log in to the app. > > > The app gives me a ticket when it tries to execute my models, because > > I set certain field defaults based on session values. > > > Here is the traceback: > > > Traceback (most recent call last): > > File "/home/cjk/svpy/gluon/restricted.py", line 204, in restricted > > exec ccode in environment > > File "/home/cjk/svpy/applications/sv/models/e.py", line 147, in > > <module> > > (db.property.org_link==session.auth.user.org_link)) > > AttributeError: 'NoneType' object has no attribute 'user' > > > Anybody got a clue what's going on? > > -- > > Bruno Rocha > [http://rochacbruno.com.br]
