-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
100% CPU usage by the backend #280
Comments
|
Notwithstanding https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests I am unable to attach the logfile. Its size is 10MB (i.e. less than the 25MB limit) |
|
Since I can't attach the logfile I'm pasting a section of it. Nov 5 20:31:00 dracor mythbackend: mythbackend[29881]: I Scheduler mythdbcon.cpp:420 (PurgeIdleConnections) New DB connection, total: 11 |
|
I'm an idiot. Input no. 6 is an MPEG tuner, which had its reclimit set to 2. |
|
Yes that can be very well the cause. |
Twice during the past week I woke up to find mythtv-backend consuming 100% CPU on all available threads of the server machine. A number of recordings had started as usual but they had not finished at the scheduled time. That is: they were still in progress so that the recording files were huge.
On both occasions I stopped/started the backend which returned things to normal.
After the second occurrence I checked the logs, which were much larger than usual but not enormous. Still: hard to ascertain what exactly went wrong. Nevertheless I noticed a number of these:
mythbackend: mythbackend[29881]: E CoreContext mainserver.cpp:3249 (HandleAddChildInput) MainServer: HandleAddChildInput: Failed to add child to input 6
That input corresponds with one of 4 HDHR DVB-C tuners.
I noticed that I had misconfigured it by setting maxrecordings to 6. I have now set it to a more reasonable 2 and will monitor over the next week to see whether the issue returns.
Klaas mentioned on the users list that maxrecordings=6 isn't a misconfiguration and asked that I attach the full log (will do so) and also include the contents of the capturecard table. See below. But please note that I have already changed maxrecordings to 2 in all of the HDHR tuners; it was set to 6 in only one of them.
Platform: Ubuntu 18.04
Linux dracor 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
MythTV Version : v31.0+fixes.202010122044.eb3c84de5f~ubuntu18.04.1
MythTV Branch : fixes/31
Network Protocol : 91
Library API : 31.20200101-1
QT Version : 5.9.5
Options compiled in:
linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_dvb using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto using_gnutls using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl using_egl using_qtwebkit using_qtscript using_qtdbus using_taglib using_v4l2 using_v4l2prime using_x11 using_libbluray_external using_xrandr using_profiletype using_systemd_notify using_systemd_journal using_drm using_bindings_perl using_bindings_python using_bindings_php using_freetype2 using_mythtranscode using_opengl using_egl using_drm using_vaapi using_nvdec using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2 using_libmp3lame
Package version:
apt-cache policy mythtv
mythtv:
Installed: 2:31.0+fixes.202010122044.eb3c84de5f
ubuntu18.04.1ubuntu18.04.1Candidate: 2:31.0+fixes.202010122044.eb3c84de5f
Version table:
*** 2:31.0+fixes.202010122044.eb3c84de5f~ubuntu18.04.1 500
500 http://ppa.launchpad.net/mythbuntu/31/ubuntu bionic/main amd64 Packages
500 http://ppa.launchpad.net/mythbuntu/31/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
2:29.1+fixes.20180414.329c235-0ubuntu3 500
500 http://be.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages
500 http://be.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages
Component: backend
The text was updated successfully, but these errors were encountered: