[Solved] Backend with high CPU load.

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

Post Reply
megabiker
Newcomer
Posts: 2
Joined: Mon Jan 23, 2023 1:23 pm
Germany

[Solved] Backend with high CPU load.

Post by megabiker »

In the course of the PC reinstallation, I also installed Mythtv in the current version 32 with fixes. I noticed that after about 3 minutes the CPU load increases dramatically when this message appears in the log

„ DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot count Uncorrected Blocks eno: Unbekannter Fehler 524 (524)“

The same message also appears for the other inputs /dev/dvb/adapter1/frontend0, /dev/dvb/adapter2/frontend0, /dev/dvb/adapter3/frontend0, with the CPU load increasing accordingly. Nothing is recorded or watched. The backend is actually idle.

Otherwise, the backend works fine. So far, all programs have been recorded and played back.

I have two "DVBSKy S952 Dual DVB-S/S2 PCIe" running under LinuxMint 21.1. I have been an enthusiastic Mythtv user for 15 years now and previously used version 29 under Linux Mint 19.3.

Can you help me?


Log:

mythbackend
2023-01-19 22:41:26.500711 C mythbackend version: fixes/32 [v32.0+fixes.202301091618.e677dd354f~ubuntu22.04.1]
2023-01-19 22:41:26.500722 C Qt version: compile: 5.15.3, runtime: 5.15.3
2023-01-19 22:41:26.500751 I Linux Mint 21.1 (x86_64)
2023-01-19 22:41:26.500753 N Enabled verbose msgs: general
2023-01-19 22:41:26.500759 N Setting Log Level to LOG_INFO
2023-01-19 22:41:26.511395 I Added logging to the console
2023-01-19 22:41:26.511663 I Setup Unterbrechung handler
2023-01-19 22:41:26.511669 I Setup Beendet handler
2023-01-19 22:41:26.511675 I Setup Speicherzugriffsfehler handler
2023-01-19 22:41:26.511679 I Setup Abgebrochen handler
2023-01-19 22:41:26.511684 I Setup Bus-Zugriffsfehler handler
2023-01-19 22:41:26.511688 I Setup Gleitkomma-Ausnahme handler
2023-01-19 22:41:26.511694 I Setup Ungültiger Maschinenbefehl handler
2023-01-19 22:41:26.511711 I Setup Real-Time Signal 0 handler
2023-01-19 22:41:26.511715 I Setup Aufgelegt handler
2023-01-19 22:41:26.511828 N Using runtime prefix = /usr
2023-01-19 22:41:26.511830 N Using configuration directory = /home/martin/.mythtv
2023-01-19 22:41:26.511861 I Assumed character encoding: de_DE.UTF-8
2023-01-19 22:41:26.512112 I Empty LocalHostName. This is typical.
2023-01-19 22:41:26.512116 I Using a profile name of: 'pussycat22' (Usually the same as this host's name.)
2023-01-19 22:41:26.512154 I Start up testing connections. DB 192.168.178.10, BE , attempt 0, status dbAwake, Delay: 2000
2023-01-19 22:41:27.056777 N Setting QT default locale to de_DE
2023-01-19 22:41:27.056790 I Current locale de_DE
2023-01-19 22:41:27.056850 N Reading locale defaults from /usr/share/mythtv//locales/de_de.xml
2023-01-19 22:41:27.125148 I Power: On AC power
2023-01-19 22:41:27.125167 I Power: Supported actions: Suspend,Restart,Shutdown
2023-01-19 22:41:27.126738 I Loading de translation for module mythfrontend
2023-01-19 22:41:27.132345 I Current MythTV Schema Version (DBSchemaVer): 1376
2023-01-19 22:41:27.132869 I Loading de translation for module mythfrontend
2023-01-19 22:41:27.133990 N MythBackend: Starting up as the master server.
2023-01-19 22:41:27.513685 I CardUtil[1]: Set delivery system: DVB-S2
2023-01-19 22:41:39.128624 I Found 0 distinct programid authorities
2023-01-19 22:41:39.128990 I New static DB connectionSchedCon
2023-01-19 22:41:39.129111 I Registering HouseKeeperTask 'LogClean'.
2023-01-19 22:41:39.129216 I Registering HouseKeeperTask 'DBCleanup'.
2023-01-19 22:41:39.129321 I Registering HouseKeeperTask 'ThemeUpdateNotifications'.
2023-01-19 22:41:39.129443 I Registering HouseKeeperTask 'RecordedArtworkUpdate'.
2023-01-19 22:41:39.131560 I Registering HouseKeeperTask 'MythFillDB'.
2023-01-19 22:41:39.132600 I Registering HouseKeeperTask 'UpdateRadioStreams'.
2023-01-19 22:41:39.132704 I Registering HouseKeeperTask 'JobQueueRecover'.
2023-01-19 22:41:39.132776 I Registering HouseKeeperTask 'HardwareProfiler'.
2023-01-19 22:41:39.137327 I Starting HouseKeeper.
2023-01-19 22:41:39.161824 I Listening on TCP 0.0.0.0:6544
2023-01-19 22:41:39.162422 I Listening on TCP [::]:6544
2023-01-19 22:41:39.162440 I Listening on TCP (SSL) 0.0.0.0:6554
2023-01-19 22:41:39.162457 I Listening on TCP (SSL) [::]:6554
2023-01-19 22:41:39.162523 I Listening on TCP 0.0.0.0:6549
2023-01-19 22:41:39.162569 I Listening on TCP [::]:6549
2023-01-19 22:41:39.172864 I Main::Registering HttpStatus Extension
2023-01-19 22:41:39.175686 I Listening on TCP 0.0.0.0:6543
2023-01-19 22:41:39.175714 I Listening on TCP [::]:6543
2023-01-19 22:41:39.178711 N AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min
2023-01-19 22:41:39.181664 I HTTPPool: Using maximum 8 threads
2023-01-19 22:41:39.187886 W SSL: SSL Host key file (/home/martin/.mythtv/certificates/key.pem) does not exist or is not readable
2023-01-19 22:41:39.200945 I Listening on TCP 0.0.0.0:6744
2023-01-19 22:41:39.200974 I Listening on TCP [::]:6744
2023-01-19 22:41:39.448103 I MainServer: MainServer::ANN Frontend
2023-01-19 22:41:39.448113 I MainServer: adding: pussycat22(55727cf815b0) as a client (events: 0)
2023-01-19 22:41:39.448161 I BackendContext: Frontend 'pussycat22' connected.
2023-01-19 22:41:39.449581 I MainServer: MainServer::ANN Monitor
2023-01-19 22:41:39.449589 I MainServer: adding: pussycat22(55727d0d03b0) as a client (events: 1)
2023-01-19 22:41:39.974951 I Bonjour: Service registration complete: name 'Mythbackend on pussycat22' type '_mythbackend._tcp.' domain: 'local.'
2023-01-19 22:41:40.005138 I Bonjour: Service registration complete: name 'mythbackend on pussycat22' type '_http._tcp.' domain: 'local.'
2023-01-19 22:41:42.165072 I Reschedule requested for MATCH 0 0 0 - SchedulerInit
2023-01-19 22:41:42.272918 I Scheduled 42 items in 0.1 = 0.05 match + 0.02 check + 0.03 place
2023-01-19 22:41:42.293919 I Scheduler: Seem to be woken up by USER
2023-01-19 22:42:58.180930 N AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min
2023-01-19 22:44:16.774984 I TVRec[1]: TuningFrequency
2023-01-19 22:44:18.562677 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot count Uncorrected Blocks
eno: Unbekannter Fehler 524 (524)
2023-01-19 22:44:27.807212 I TVRec[3]: TuningFrequency
2023-01-19 22:44:29.592083 W DVBSigMon[3](/dev/dvb/adapter2/frontend0): Cannot count Uncorrected Blocks
eno: Unbekannter Fehler 524 (524)
2023-01-19 22:45:06.456735 I TVRec[2]: TuningFrequency
2023-01-19 22:45:08.246676 W DVBSigMon[2](/dev/dvb/adapter1/frontend0): Cannot count Uncorrected Blocks
eno: Unbekannter Fehler 524 (524)
2023-01-19 22:46:10.633484 I TVRec[4]: TuningFrequency
2023-01-19 22:46:12.443111 W DVBSigMon[4](/dev/dvb/adapter3/frontend0): Cannot count Uncorrected Blocks
eno: Unbekannter Fehler 524 (524)
2023-01-19 22:49:35.102596 I Reschedule requested for MATCH 0 1 15 2023-01-22T23:15:00Z EITScanner
2023-01-19 22:49:35.188041 I Scheduled 42 items in 0.1 = 0.04 match + 0.00 check + 0.02 place
2023-01-19 22:49:35.375641 I Reschedule requested for MATCH 0 1 3 2023-01-26T21:30:00Z EITScanner
2023-01-19 22:49:35.471329 I Scheduled 42 items in 0.1 = 0.03 match + 0.00 check + 0.04 place
2023-01-19 22:49:36.361569 I TVRec[3]: TuningFrequency
2023-01-19 22:49:36.910102 I TVRec[1]: TuningFrequency
2023-01-19 22:49:37.045635 I CardUtil[1]: Set delivery system: DVB-S2
2023-01-19 22:49:38.176738 W DVBSigMon[3](/dev/dvb/adapter2/frontend0): Cannot count Uncorrected Blocks
eno: Unbekannter Fehler 524 (524)
2023-01-19 22:49:38.232369 I DVBChan[1](/dev/dvb/adapter0/frontend0): Next tuning after less than 1000ms, delaying by 463ms
2023-01-19 22:49:39.190126 W DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot count Uncorrected Blocks
eno: Unbekannter Fehler 524 (524)
2023-01-19 22:50:32.702428 I Reschedule requested for MATCH 0 1 49 2023-01-19T22:00:00Z EITScanner
2023-01-19 22:50:32.786263 I Scheduled 42 items in 0.1 = 0.04 match + 0.00 check + 0.02 place
2023-01-19 22:50:33.637267 I TVRec[2]: TuningFrequency
2023-01-19 22:50:35.458158 W DVBSigMon[2](/dev/dvb/adapter1/frontend0): Cannot count Uncorrected Blocks
eno: Unbekannter Fehler 524 (524)
User avatar
kmdewaal
Developer
Posts: 640
Joined: Wed Dec 07, 2016 8:01 pm
Netherlands

Re: Backend with high CPU load.

Post by kmdewaal »

About
DVBSigMon[1](/dev/dvb/adapter0/frontend0): Cannot count Uncorrected Blocks eno: Unbekannter Fehler 524 (524)
These messages are harmless. They indicate that the tuner cards are not capable of returning the Uncorrected Block Count and that is typical for the DVBSky tuners. In your case this message does indicate that the tuner is now being used.

About
The same message also appears for the other inputs /dev/dvb/adapter1/frontend0, /dev/dvb/adapter2/frontend0, /dev/dvb/adapter3/frontend0, with the CPU load increasing accordingly. Nothing is recorded or watched. The backend is actually idle.
This means that all your tuners are becoming active.

The cause of this is most likely that you have EIT enabled on all capture cards.
This is only useful when each capture card is set up to receive a different satellite, with each capture card then having its own video source.
When all your capture cards are configured to receive the same satellite then you need to enable EIT on only one capture card.
When you get your guide data from somewhere else, e.g. Schedules Direct, then you should disable EIT completely.

For a complete guide on configuration see the guide on the Wiki: https://www.mythtv.org/wiki/Channel_Scanning which also has a few paragraphs about satellite configuration.
megabiker
Newcomer
Posts: 2
Joined: Mon Jan 23, 2023 1:23 pm
Germany

Re: Backend with high CPU load.

Post by megabiker »

Thanks alot. I had actually turned on EIT on all cards. After deactivation, the CPU load is normal.

A few years ago I asked if there was a donation option for Mythtv. At that time, open source was only generally mentioned as a donation. Is there a way to donate directly to the developers now?

Kind regards, Martin
Post Reply