> Every now and again there is a "BUG: unable to handle kernel paging > request at virtual address b79b3000", always in the web2py Python > process, and web2py more or less hangs.
Where do you see this error message? On Jul 2, 4:52 am, Rowdy <ro...@netspace.net.au> wrote: > Candid wrote: > > I am using web2py in my organization for internal applications. One of > > the applications uses dedicated instance of web2py (v1.78.1) running > > on dedicated ubuntu server. It connects to our SQL Server 2005 > > database via freetds. It runs with the following parameters: > > > python web2py.py -i ... -p ... -a ... -n 100 -q 100 > > > The application uses connection pool with 50 connections. > > > Recently it has started freezing occasionally. The weird thing is that > > the whole web2py server freezes and basically stops responding, so not > > only you cannot access the app, you cannot even open the admin > > console. Sometimes it starts working again after a few minutes, > > sometimes I have to restart web2py. > > I suspect it has something to with either web server threads not > > getting released or databases connections not getting returned to the > > pool (the latter would not explain why I cannot access admin console > > though). > > > Has anyone had similar issues? Any suggestions on how to troubleshoot > > the problem? Any input would be highly appreciated. > > Greetings, > > I have a web2py application running in 1.76.5 (from source, and haven't > had the chance to test the app in a more recent version of web2py). > > The server is running vanilla Ubuntu 7.10 with all the patches up to > when support and security updates stopped. > > Every now and again there is a "BUG: unable to handle kernel paging > request at virtual address b79b3000", always in the web2py Python > process, and web2py more or less hangs. > > Actually XML-RPC calls timeout, web pages do not load, but the web2py > internal cron keeps working and generating more Python processes (each > of which also seems to hang). > > I need to kill -9 the processes and start it again. > > This did not happen at all during the previous 4 months of development > on the same server, and does not happen at all in another NetBSD-based > server that I have setup as a development/test environment. > > For various other reasons a replacement server is being commissioned at > the moment, so restarting web2py every couple of days suffices for me > for now. > > Rowdy
