Shouldn't we detect that? Possibly display a message like 'error cannot write to filesystem'? I have been bitten by this one before on a poorly configured shared hosting setup.
On Jan 6, 1:28 am, Massimo Di Pierro <[email protected]> wrote: > You will not finding anything at tha apache log error. This is a > web2py error and it is indeed its failure to write to the filesystem. > > On Jan 5, 3:30 pm, Magnitus <[email protected]> wrote: > > > > > > > > > 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 <[email protected]> > > 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")?
