[mythtv-users] recent mythbackend crashing

Eyal Lebedinsky eyal at eyal.emu.id.au
Mon May 30 02:59:15 UTC 2022 


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
> =====

Examining the logs I see in 'messages'
=====
May 29 16:44:05 e7 audit[2588]: ANOM_ABEND auid=4294967295 uid=490 gid=482 ses=4294967295 subj=kernel pid=2588 comm="DVBRead" exe="/usr/bin/mythbackend" sig=6 res=1
May 30 00:14:54 e7 audit[760755]: ANOM_ABEND auid=4294967295 uid=490 gid=482 ses=4294967295 subj=kernel pid=760755 comm="DVBRead" exe="/usr/bin/mythbackend" sig=6 res=1
May 30 04:58:39 e7 audit[1012624]: ANOM_ABEND auid=4294967295 uid=490 gid=482 ses=4294967295 subj=kernel pid=1012624 comm="DVBRead" exe="/usr/bin/mythbackend" sig=6 res=1
May 30 09:04:03 e7 audit[2349582]: ANOM_ABEND auid=4294967295 uid=490 gid=482 ses=4294967295 subj=kernel pid=2349582 comm="DVBRead" exe="/usr/bin/mythbackend" sig=6 res=1
May 30 11:33:09 e7 audit[2883839]: ANOM_ABEND auid=4294967295 uid=490 gid=482 ses=4294967295 subj=kernel pid=2883839 comm="DVBRead" exe="/usr/bin/mythbackend" sig=6 res=1
May 30 11:48:37 e7 audit[2950437]: ANOM_ABEND auid=4294967295 uid=490 gid=482 ses=4294967295 subj=kernel pid=2950437 comm="DVBRead" exe="/usr/bin/mythbackend" sig=6 res=1
May 30 12:03:46 e7 audit[2958463]: ANOM_ABEND auid=4294967295 uid=490 gid=482 ses=4294967295 subj=kernel pid=2958463 comm="DVBRead" exe="/usr/bin/mythbackend" sig=6 res=1
=====

As these crashes happen when no recording is active, is it likely to be from the EIT scanner?

Looking at logs just before a crash:

==
2022-05-30 11:32:34.188883 I [2883839/2883989] Scheduler scheduler.cpp:2330 (HandleReschedule) - Reschedule requested for MATCH 0 2 13 2022-05-30T01:40:20Z EITScanner
2022-05-30 11:32:34.276453 I [2883839/2883908] TVRecEvent tv_rec.cpp:3600 (TuningFrequency) - TVRec[29]: TuningFrequency
2022-05-30 11:32:34.458548 W [2883839/2883908] TVRecEvent recorders/dvbsignalmonitor.cpp:110 (DVBSignalMonitor) - DVBSigMon[29](/dev/dvb/adapter-OPEN-ELEC-1/frontend0): Cannot count Uncorrected Blocks
                         eno: Unknown error 524 (524)
2022-05-30 11:32:35.305312 I [2883839/2883989] Scheduler scheduler.cpp:2444 (HandleReschedule) - Scheduled 206 items in 1.0 = 0.86 match + 0.00 check + 0.12 place
2022-05-30 11:33:08.131133 C [2883839/2883839] CoreContext signalhandling.cpp:294 (handleSignal) - Received Aborted: Code -6, PID 2883839, UID 490, Value 0x00000000
==
2022-05-30 11:47:18.773153 I [2950437/2950580] Scheduler scheduler.cpp:2330 (HandleReschedule) - Reschedule requested for MATCH 0 2 13 2022-06-06T23:31:01Z EITScanner
2022-05-30 11:47:18.888381 I [2950437/2950495] TVRecEvent tv_rec.cpp:3600 (TuningFrequency) - TVRec[29]: TuningFrequency
2022-05-30 11:47:19.068896 W [2950437/2950495] TVRecEvent recorders/dvbsignalmonitor.cpp:110 (DVBSignalMonitor) - DVBSigMon[29](/dev/dvb/adapter-OPEN-ELEC-1/frontend0): Cannot count Uncorrected Blocks
                         eno: Unknown error 524 (524)
2022-05-30 11:47:19.938243 I [2950437/2950580] Scheduler scheduler.cpp:2444 (HandleReschedule) - Scheduled 207 items in 1.0 = 0.87 match + 0.03 check + 0.12 place
2022-05-30 11:48:36.796758 C [2950437/2950437] CoreContext signalhandling.cpp:294 (handleSignal) - Received Aborted: Code -6, PID 2950437, UID 490, Value 0x00000000
==
2022-05-30 12:01:54.912021 I [2958463/2958610] Scheduler scheduler.cpp:2330 (HandleReschedule) - Reschedule requested for MATCH 0 2 12 2022-05-30T02:51:55Z EITScanner
2022-05-30 12:01:56.045005 I [2958463/2958610] Scheduler scheduler.cpp:2444 (HandleReschedule) - Scheduled 206 items in 1.0 = 0.87 match + 0.00 check + 0.12 place
2022-05-30 12:02:33.832171 I [2958463/2958610] Scheduler scheduler.cpp:2330 (HandleReschedule) - Reschedule requested for MATCH 0 2 3 2022-06-06T19:30:00Z EITScanner
2022-05-30 12:02:33.965382 I [2958463/2958534] TVRecEvent tv_rec.cpp:3600 (TuningFrequency) - TVRec[29]: TuningFrequency
2022-05-30 12:02:34.147658 W [2958463/2958534] TVRecEvent recorders/dvbsignalmonitor.cpp:110 (DVBSignalMonitor) - DVBSigMon[29](/dev/dvb/adapter-OPEN-ELEC-1/frontend0): Cannot count Uncorrected Blocks
                         eno: Unknown error 524 (524)
2022-05-30 12:02:34.961101 I [2958463/2958610] Scheduler scheduler.cpp:2444 (HandleReschedule) - Scheduled 206 items in 1.0 = 0.86 match + 0.00 check + 0.12 place
2022-05-30 12:03:08.530039 I [2958463/2958610] Scheduler scheduler.cpp:2330 (HandleReschedule) - Reschedule requested for MATCH 0 2 12 2022-05-30T03:33:13Z EITScanner
2022-05-30 12:03:08.530039 I [2958463/2958610] Scheduler scheduler.cpp:2330 (HandleReschedule) - Reschedule requested for MATCH 0 2 12 2022-05-30T03:33:13Z EITScanner
2022-05-30 12:03:09.663031 I [2958463/2958610] Scheduler scheduler.cpp:2444 (HandleReschedule) - Scheduled 206 items in 1.0 = 0.87 match + 0.00 check + 0.12 place
2022-05-30 12:03:45.054855 C [2958463/2958463] CoreContext signalhandling.cpp:294 (handleSignal) - Received Aborted: Code -6, PID 2958463, UID 490, Value 0x00000000
==

BTW, these two lines were always showing for years (even now about every 5 minutes), so probably are not related:
==
2022-05-30 11:47:19.068896 W [2950437/2950495] TVRecEvent recorders/dvbsignalmonitor.cpp:110 (DVBSignalMonitor) - DVBSigMon[29](/dev/dvb/adapter-OPEN-ELEC-1/frontend0): Cannot count Uncorrected Blocks
                         eno: Unknown error 524 (524)
==

I will try to disable the EIT scanner.

-- 
Eyal Lebedinsky (eyal at eyal.emu.id.au)

More information about the mythtv-users mailing list