<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Long time happy user. Just did a Fedora 37 update using dnf to upgrade the kernel from 6.3.4 to 6.3.8-100. Upon reboot, none of my frontend clients could connect to the backend. Netstat reflected that there was nothing listening on port 6543. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Backend was running and the logs showed it interacting with the database.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>But when I tried to stop / restart the service, it wouldn’t complete the shutdown, just hung (systemctl stop mythbackend). If I got the PID with ps -aux | grep mythbackend, and then tried to kill the process, it wouldn’t kill. Even “kill -9 XXXX” wouldn’t kill the mythbackend process. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Only way to kill the process was a reboot, which was lengthy because the kill timers all had to timeout before rebooting.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Anyway – I selected the prior 6.3.4 kernel from the grub2 boot menu, everything booted right up, mythbackend started and functioned fully normally as it has for many years.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I ran backend in the foreground with -v all, but no errors popped.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any suggestions or ideas? It is reproducable… if I boot 6.3.8-100, mythbackend is a non-responsive zombie. Boot 6.3.4, everything is fine.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for any ideas.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>