Bug#1072751: Acknowledgement (linux-image-6.1.0-21-cloud-amd64: Bookworm with latest kernel 6.6.16generic, failed to umount partition with message "Umounting local filesystems...umount: /var/log: targ
PFA: Screenshot of the Error On Fri, Jun 7, 2024 at 7:09 PM Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1072751: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072751. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > jvishwanat...@gmail.com, bnaigaon...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian Kernel Team > > If you wish to submit further information on this problem, please > send it to 1072...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1072751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072751 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems -- --Regards Vishwanath
Bug#1039584: Acknowledgement (libapache2-mod-wsgi-py3: Fatal Python error: Could not allocate TSS entry)
Any update on the same? On Tue, Jun 27, 2023 at 6:24 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1039584: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039584. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > jvishwanat...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian Python Team > > If you wish to submit further information on this problem, please > send it to 1039...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1039584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039584 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > -- --Regards Vishwanath
Bug#1026100: Acknowledgement (libapache2-mod-wsgi: Repeated "Fatal Python error: Could not allocate TSS entry" error logged by libapache2-mod-wsgi-py3)
Hi Guys, Any update on this? On Thu, Dec 15, 2022 at 12:03 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1026100: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026100. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > jvishwanat...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian Python Modules Team > > If you wish to submit further information on this problem, please > send it to 1026...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1026100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026100 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > -- --Regards Vishwanath
Bug#1026100:
Hi Guys, Is there any update on this? Is it fixed in any of the latest releases? -- --Regards Vishwanath
Bug#1026100: Some more details on 1026100
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 -- --Regards Vishwanath
