Forums

Odd recursion error

I have 2 websites that use exactly the same git repo. One works fine and the other one works for a bit, then just seems to time out, then eventually gives a generic pythonanywhere error screen. If I turn debug on, I get the same error screen.

Looking at the server log

2022-06-25 00:27:28 Sat Jun 25 00:27:28 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /logout/ (ip 10.0.0.66) !!!
2022-06-25 00:27:28 Sat Jun 25 00:27:28 2022 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /logout/ (10.0.0.66)
2022-06-25 00:27:28 OSError: write error
2022-06-25 00:28:02 Error running WSGI application
2022-06-25 00:28:02 RecursionError: maximum recursion depth exceeded
2022-06-25 00:28:02   File "/home/conceptpyrota/.virtualenvs/supermarketvirtualenv/lib/python3.9/site-packages/django/core/handlers/wsgi.py", line 132, in __call__
2022-06-25 00:28:02     response = self.get_response(request)
2022-06-25 00:28:02 
2022-06-25 00:28:02   File "/home/conceptpyrota/.virtualenvs/supermarketvirtualenv/lib/python3.9/site-packages/django/core/handlers/base.py", line 143, in get_response
2022-06-25 00:28:02     log_response(
2022-06-25 00:28:02 
2022-06-25 00:28:02   File "/home/conceptpyrota/.virtualenvs/supermarketvirtualenv/lib/python3.9/site-packages/django/utils/log.py", line 241, in log_response
2022-06-25 00:28:02     getattr(logger, level)(
2022-06-25 00:28:02 
2022-06-25 00:28:02   File "/usr/local/lib/python3.9/logging/__init__.py", line 1458, in warning
2022-06-25 00:28:02     self._log(WARNING, msg, args, **kwargs)

and the error log

Jun 25 00:27:28 2022 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /logout/ (ip 10.0.0.66) !!!
2022-06-25 00:27:28 Sat Jun 25 00:27:28 2022 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 306] during GET /logout/ (10.0.0.66)
2022-06-25 00:27:28 OSError: write error
2022-06-25 00:28:02 Error running WSGI application
2022-06-25 00:28:02 RecursionError: maximum recursion depth exceeded
2022-06-25 00:28:02   File "/home/conceptpyrota/.virtualenvs/supermarketvirtualenv/lib/python3.9/site-packages/django/core/handlers/wsgi.py", line 132, in __call__
2022-06-25 00:28:02     response = self.get_response(request)
2022-06-25 00:28:02 
2022-06-25 00:28:02   File "/home/conceptpyrota/.virtualenvs/supermarketvirtualenv/lib/python3.9/site-packages/django/core/handlers/base.py", line 143, in get_response
2022-06-25 00:28:02     log_response(
2022-06-25 00:28:02 
2022-06-25 00:28:02   File "/home/conceptpyrota/.virtualenvs/supermarketvirtualenv/lib/python3.9/site-packages/django/utils/log.py", line 241, in log_response
2022-06-25 00:28:02     getattr(logger, level)(
2022-06-25 00:28:02 
2022-06-25 00:28:02   File "/usr/local/lib/python3.9/logging/__init__.py", line 1458, in warning
2022-06-25 00:28:02     self._log(WARNING, msg, args, **kwargs)
2022-06-25 00:28:02 
2022-06-25 00:28:02   File "/usr/local/lib/python3.9/logging/__init__.py", line 1589, in _log
2022-06-25 00:28:02     self.handle(record)

spammed over and over. Like I mentioned the other site with the same code base works fine. The only difference is the data in the database. Any ideas what I should attempt to determine the problem? I can't tell whats going on from the log apart from some type of recursion error going on somewhere. The only significant thing I added was django_debug_toolbar, but I set debug to False so it wouldn't operate. Could that the the issue?

deleted-user-11511982 | 8 posts | June 25, 2022, 1:31 a.m. | permalink

It looks like you copied only the bits from the server log -- could you share also relevant parts from the error log?

Staff pafk | 3627 posts | PythonAnywhere staff | June 25, 2022, 11:06 a.m. | permalink

Its ok. I removed the django_debug_toolbar app from the installed_apps in settings.py file and now it works correctly. So I assume there is something in django debug toolbar that is not playing nice. Since I would never want to run this in production anyway, I just coded it so it appends to that setting when I run on the local machine instead of simply setting debug=False.

deleted-user-11511982 | 8 posts | June 25, 2022, 12:19 p.m. | permalink

Glad you solved it -- and thanks for sharing the solution!

Staff pafk | 3627 posts | PythonAnywhere staff | June 25, 2022, 4:43 p.m. | permalink

Same thing happened to me. I forgot to remove django_debug_toolbar app when I deployed the app. Thank you

Beloved premium user assignguru | 3 posts | Oct. 21, 2022, 6:38 p.m. | permalink

Glad to hear that you were able to fix it!

Staff fjl | 4968 posts | PythonAnywhere staff | Oct. 22, 2022, 1:26 p.m. | permalink

thanks a bunch for sharing the solution, removing django_debug_toolbar also resolved my problem.

razi | 1 post | Dec. 14, 2022, 3:54 p.m. | permalink

Thanks for sharing this solution, and it worked for me too (django 3.2.25)

Beloved premium user tangbj | 29 posts | Sept. 16, 2024, 9:29 a.m. | permalink

Excellent, thanks for confirming :-)

Staff giles | 12640 posts | PythonAnywhere staff | Sept. 16, 2024, 5:10 p.m. | permalink