Forums

My app was working fine, and then in web2py I clicked "toggle breakpoint," which I never used before. Now my site is offline, and the error log shows

2016-07-20 04:25:36,003 :IOError: write error
2016-07-20 04:25:36,004 :Error running WSGI application
Traceback (most recent call last):
  File "/bin/user_wsgi_wrapper.py", line 156, in __call__
    yield response
GeneratorExit

Edit: earlier it would not reload, but now after I reloaded it, it works again. Nevermind :)

That exception is normally ignorable, unless you get a very large number of them (eg. one for most requests). It basically means that your website was trying to send some data back to a browser, but the browser closed the connection before it had finished sending. This happens with most sites from time to time due to general problems sending data over the Internet, people using unreliable connections like cellphones, and so on.

However, if your site suddenly starts running really slowly, then of course people will start disconnecting when loading a page takes a long time so they browse away to a different site, or hit the "stop" button in their browser. So that's when you'll get a lot of them and need to diagnose why things are running slowly.

I'm wondering if adding the breakpoint made your site run super-slowly (maybe because it was stopped at a breakpoint halfway through processing a request?) and so something disconnected...?

It was happening for all requests for maybe 10-15 minutes. For now I'm not going to use the web2py debug feature until I know more how it works.

Sounds like a wise plan. There's a great Google group for web2py, if you haven't seen it -- people tend to be very helpful there.