Hello Marin, sorry for the late reply. I don't have your e-mail (this list doesn't show e-mails), but I am also not sure I can provide a lot more extra info on this.
Did you manage to look into it? Did you find anything? Thanks! Tamas On Friday, March 8, 2013 4:00:24 PM UTC+1, Marin Pranjić wrote: > > Would you mind emailing me the details? > I won't promise, but I plan to look into it next week. > > Dana petak, 8. ožujka 2013. 15:49:42 UTC+1, korisnik Tamas napisao je: >> >> >> >> On Friday, March 8, 2013 3:16:25 PM UTC+1, Marin Pranjić wrote: >>> >>> True, but... Apache is not raising errors, web2py is. The error message >>> is strange. At least we could have a nicer error if this can't be fixed. >>> However in my example, both instances work until i try to log in. I can >>> use the site without database i/o. Both instances work. >>> >>> Now, why would web2py (1) raise an exception when working with database >>> (2) because the apache (3) configuration is bad ? >>> >>> Sometimes the testing instance fails on login, sometimes it is >>> production instance... >>> >>> I'd like to see more about Tamas's problem. >>> >>> >> Well, we're running a very busy WSGI Python sctipt alongside a few web2py >> instances, and just like with your setup the only error that happens is >> when we try to log in on a w2p instance that uses the same mysql database >> as the other WSGI script. >> >> I've e-mailed Massimo with more details a couple of months ago, and he >> promised to look into the problem, but he never checked back, and my >> further inquiries had no answer, so I guess it's not an easy fix :( >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
