[mythtv-users] recent mythbackend crashing

[Klaas de Waal]

On Tue, 31 May 2022 at 15:40, John Pilkington <johnpilk222 at gmail.com> wrote:

> On 31/05/2022 11:53, Eyal Lebedinsky wrote:
> >
> >
> > On 30/05/2022 11.00, Eyal Lebedinsky wrote:
> >> Running f34 up-to-date.
> >>
> >> Recently, following an update of mythtv and the kernel, mythbackend
> >> started crahing even when not recording or watching.
> >> Does anyone else see this?
> >>
> >> =====
> >> ## Latest update:
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythffmpeg-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythmusic-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythtv-backend-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythtv-base-themes-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythtv-common-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythtv-docs-32.0-1.30.20220510git26079f815a.fc34.noarch
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythtv-frontend-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythtv-libs-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded:
> >> mythtv-setup-32.0-1.30.20220510git26079f815a.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Upgraded: mythweb-32.0-1.fc34.noarch
> >> 2022-05-29T08:46:33+1000 DEBUG Installed: kernel-5.17.11-100.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Installed:
> >> kernel-core-5.17.11-100.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Installed:
> >> kernel-debug-devel-5.17.11-100.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Installed:
> >> kernel-devel-5.17.11-100.fc34.x86_64
> >> 2022-05-29T08:46:33+1000 DEBUG Installed:
> >> kernel-modules-5.17.11-100.fc34.x86_64
> >> ## rebooted
> >> May 29 08:51:02 e7 kernel: Linux version 5.17.11-100.fc34.x86_64
> >> (mockbuild at bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.3.1
> >> 20220421 (Red Hat 11.3.1-2), GNU ld version 2.35.2-6.fc34) #1 SMP
> >> PREEMPT Wed May 25 15:14:37 UTC 2022
> >> ## mythbackend crashes so far:
> >> May 29 16:44:04 e7 mythbackend[2588]: 2022-05-29 16:44:04.764734 C
> >> [2588/2588] CoreContext signalhandling.cpp:294:handleSignal  Received
> >> Aborted: Code -6, PID 2588, UID 490, Value 0x00000000
> >> May 30 00:14:53 e7 mythbackend[760755]: 2022-05-30 00:14:53.903080 C
> >> [760755/760755] CoreContext signalhandling.cpp:294:handleSignal
> >> Received Aborted: Code -6, PID 760755, UID 490, Value 0x00000000
> >> May 30 04:58:38 e7 mythbackend[1012624]: 2022-05-30 04:58:38.158620 C
> >> [1012624/1012624] CoreContext signalhandling.cpp:294:handleSignal
> >> Received Aborted: Code -6, PID 1012624, UID 490, Value 0x00000000
> >> May 30 09:04:02 e7 mythbackend[2349582]: 2022-05-30 09:04:02.508086 C
> >> [2349582/2349582] CoreContext signalhandling.cpp:294:handleSignal
> >> Received Aborted: Code -6, PID 2349582, UID 490, Value 0x00000000
> >> =====
> >
> > I mentioned (elsewhere in this thread) that I see that the crashes
> > happen during EIT scan.
> >
> > So far, after disabling EIT (midday yesterday), no more crashes.
> > I will stay this way until after I upgrade f34->f36 (very soon) then
> > enable EIT and see.
> > Though I can see that f36 has the same mythtv version as f34 (both
> > updated recently)...
> >
> > So, does anyone else see this?
> >
> I'm running today's master in F35, using DVB-T/T2 eit in the uk.  I just
> rescanned and ran mythbackend --setverbose eit.  All seems ok and
> there's quite a lot of EITHelper and EITCache activity at present.
>
> The 'el7' system  has DVB-T only, running master from a few days ago.
> It's currently 'Postponing EIT scan on input [3] because input 19 is
> busy' but no problems seen.
>
> ISTR that I have had problems in the past if I had more than one device
> doing active EIT scans, but the only symptom was complaints from
> ProjectX during post-processing about packages out of order.
>
> John P
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org




>> [1012624/1012624] CoreContext signalhandling.cpp:294:handleSignal
>> Received Aborted: Code -6, PID 1012624, UID 490, Value 0x00000000

What is a bit strange is that you get the abort signal. Usually we get the
segmentation fault.
It could be useful if you have a mythbackend log with lots of debug output.
Because you suspect EIT the verbosity options "-v channel,eit
--loglevel=debug" would be a good idea.

Klaas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220531/d4bd682b/attachment.htm>