the reason I doubt your suggestion: a new request will start a new main thread, and this is _really_ early in that execution....
....maybe if welcome was deleted, and web2py was not restarted after??? I don't know - I would do a ps -axl | grep web2py first; Kill any older ones that may be hanging around unintended; stop and restart web2py second; See if either of those help. On Fri, Jul 24, 2009 at 11:48 PM, Jonathan Lundell <[email protected]>wrote: > On Jul 24, 2009, at 9:38 PM, Yarko Tymciurak wrote: > > On Fri, Jul 24, 2009 at 11:27 PM, Jonathan Lundell <[email protected]>wrote: > >> On Jul 24, 2009, at 9:20 PM, Yarko Tymciurak wrote: >> >> check your processes - make sure you don't have another instance of web2py >> still running somewhere... >> >> >> There's a path in wsgibase that looks like it could cause this behavior if >> the execution environment gets sufficiently messed up: >> > > Here - maybe this will help you read this: (you'll notice a few lines > above, if no 'a' ... application set, then start with 'init'): > > >> >> if not os.path.exists(request.folder): # if we can't find >> the app..... >> if request.application=='init': # and we've >> already tried init, then.... >> request.application = 'welcome' # next try >> welcome.... >> redirect(html.URL(r=request)) # and go there.... >> > > This is the default sequence: of no 'a' (app) specified, then start with > init, and if it fails, then go to 'welcome' > > Make sense now? > > > It made sense already, and if request.folder (or more likely its > progenitors) gets corrupted somehow (I have no theory), then we'd see > something like what David is seeing, even in the absence of an actual > welcome application. > > > - Yarko > > >> >> >> It might be worth looking to see whether that path ever gets taken, and if >> so why. >> >> >> On Fri, Jul 24, 2009 at 10:30 PM, David Watson >> <[email protected]>wrote: >> >>> >>> Hi, >>> >>> I am running tip of the trunk from svn. I have my application in init >>> and deleted the welcome application. I am running on ubuntu server >>> 9.04 on a single core pentium 4. I start web2py with: >>> >>> sudo nohup python web2py.py -p 80 -i 192.168.1.40 -a whatever >>> >>> Everything is fine and the pages are served from init when >>> requesting / as a for instance. >>> >>> Somewhere in a few hours, web2py starts pointing / at /welcome/default/ >>> index. If I restart, then it goes back to serving / against init. >>> >>> I don't think I've done anything wrong. Could this be a bug? >>> >>> Thanks, >>> David >>> >>> >>> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
