<html><head></head><body><span class="viv-signature"></span>On Saturday 24 June 2023 06:55:21 PM (-05:00), John Freer via mythtv-users wrote:<br><br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><style>div.WordSection1{
page:WordSection1;
}
.MsoChpDefault{
font-family:Calibri, sans-serif;
}
span.EmailStyle17{
color:windowtext;
font-family:Calibri, sans-serif;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal{
font-family:Calibri, sans-serif;
font-size:11pt;
margin-left:0in;
margin-bottom:0in;
margin-right:0in;
margin-top:0in;
}
@font-face {
font-family:Calibri;
}
@font-face {
font-family:"Cambria Math";
}</style><div class="WordSection1"><p class="MsoNormal">Hi: </p><p class="MsoNormal"> </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. </p><p class="MsoNormal"> </p><p class="MsoNormal">Backend was running and the logs showed it interacting with the database.</p><p class="MsoNormal"> </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. </p><p class="MsoNormal"> </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.</p><p class="MsoNormal"> </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.</p><p class="MsoNormal"> </p><p class="MsoNormal">I ran backend in the foreground with -v all, but no errors popped.</p><p class="MsoNormal"> </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.</p><p class="MsoNormal"> </p><p class="MsoNormal">Thanks for any ideas.</p></div></blockquote><div><br></div><div><br></div>Info here: https://github.com/MythTV/mythtv/issues/761 <div><br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div class="WordSection1"><p class="MsoNormal"></p></div></blockquote><span class="viv-signature-below">-- <br>Bill</span></div></body></html>