New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apache/mod_wsgi log object is not associated with a file descriptor #26302
Comments
@Mutantpenguin can you verify if this change is fine for your usage too 👀 don't want to break it again while fixing this. |
@gongomgra you might wanna migrate to nginx + gunicorn setup. We don't test compatibility with Apache/mod_wsgi at all. (maybe we historically supported this? idk) |
Hi @ankush, Thanks for letting us know. We will create an internal task to migrate to the recommended setup. In the meantime, we will keep an eye on the solution of this issue. |
Thanks @ankush for thinking of me! If the current safeguard |
Hi @ankush, I see a new Frappe version have been released recently, but the solution for this issue seems not to be included yet. Do you have any news on this? Thanks! |
Description of the issue
Hello, team. We are facing an issue trying to install and configure ERPNext in a Debian 12 virtual-machine using bench
5.22.3
. Although the ERPNext site gets generated, the website is not available with internal server error through Apache/mod_wsgi. WSGI log showsOSError: Apache/mod_wsgi log object is not associated with a file descriptor
. Seems related to recent changes in__init__.py
.As a test, we implemented the change below and it seems to work. However, we saw this as a hot fix suggestion somewhere else, so we created this ticket for further help. Can you help us to understand what's the issue and how to fix it?
Context information (for bug reports)
Output of
bench version
Steps to reproduce the issue
5.22.3
host_name
tohttp://localhost
insite_config.json
Observed result
Internal server error plus
OSError: Apache/mod_wsgi log object is not associated with a file descriptor
in logs.Expected result
Login page.
Stacktrace / full error message
Additional information
Debian 12.
While looking for other issues affected with the same error message, we found a hot fix suggested here. We tested to update the line 2527 mentioned in the error message to the one below. After that, I was able to generate another site and get to the login page, pass the wizard, and get access to my ERPNext site.
According to Python's docs it contains the original value of stderr at the start of the program.
The text was updated successfully, but these errors were encountered: