#1026100 libapache2-mod-wsgi: Repeated "Fatal Python error: Could not allocate TSS entry" error logged by libapache2-mod-wsgi-py3 #1026100
- Package:
- libapache2-mod-wsgi
- Source:
- libapache2-mod-wsgi
- Submitter:
- Vishwanath Jadhav
- Date:
- 2023-12-22 12:18:11 UTC
- Severity:
- normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Hi Please find the details
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Ans:
services wasn't able to access web-UI with following errors:
/var/log/apache2 have huge log files having errors like :
-Fatal Python Error : Could not allocate TSS entry.
-AH00052 : child pid 4677* exit signal Aborted
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ans:
1. No speccial steps to trigger the issue. It eventually fills the apache logs
with the error messages.
2. Once we restart the apache it goes away but it reoccurs after 2-3
hours later.
* What was the outcome of this action?
Ans:
1. It resulted in service denial for Web-UI.
* What outcome did you expect instead?
Ans:
1. Web UI should be accesible
Please check error logs:
Fatal Python error: Could not allocate TSS entry
Fatal Python error: Could not allocate TSS entry
[Wed Oct 19 14:52:21.075114 2022] [core:notice] [pid 7554] AH00052:
child pid 42179 exit signal Aborted (6)
[Wed Oct 19 14:52:21.075157 2022] [core:notice] [pid 7554] AH00052:
child pid 42180 exit signal Aborted (6)
Best Regards
Hi Guys, Is there any update on this? Is it fixed in any of the latest releases?
Hi Guys, Any update on this?