Hi All,
Recently, we've can an issue were Arches users are automatically logged out, generally in the middle of loading the search page.
A few weeks ago I changed from the default CACHE engine that Arches comes with to a database cache, and followed the Django docs for this. Seemed to be working just fine, but it's possible that this caused the issue.
When this forced logout happens, I see this error in e-mail logs:
Report at /mvt/3067ed10-dbaa-11e7-87be-94659cf754d0/8/68/106.pbf
The request's session was deleted before the request completed. The user
may have logged out in a concurrent request, for example.
I've tried a number of new settings having to do with sessions.
For example, storing sessions in the file system like this
SESSION_ENGINE = 'django.contrib.sessions.backends.file'
SESSION_FILE_PATH = '/path/to/dir'
does seems to work and create session objects, but eventually the issue returns. I also tried
'django.contrib.sessions.backends.cache'
'django.contrib.sessions.backends.db_cache'
for the session engine but the issue returns.
For now, I've reverted to all Arches defaults (commented out my CACHE and session-related settings), and the problem is gone for the time being.
At any rate, I'm wondering if others have
1) experienced this issue or something like it, or
2) implemented any of these cache and session engine backends that I mentioned without having this issue.
Thanks,
Adam