So I guess it would be indicative of a lower level issue at a layer below the framework?
I guess its time to dust off those Apache logs then. On Jan 5, 3:42 pm, Kenneth Lundström <kenneth.t.lundst...@gmail.com> wrote: > If I remember right Unknown ticket is displayed when web2py/webserver is > not able to write a ticket into ticket directory. > > Kenneth > > > Hi, > > > some of my users have encountered a weird error on my mock production > > server. > > > They get the following ticket when the first page (login) tries to > > load: > > > Internal error > > > Ticket issued: unknown > > > Rebooting the server fixed the problem, but I'd still like to get some > > insight into what could have gone wrong. > > > When I look in the ticket directory, I don't see any recent ticket. > > > The web2py version I use on the server isn't the most up-to-date > > (1.88.2). > > > With that in mind, would someone have any insight on the type of > > circumstances that would make Web2py behave in the above manner (not > > write an actual ticket and display it to the viewer as "unknown")? > >
