Open Microscopy Environment

Well we have restarted numerous times since the problem popped up with no change in behavior. I rechecked the time/date on the server and it is within a minute of the time on my machine from where I can replicate the problem.

I honestly have exhausted all the avenues I can think of. What you can try would be to backup the database and replace it with a new one to see if your problem is server related; which I can't see it being but anything is possible at this point I suppose. What's in your bin/omero config get?

Thanks Chris. As it happens, Bernhard Holländer found the solution, which he mentioned in a thread on the ome-users mailing list today.

Essentially the problem was that the Django cache folder in /var/tmp/django_cache was owned by the omero Unix user we had set up, rather than being owned by the Apache user (www-data). By renaming this folder and attempting to log in to the web client, OMERO.web successfully recreated the cache owned by www-data and all is well!