Mailing List Archive

Getting slower
Over the last few releases mythtv has got slower to start and stop.
What is the delay looking for ipv6 dtuff?

This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.

If the issue is not my config should we not gently think about start and stop times from a dev point of view?

James

00.730068 I Setup Interrupt: 2 handler
00.730091 I Setup Terminated: 15 handler
00.730098 I Setup Segmentation fault: 11 handler
00.730104 I Setup Abort trap: 6 handler
00.730109 I Setup Bus error: 10 handler
00.730115 I Setup Floating point exception: 8 handler
00.730123 I Setup Illegal instruction: 4 handler
00.730130 I Setup User defined signal 1: 30 handler
00.730137 I Setup User defined signal 2: 31 handler
00.730144 I Setup Hangup: 1 handler
00.730215 C mythfrontend version: fixes/31 [v31.0-81-g05a613f9fa] www.mythtv.org
00.730224 C Qt version: compile: 5.14.2, runtime: 5.14.2
00.730243 I macOS 10.15 (x86_64)
00.730249 N Enabled verbose msgs: general
00.730266 N Setting Log Level to LOG_INFO
00.741674 I Added logging to the console
00.742843 N Using runtime prefix = /Applications/Mythfrontend.app/Contents/Resources
00.742867 N Using configuration directory = /Users/jam/.mythtv
00.743495 I Assumed character encoding: en_AU.UTF-8
00.747012 I Loading en_us translation for module mythfrontend
00.747443 I Empty LocalHostName. This is typical.
00.747457 I Using a profile name of: 'plasma.home' (Usually the same as this host's name.)
00.747563 I Start up testing connections. DB 192.168.5.33, BE , attempt 0, status dbAwake, Delay: 2000
02.562399 N Setting QT default locale to en_AU
02.562434 I Current locale en_AU
02.562575 E No locale defaults file for en_AU, skipping
02.621197 I Display: Found screen 'Colour LCD'
02.621234 I Display: Using screen 'Colour LCD' (Make: Unknown Model: Unknown)
02.621253 I Display: Qt screen pixel ratio: 1.00
02.621283 I Display: Geometry: 1792x1120+0+0 Size(Qt): 344.824mmx214.702mm
02.629084 N Display: Desktop video mode: 1792x1120 60.000Hz
ic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
03.250188 I Power: Battery at 100%
03.250310 I Power: Supported actions: Suspend,Restart,Shutdown
03.641367 I Listening on TCP 0.0.0.0:6547
03.661254 I Listening on TCP [::]:6547

----------------------------------------
What is this
---------------------------------------

11.012437 I Loading en_us translation for module mythfrontend
11.122577 E LIRC: Failed to connect to Unix socket '/var/run/lirc/lircd'
ile or directory (2)
11.123518 E AppleRemote::_findAppleRemoteDevice(AppleIRController) failed
11.123544 E AppleRemote::_findAppleRemoteDevice(AppleTVIRReceiver) failed
11.123552 E AppleRemote::startListening() failed
11.123586 I UDPListener: Enabling
11.131896 I Binding to UDP 0.0.0.0:6948
11.131956 I Binding to UDP [::]:6948
12.047050 I Using Frameless Window
12.047063 I Using Full Screen Window
12.057267 I Display: Have main widget
12.057288 I Display: Have main window
12.067090 I Display: Found screen 'Colour LCD'
12.098587 I UI Screen Resolution: 1792 x 1120
12.237759 I OpenGL: OpenGL vendor : Intel Inc.
12.237770 I OpenGL: OpenGL renderer : Intel(R) UHD Graphics 630
12.237777 I OpenGL: OpenGL version : 2.1 INTEL-14.6.18
12.237785 I OpenGL: Qt platform : cocoa
12.237791 I OpenGL: Qt OpenGL format : OpenGL 2.1
12.237799 I OpenGL: Qt OpenGL surface : RGBA: 888-1 Depth: 0 Stencil: 0
12.237805 I OpenGL: Max texture size : 16384
12.237811 I OpenGL: Max texture units : 16
12.237819 I OpenGL: Shaders : Yes
12.237827 I OpenGL: NPOT textures : Yes
12.237833 I OpenGL: Multitexturing : Yes
12.237838 I OpenGL: Rectangular textures : Yes
12.237844 I OpenGL: Buffer mapping : Yes
12.237851 I OpenGL: Framebuffer objects : Yes
12.237857 I OpenGL: 16bit framebuffers : Yes
12.237863 I OpenGL: Unpack Subimage : Yes
12.237869 I OpenGL: GL_RED/GL_R8 : Yes
12.246385 I OpenGL: Initialised MythRenderOpenGL
12.246393 I OpenGL: Using full range output
12.246437 I High DPI scaling disabled
12.269403 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
12.274189 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
12.274244 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
12.295615 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
ylib, 1): no suitable image found. Did find:
thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
13.292341 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.5.33:6543 (try 1 of 1)
13.301605 I MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
13.345602 E CECAdapter: Failed to load libcec.
13.354158 E RAOP Device: Aborting startup - no key found.
13.362064 I AirPlay: Created airplay objects.
13.362197 I Listening on TCP 0.0.0.0:5100
13.362260 I Listening on TCP [::]:5100
13.458092 I Current MythTV Schema Version (DBSchemaVer): 1361
13.485082 I VTBDec: Supported/available VideoToolbox decoders:
13.485102 I VTBDec: H264
13.485108 I VTBDec: HEVC

---------------------------------------------------
GUI up and running
Now exit
---------------------------------------------------

14.061260 I Bonjour: Service registration complete: name 'MythTV on plasma.home' type '_airplay._tcp.' domain: 'local.'
20.879759 N Registering Internal as a media playback plugin.
20.914671 W No plugins directory /Applications/Mythfrontend.app/Contents/Resources/lib/mythtv/plugins
20.974499 I Using Frameless Window
20.974514 I Using Full Screen Window
20.982686 I Display: Have main widget
20.982700 I Display: Have main window
21.026 mythfrontend.real[4207:201300] not in fullscreen state
20.997174 I Display: Found screen 'Colour LCD'
20.997209 I Display: Waiting for new screen
21.024347 I Bonjour: Service registration complete: name 'Mythfrontend on plasma.home' type '_mythfrontend._tcp.' domain: 'local.'
21.473519 W Display: Timed out waiting for new screen
21.492106 I UI Screen Resolution: 1792 x 1120
21.559729 I OpenGL: Initialised MythRenderOpenGL
21.559740 I OpenGL: Using full range output
21.559776 I High DPI scaling disabled
21.596433 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
21.601489 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
21.601552 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
21.623046 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
ylib, 1): no suitable image found. Did find:
thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
21.824091 E CECAdapter: Failed to load libcec.
21.824148 W MythPainter: 1 images not yet de-allocated.
21.824167 I Clearing OpenGL painter cache.
21.825898 I OpenGL: MythRenderOpenGL closing
21.951746 N Found mainmenu.xml for theme 'MythCenter-wide'
22.049329 I Checking for theme updates every hour
22.058027 I Starting HouseKeeper.
22.058358 I Starting process manager
22.058390 I Starting process signal handler
22.058634 I Starting IO manager (read)
22.058896 I Starting IO manager (write)
35.124192 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
35.128853 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
35.128910 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
35.151154 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
35.917695 I Bonjour: De-registering service '_mythfrontend._tcp.' on 'Mythfrontend on plasma.home'
35.937750 W MythPainter: 61 images not yet de-allocated.
35.937793 I Clearing OpenGL painter cache.
35.940032 I OpenGL: MythRenderOpenGL closing
35.942244 I Display: Deleting
35.948702 I RAOP Device: Cleaning up.
35.948722 I AirPlay: Cleaning up.
35.948834 I Bonjour: De-registering service '_airplay._tcp.' on 'MythTV on plasma.home'
35.949171 I Shutting down UPnP client...
42.983810 I Waiting for threads to exit.
49.795710 I Exiting
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
I, too, have noticed some very long startup times, but it seems to vary
a LOT:  anywhere from a couple of seconds to what seems like 45-50
seconds.  The first startup of the day seems to be doing something;
generating thumbnails?  Looking for icons? Optimizing the database?  But
it's not like there's one slow startup and all others are equally
quick.  Startup time seems to vary unpredictably, and the long ones
adversely affect the WAF (which is unacceptable! :).  Exit is never slow.

Dave D.

On 8/2/20 4:00 PM, jam@tigger.ws wrote:
> Over the last few releases mythtv has got slower to start and stop.
> What is the delay looking for ipv6 dtuff?
>
> This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>
> If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>
> James
>
> 00.730068 I Setup Interrupt: 2 handler
> 00.730091 I Setup Terminated: 15 handler
> 00.730098 I Setup Segmentation fault: 11 handler
> 00.730104 I Setup Abort trap: 6 handler
> 00.730109 I Setup Bus error: 10 handler
> 00.730115 I Setup Floating point exception: 8 handler
> 00.730123 I Setup Illegal instruction: 4 handler
> 00.730130 I Setup User defined signal 1: 30 handler
> 00.730137 I Setup User defined signal 2: 31 handler
> 00.730144 I Setup Hangup: 1 handler
> 00.730215 C mythfrontend version: fixes/31 [v31.0-81-g05a613f9fa] www.mythtv.org
> 00.730224 C Qt version: compile: 5.14.2, runtime: 5.14.2
> 00.730243 I macOS 10.15 (x86_64)
> 00.730249 N Enabled verbose msgs: general
> 00.730266 N Setting Log Level to LOG_INFO
> 00.741674 I Added logging to the console
> 00.742843 N Using runtime prefix = /Applications/Mythfrontend.app/Contents/Resources
> 00.742867 N Using configuration directory = /Users/jam/.mythtv
> 00.743495 I Assumed character encoding: en_AU.UTF-8
> 00.747012 I Loading en_us translation for module mythfrontend
> 00.747443 I Empty LocalHostName. This is typical.
> 00.747457 I Using a profile name of: 'plasma.home' (Usually the same as this host's name.)
> 00.747563 I Start up testing connections. DB 192.168.5.33, BE , attempt 0, status dbAwake, Delay: 2000
> 02.562399 N Setting QT default locale to en_AU
> 02.562434 I Current locale en_AU
> 02.562575 E No locale defaults file for en_AU, skipping
> 02.621197 I Display: Found screen 'Colour LCD'
> 02.621234 I Display: Using screen 'Colour LCD' (Make: Unknown Model: Unknown)
> 02.621253 I Display: Qt screen pixel ratio: 1.00
> 02.621283 I Display: Geometry: 1792x1120+0+0 Size(Qt): 344.824mmx214.702mm
> 02.629084 N Display: Desktop video mode: 1792x1120 60.000Hz
> ic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
> 03.250188 I Power: Battery at 100%
> 03.250310 I Power: Supported actions: Suspend,Restart,Shutdown
> 03.641367 I Listening on TCP 0.0.0.0:6547
> 03.661254 I Listening on TCP [::]:6547
>
> ----------------------------------------
> What is this
> ---------------------------------------
>
> 11.012437 I Loading en_us translation for module mythfrontend
> 11.122577 E LIRC: Failed to connect to Unix socket '/var/run/lirc/lircd'
> ile or directory (2)
> 11.123518 E AppleRemote::_findAppleRemoteDevice(AppleIRController) failed
> 11.123544 E AppleRemote::_findAppleRemoteDevice(AppleTVIRReceiver) failed
> 11.123552 E AppleRemote::startListening() failed
> 11.123586 I UDPListener: Enabling
> 11.131896 I Binding to UDP 0.0.0.0:6948
> 11.131956 I Binding to UDP [::]:6948
> 12.047050 I Using Frameless Window
> 12.047063 I Using Full Screen Window
> 12.057267 I Display: Have main widget
> 12.057288 I Display: Have main window
> 12.067090 I Display: Found screen 'Colour LCD'
> 12.098587 I UI Screen Resolution: 1792 x 1120
> 12.237759 I OpenGL: OpenGL vendor : Intel Inc.
> 12.237770 I OpenGL: OpenGL renderer : Intel(R) UHD Graphics 630
> 12.237777 I OpenGL: OpenGL version : 2.1 INTEL-14.6.18
> 12.237785 I OpenGL: Qt platform : cocoa
> 12.237791 I OpenGL: Qt OpenGL format : OpenGL 2.1
> 12.237799 I OpenGL: Qt OpenGL surface : RGBA: 888-1 Depth: 0 Stencil: 0
> 12.237805 I OpenGL: Max texture size : 16384
> 12.237811 I OpenGL: Max texture units : 16
> 12.237819 I OpenGL: Shaders : Yes
> 12.237827 I OpenGL: NPOT textures : Yes
> 12.237833 I OpenGL: Multitexturing : Yes
> 12.237838 I OpenGL: Rectangular textures : Yes
> 12.237844 I OpenGL: Buffer mapping : Yes
> 12.237851 I OpenGL: Framebuffer objects : Yes
> 12.237857 I OpenGL: 16bit framebuffers : Yes
> 12.237863 I OpenGL: Unpack Subimage : Yes
> 12.237869 I OpenGL: GL_RED/GL_R8 : Yes
> 12.246385 I OpenGL: Initialised MythRenderOpenGL
> 12.246393 I OpenGL: Using full range output
> 12.246437 I High DPI scaling disabled
> 12.269403 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
> 12.274189 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
> 12.274244 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
> 12.295615 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
> ylib, 1): no suitable image found. Did find:
> thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
> 13.292341 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.5.33:6543 (try 1 of 1)
> 13.301605 I MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
> 13.345602 E CECAdapter: Failed to load libcec.
> 13.354158 E RAOP Device: Aborting startup - no key found.
> 13.362064 I AirPlay: Created airplay objects.
> 13.362197 I Listening on TCP 0.0.0.0:5100
> 13.362260 I Listening on TCP [::]:5100
> 13.458092 I Current MythTV Schema Version (DBSchemaVer): 1361
> 13.485082 I VTBDec: Supported/available VideoToolbox decoders:
> 13.485102 I VTBDec: H264
> 13.485108 I VTBDec: HEVC
>
> ---------------------------------------------------
> GUI up and running
> Now exit
> ---------------------------------------------------
>
> 14.061260 I Bonjour: Service registration complete: name 'MythTV on plasma.home' type '_airplay._tcp.' domain: 'local.'
> 20.879759 N Registering Internal as a media playback plugin.
> 20.914671 W No plugins directory /Applications/Mythfrontend.app/Contents/Resources/lib/mythtv/plugins
> 20.974499 I Using Frameless Window
> 20.974514 I Using Full Screen Window
> 20.982686 I Display: Have main widget
> 20.982700 I Display: Have main window
> 21.026 mythfrontend.real[4207:201300] not in fullscreen state
> 20.997174 I Display: Found screen 'Colour LCD'
> 20.997209 I Display: Waiting for new screen
> 21.024347 I Bonjour: Service registration complete: name 'Mythfrontend on plasma.home' type '_mythfrontend._tcp.' domain: 'local.'
> 21.473519 W Display: Timed out waiting for new screen
> 21.492106 I UI Screen Resolution: 1792 x 1120
> 21.559729 I OpenGL: Initialised MythRenderOpenGL
> 21.559740 I OpenGL: Using full range output
> 21.559776 I High DPI scaling disabled
> 21.596433 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
> 21.601489 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
> 21.601552 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
> 21.623046 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
> ylib, 1): no suitable image found. Did find:
> thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
> 21.824091 E CECAdapter: Failed to load libcec.
> 21.824148 W MythPainter: 1 images not yet de-allocated.
> 21.824167 I Clearing OpenGL painter cache.
> 21.825898 I OpenGL: MythRenderOpenGL closing
> 21.951746 N Found mainmenu.xml for theme 'MythCenter-wide'
> 22.049329 I Checking for theme updates every hour
> 22.058027 I Starting HouseKeeper.
> 22.058358 I Starting process manager
> 22.058390 I Starting process signal handler
> 22.058634 I Starting IO manager (read)
> 22.058896 I Starting IO manager (write)
> 35.124192 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
> 35.128853 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
> 35.128910 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
> 35.151154 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
> 35.917695 I Bonjour: De-registering service '_mythfrontend._tcp.' on 'Mythfrontend on plasma.home'
> 35.937750 W MythPainter: 61 images not yet de-allocated.
> 35.937793 I Clearing OpenGL painter cache.
> 35.940032 I OpenGL: MythRenderOpenGL closing
> 35.942244 I Display: Deleting
> 35.948702 I RAOP Device: Cleaning up.
> 35.948722 I AirPlay: Cleaning up.
> 35.948834 I Bonjour: De-registering service '_airplay._tcp.' on 'MythTV on plasma.home'
> 35.949171 I Shutting down UPnP client...
> 42.983810 I Waiting for threads to exit.
> 49.795710 I Exiting
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On Mon, 3 Aug 2020 07:00:36 +0800, you wrote:

>Over the last few releases mythtv has got slower to start and stop.
>What is the delay looking for ipv6 dtuff?

There is no delay from IPv6 - that is a red herring.

>This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>
>If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>
>James
>
>00.730068 I Setup Interrupt: 2 handler
>00.730091 I Setup Terminated: 15 handler
>00.730098 I Setup Segmentation fault: 11 handler
>00.730104 I Setup Abort trap: 6 handler
>00.730109 I Setup Bus error: 10 handler
>00.730115 I Setup Floating point exception: 8 handler
>00.730123 I Setup Illegal instruction: 4 handler
>00.730130 I Setup User defined signal 1: 30 handler
>00.730137 I Setup User defined signal 2: 31 handler
>00.730144 I Setup Hangup: 1 handler
>00.730215 C mythfrontend version: fixes/31 [v31.0-81-g05a613f9fa] www.mythtv.org
>00.730224 C Qt version: compile: 5.14.2, runtime: 5.14.2
>00.730243 I macOS 10.15 (x86_64)
>00.730249 N Enabled verbose msgs: general
>00.730266 N Setting Log Level to LOG_INFO
>00.741674 I Added logging to the console
>00.742843 N Using runtime prefix = /Applications/Mythfrontend.app/Contents/Resources
>00.742867 N Using configuration directory = /Users/jam/.mythtv
>00.743495 I Assumed character encoding: en_AU.UTF-8
>00.747012 I Loading en_us translation for module mythfrontend
>00.747443 I Empty LocalHostName. This is typical.
>00.747457 I Using a profile name of: 'plasma.home' (Usually the same as this host's name.)
>00.747563 I Start up testing connections. DB 192.168.5.33, BE , attempt 0, status dbAwake, Delay: 2000
>02.562399 N Setting QT default locale to en_AU
>02.562434 I Current locale en_AU
>02.562575 E No locale defaults file for en_AU, skipping
>02.621197 I Display: Found screen 'Colour LCD'
>02.621234 I Display: Using screen 'Colour LCD' (Make: Unknown Model: Unknown)
>02.621253 I Display: Qt screen pixel ratio: 1.00
>02.621283 I Display: Geometry: 1792x1120+0+0 Size(Qt): 344.824mmx214.702mm
>02.629084 N Display: Desktop video mode: 1792x1120 60.000Hz
>ic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
>03.250188 I Power: Battery at 100%
>03.250310 I Power: Supported actions: Suspend,Restart,Shutdown
>03.641367 I Listening on TCP 0.0.0.0:6547
>03.661254 I Listening on TCP [::]:6547
>
>----------------------------------------
>What is this
>---------------------------------------
>
>11.012437 I Loading en_us translation for module mythfrontend
>11.122577 E LIRC: Failed to connect to Unix socket '/var/run/lirc/lircd'
>ile or directory (2)
>11.123518 E AppleRemote::_findAppleRemoteDevice(AppleIRController) failed
>11.123544 E AppleRemote::_findAppleRemoteDevice(AppleTVIRReceiver) failed
>11.123552 E AppleRemote::startListening() failed
>11.123586 I UDPListener: Enabling
>11.131896 I Binding to UDP 0.0.0.0:6948
>11.131956 I Binding to UDP [::]:6948
>12.047050 I Using Frameless Window
>12.047063 I Using Full Screen Window
>12.057267 I Display: Have main widget
>12.057288 I Display: Have main window
>12.067090 I Display: Found screen 'Colour LCD'
>12.098587 I UI Screen Resolution: 1792 x 1120
>12.237759 I OpenGL: OpenGL vendor : Intel Inc.
>12.237770 I OpenGL: OpenGL renderer : Intel(R) UHD Graphics 630
>12.237777 I OpenGL: OpenGL version : 2.1 INTEL-14.6.18
>12.237785 I OpenGL: Qt platform : cocoa
>12.237791 I OpenGL: Qt OpenGL format : OpenGL 2.1
>12.237799 I OpenGL: Qt OpenGL surface : RGBA: 888-1 Depth: 0 Stencil: 0
>12.237805 I OpenGL: Max texture size : 16384
>12.237811 I OpenGL: Max texture units : 16
>12.237819 I OpenGL: Shaders : Yes
>12.237827 I OpenGL: NPOT textures : Yes
>12.237833 I OpenGL: Multitexturing : Yes
>12.237838 I OpenGL: Rectangular textures : Yes
>12.237844 I OpenGL: Buffer mapping : Yes
>12.237851 I OpenGL: Framebuffer objects : Yes
>12.237857 I OpenGL: 16bit framebuffers : Yes
>12.237863 I OpenGL: Unpack Subimage : Yes
>12.237869 I OpenGL: GL_RED/GL_R8 : Yes
>12.246385 I OpenGL: Initialised MythRenderOpenGL
>12.246393 I OpenGL: Using full range output
>12.246437 I High DPI scaling disabled
>12.269403 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
>12.274189 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
>12.274244 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
>12.295615 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
>ylib, 1): no suitable image found. Did find:
>thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
>13.292341 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.5.33:6543 (try 1 of 1)
>13.301605 I MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
>13.345602 E CECAdapter: Failed to load libcec.
>13.354158 E RAOP Device: Aborting startup - no key found.
>13.362064 I AirPlay: Created airplay objects.
>13.362197 I Listening on TCP 0.0.0.0:5100
>13.362260 I Listening on TCP [::]:5100
>13.458092 I Current MythTV Schema Version (DBSchemaVer): 1361
>13.485082 I VTBDec: Supported/available VideoToolbox decoders:
>13.485102 I VTBDec: H264
>13.485108 I VTBDec: HEVC
>
>---------------------------------------------------
>GUI up and running
>Now exit
>---------------------------------------------------

The logs say that mythfrontend is still starting up here.

>14.061260 I Bonjour: Service registration complete: name 'MythTV on plasma.home' type '_airplay._tcp.' domain: 'local.'
>20.879759 N Registering Internal as a media playback plugin.
>20.914671 W No plugins directory /Applications/Mythfrontend.app/Contents/Resources/lib/mythtv/plugins
>20.974499 I Using Frameless Window
>20.974514 I Using Full Screen Window
>20.982686 I Display: Have main widget
>20.982700 I Display: Have main window
>21.026 mythfrontend.real[4207:201300] not in fullscreen state
>20.997174 I Display: Found screen 'Colour LCD'
>20.997209 I Display: Waiting for new screen
>21.024347 I Bonjour: Service registration complete: name 'Mythfrontend on plasma.home' type '_mythfrontend._tcp.' domain: 'local.'
>21.473519 W Display: Timed out waiting for new screen
>21.492106 I UI Screen Resolution: 1792 x 1120
>21.559729 I OpenGL: Initialised MythRenderOpenGL
>21.559740 I OpenGL: Using full range output
>21.559776 I High DPI scaling disabled
>21.596433 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
>21.601489 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
>21.601552 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
>21.623046 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
>ylib, 1): no suitable image found. Did find:
>thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
>21.824091 E CECAdapter: Failed to load libcec.
>21.824148 W MythPainter: 1 images not yet de-allocated.
>21.824167 I Clearing OpenGL painter cache.
>21.825898 I OpenGL: MythRenderOpenGL closing
>21.951746 N Found mainmenu.xml for theme 'MythCenter-wide'
>22.049329 I Checking for theme updates every hour
>22.058027 I Starting HouseKeeper.
>22.058358 I Starting process manager
>22.058390 I Starting process signal handler
>22.058634 I Starting IO manager (read)
>22.058896 I Starting IO manager (write)

This is where the startup is complete.

>35.124192 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
>35.128853 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
>35.128910 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
>35.151154 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
>35.917695 I Bonjour: De-registering service '_mythfrontend._tcp.' on 'Mythfrontend on plasma.home'
>35.937750 W MythPainter: 61 images not yet de-allocated.
>35.937793 I Clearing OpenGL painter cache.
>35.940032 I OpenGL: MythRenderOpenGL closing
>35.942244 I Display: Deleting
>35.948702 I RAOP Device: Cleaning up.
>35.948722 I AirPlay: Cleaning up.
>35.948834 I Bonjour: De-registering service '_airplay._tcp.' on 'MythTV on plasma.home'
>35.949171 I Shutting down UPnP client...
>42.983810 I Waiting for threads to exit.
>49.795710 I Exiting

There are lots of things that can affect the startup time for
mythfrontend. In my case, I have a huge database, and I have been
attributing slow startup to that. My mother's system has a much
smaller database and mythfrontend starts faster there than on mine,
but there is still a significant wait, and I am not sure there is any
good reason for it. But finding the source of the slowness will
probably need more detailed debug output.

In your case, some questions to rule out some obvious things.

Is your local network IPv6 capable? Does it have IPv6 connection to
the Internet with delegated IPv6 addressing so that your devices have
global unicast IPv6 addresses? The "ip addr" command on Linux will
show IPv6 addresses marked as "scope global" if you do have delegated
IPv6 addressing.

Do you run a local DNS server for your network? How are the IP
addresses of your devices specified to MythTV - do you use hostnames
or IP addresses?

Do you have any hard drives on the mythfrontend or mythbackend PCs
that stop rotating and sleep when they are not being used? Do they
need to be started for MythTV to use?
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
Stephen thanks for input

> There are lots of things that can affect the startup time for
> mythfrontend. In my case, I have a huge database, and I have been
> attributing slow startup to that. My mother's system has a much
> smaller database and mythfrontend starts faster there than on mine,
> but there is still a significant wait, and I am not sure there is any
> good reason for it. But finding the source of the slowness will
> probably need more detailed debug output.
>
> In your case, some questions to rule out some obvious things.
>
> Is your local network IPv6 capable? Does it have IPv6 connection to
> the Internet with delegated IPv6 addressing so that your devices have
> global unicast IPv6 addresses? The "ip addr" command on Linux will
> show IPv6 addresses marked as "scope global" if you do have delegated
> IPv6 addressing.

There is no ipv6 on my network

> Do you run a local DNS server for your network? How are the IP
> addresses of your devices specified to MythTV - do you use hostnames
> or IP addresses?

I do run a local DNS server. I found dnsmasq does what I want. All mythtv refs are by IP not by name.

> Do you have any hard drives on the mythfrontend or mythbackend PCs
> that stop rotating and sleep when they are not being used? Do they
> need to be started for MythTV to use?

The main disk is m2 - hdparm says about 2500 M/S
/store is a SATA SSH. hdparm says about 530 M/S

I run trim once per day (at 4 ayem)

Hmmm
James

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
11.122577 E LIRC: Failed to connect to Unix socket '/var/run/lirc/lircd'
ile or directory (2)
11.123518 E AppleRemote::_findAppleRemoteDevice(AppleIRController) failed
11.123544 E AppleRemote::_findAppleRemoteDevice(AppleTVIRReceiver) failed
11.123552 E AppleRemote::startList




12.295615 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
ylib, 1): no suitable image found. Did find:
thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20





13.345602 E CECAdapter: Failed to load libcec.
13.354158 E RAOP Device: Aborting startup - no key found.
13.362064 I AirPlay: Created airplay objects.




20.914671 W No plugins directory /Applications/Mythfrontend.app/Contents/Resources/lib/mythtv/plugins





21.623046 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
ylib, 1): no suitable image found. Did find:
thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
21.824091 E CECAdapter: Failed to load libcec.
21.824148 W MythPainter: 1 images not yet de-allocated.


These are probably good candidates for a starting point. IIRC airplay has not worked in some years so may not be worth having enabled.

11.122577 E LIRC: Failed to connect to Unix socket '/var/run/lirc/lircd'
ile or directory (2)
11.123518 E AppleRemote::_findAppleRemoteDevice(AppleIRController) failed
11.123544 E AppleRemote::_findAppleRemoteDevice(AppleTVIRReceiver) failed
11.123552 E AppleRemote::startList




12.295615 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
ylib, 1): no suitable image found. Did find:
thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20





13.345602 E CECAdapter: Failed to load libcec.
13.354158 E RAOP Device: Aborting startup - no key found.
13.362064 I AirPlay: Created airplay objects.




20.914671 W No plugins directory /Applications/Mythfrontend.app/Contents/Resources/lib/mythtv/plugins





21.623046 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
ylib, 1): no suitable image found. Did find:
thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
21.824091 E CECAdapter: Failed to load libcec.
21.824148 W MythPainter: 1 images not yet de-allocated.


These are probably good candidates for a starting point. IIRC airplay has not worked in some years so may not be worth having enabled.
Re: Getting slower [ In reply to ]
On 8/3/20 12:14 AM, Stephen Worthington wrote:
> On Mon, 3 Aug 2020 07:00:36 +0800, you wrote:
>
>> Over the last few releases mythtv has got slower to start and stop.
>> What is the delay looking for ipv6 dtuff?
> There is no delay from IPv6 - that is a red herring.
>
>> This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>>
>> If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>>
>> James
>>
>> 00.730068 I Setup Interrupt: 2 handler
>> 00.730091 I Setup Terminated: 15 handler
>> 00.730098 I Setup Segmentation fault: 11 handler
>> 00.730104 I Setup Abort trap: 6 handler
>> 00.730109 I Setup Bus error: 10 handler
>> 00.730115 I Setup Floating point exception: 8 handler
>> 00.730123 I Setup Illegal instruction: 4 handler
>> 00.730130 I Setup User defined signal 1: 30 handler
>> 00.730137 I Setup User defined signal 2: 31 handler
>> 00.730144 I Setup Hangup: 1 handler
>> 00.730215 C mythfrontend version: fixes/31 [v31.0-81-g05a613f9fa] www.mythtv.org
>> 00.730224 C Qt version: compile: 5.14.2, runtime: 5.14.2
>> 00.730243 I macOS 10.15 (x86_64)
>> 00.730249 N Enabled verbose msgs: general
>> 00.730266 N Setting Log Level to LOG_INFO
>> 00.741674 I Added logging to the console
>> 00.742843 N Using runtime prefix = /Applications/Mythfrontend.app/Contents/Resources
>> 00.742867 N Using configuration directory = /Users/jam/.mythtv
>> 00.743495 I Assumed character encoding: en_AU.UTF-8
>> 00.747012 I Loading en_us translation for module mythfrontend
>> 00.747443 I Empty LocalHostName. This is typical.
>> 00.747457 I Using a profile name of: 'plasma.home' (Usually the same as this host's name.)
>> 00.747563 I Start up testing connections. DB 192.168.5.33, BE , attempt 0, status dbAwake, Delay: 2000
>> 02.562399 N Setting QT default locale to en_AU
>> 02.562434 I Current locale en_AU
>> 02.562575 E No locale defaults file for en_AU, skipping
>> 02.621197 I Display: Found screen 'Colour LCD'
>> 02.621234 I Display: Using screen 'Colour LCD' (Make: Unknown Model: Unknown)
>> 02.621253 I Display: Qt screen pixel ratio: 1.00
>> 02.621283 I Display: Geometry: 1792x1120+0+0 Size(Qt): 344.824mmx214.702mm
>> 02.629084 N Display: Desktop video mode: 1792x1120 60.000Hz
>> ic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
>> 03.250188 I Power: Battery at 100%
>> 03.250310 I Power: Supported actions: Suspend,Restart,Shutdown
>> 03.641367 I Listening on TCP 0.0.0.0:6547
>> 03.661254 I Listening on TCP [::]:6547
>>
>> ----------------------------------------
>> What is this
>> ---------------------------------------
>>
>> 11.012437 I Loading en_us translation for module mythfrontend
>> 11.122577 E LIRC: Failed to connect to Unix socket '/var/run/lirc/lircd'
>> ile or directory (2)
>> 11.123518 E AppleRemote::_findAppleRemoteDevice(AppleIRController) failed
>> 11.123544 E AppleRemote::_findAppleRemoteDevice(AppleTVIRReceiver) failed
>> 11.123552 E AppleRemote::startListening() failed
>> 11.123586 I UDPListener: Enabling
>> 11.131896 I Binding to UDP 0.0.0.0:6948
>> 11.131956 I Binding to UDP [::]:6948
>> 12.047050 I Using Frameless Window
>> 12.047063 I Using Full Screen Window
>> 12.057267 I Display: Have main widget
>> 12.057288 I Display: Have main window
>> 12.067090 I Display: Found screen 'Colour LCD'
>> 12.098587 I UI Screen Resolution: 1792 x 1120
>> 12.237759 I OpenGL: OpenGL vendor : Intel Inc.
>> 12.237770 I OpenGL: OpenGL renderer : Intel(R) UHD Graphics 630
>> 12.237777 I OpenGL: OpenGL version : 2.1 INTEL-14.6.18
>> 12.237785 I OpenGL: Qt platform : cocoa
>> 12.237791 I OpenGL: Qt OpenGL format : OpenGL 2.1
>> 12.237799 I OpenGL: Qt OpenGL surface : RGBA: 888-1 Depth: 0 Stencil: 0
>> 12.237805 I OpenGL: Max texture size : 16384
>> 12.237811 I OpenGL: Max texture units : 16
>> 12.237819 I OpenGL: Shaders : Yes
>> 12.237827 I OpenGL: NPOT textures : Yes
>> 12.237833 I OpenGL: Multitexturing : Yes
>> 12.237838 I OpenGL: Rectangular textures : Yes
>> 12.237844 I OpenGL: Buffer mapping : Yes
>> 12.237851 I OpenGL: Framebuffer objects : Yes
>> 12.237857 I OpenGL: 16bit framebuffers : Yes
>> 12.237863 I OpenGL: Unpack Subimage : Yes
>> 12.237869 I OpenGL: GL_RED/GL_R8 : Yes
>> 12.246385 I OpenGL: Initialised MythRenderOpenGL
>> 12.246393 I OpenGL: Using full range output
>> 12.246437 I High DPI scaling disabled
>> 12.269403 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
>> 12.274189 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
>> 12.274244 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
>> 12.295615 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
>> ylib, 1): no suitable image found. Did find:
>> thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
>> 13.292341 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.5.33:6543 (try 1 of 1)
>> 13.301605 I MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
>> 13.345602 E CECAdapter: Failed to load libcec.
>> 13.354158 E RAOP Device: Aborting startup - no key found.
>> 13.362064 I AirPlay: Created airplay objects.
>> 13.362197 I Listening on TCP 0.0.0.0:5100
>> 13.362260 I Listening on TCP [::]:5100
>> 13.458092 I Current MythTV Schema Version (DBSchemaVer): 1361
>> 13.485082 I VTBDec: Supported/available VideoToolbox decoders:
>> 13.485102 I VTBDec: H264
>> 13.485108 I VTBDec: HEVC
>>
>> ---------------------------------------------------
>> GUI up and running
>> Now exit
>> ---------------------------------------------------
> The logs say that mythfrontend is still starting up here.
>
>> 14.061260 I Bonjour: Service registration complete: name 'MythTV on plasma.home' type '_airplay._tcp.' domain: 'local.'
>> 20.879759 N Registering Internal as a media playback plugin.
>> 20.914671 W No plugins directory /Applications/Mythfrontend.app/Contents/Resources/lib/mythtv/plugins
>> 20.974499 I Using Frameless Window
>> 20.974514 I Using Full Screen Window
>> 20.982686 I Display: Have main widget
>> 20.982700 I Display: Have main window
>> 21.026 mythfrontend.real[4207:201300] not in fullscreen state
>> 20.997174 I Display: Found screen 'Colour LCD'
>> 20.997209 I Display: Waiting for new screen
>> 21.024347 I Bonjour: Service registration complete: name 'Mythfrontend on plasma.home' type '_mythfrontend._tcp.' domain: 'local.'
>> 21.473519 W Display: Timed out waiting for new screen
>> 21.492106 I UI Screen Resolution: 1792 x 1120
>> 21.559729 I OpenGL: Initialised MythRenderOpenGL
>> 21.559740 I OpenGL: Using full range output
>> 21.559776 I High DPI scaling disabled
>> 21.596433 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
>> 21.601489 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
>> 21.601552 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
>> 21.623046 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
>> ylib, 1): no suitable image found. Did find:
>> thfrontend.app/Contents/MacOS/../Frameworks/libcec.4.0.5.dylib/libcec.4.dylib: stat() failed with errno=20
>> 21.824091 E CECAdapter: Failed to load libcec.
>> 21.824148 W MythPainter: 1 images not yet de-allocated.
>> 21.824167 I Clearing OpenGL painter cache.
>> 21.825898 I OpenGL: MythRenderOpenGL closing
>> 21.951746 N Found mainmenu.xml for theme 'MythCenter-wide'
>> 22.049329 I Checking for theme updates every hour
>> 22.058027 I Starting HouseKeeper.
>> 22.058358 I Starting process manager
>> 22.058390 I Starting process signal handler
>> 22.058634 I Starting IO manager (read)
>> 22.058896 I Starting IO manager (write)
> This is where the startup is complete.
>
>> 35.124192 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
>> 35.128853 I MythUIHelper: Kept 69 files, deleted 0 files, stat error on 0 files
>> 35.128910 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
>> 35.151154 I MythUIHelper: Kept 423 files, deleted 0 files, stat error on 0 files
>> 35.917695 I Bonjour: De-registering service '_mythfrontend._tcp.' on 'Mythfrontend on plasma.home'
>> 35.937750 W MythPainter: 61 images not yet de-allocated.
>> 35.937793 I Clearing OpenGL painter cache.
>> 35.940032 I OpenGL: MythRenderOpenGL closing
>> 35.942244 I Display: Deleting
>> 35.948702 I RAOP Device: Cleaning up.
>> 35.948722 I AirPlay: Cleaning up.
>> 35.948834 I Bonjour: De-registering service '_airplay._tcp.' on 'MythTV on plasma.home'
>> 35.949171 I Shutting down UPnP client...
>> 42.983810 I Waiting for threads to exit.
>> 49.795710 I Exiting
> There are lots of things that can affect the startup time for
> mythfrontend. In my case, I have a huge database, and I have been
> attributing slow startup to that. My mother's system has a much
> smaller database and mythfrontend starts faster there than on mine,
> but there is still a significant wait, and I am not sure there is any
> good reason for it. But finding the source of the slowness will
> probably need more detailed debug output.
>
> In your case, some questions to rule out some obvious things.
>
> Is your local network IPv6 capable? Does it have IPv6 connection to
> the Internet with delegated IPv6 addressing so that your devices have
> global unicast IPv6 addresses? The "ip addr" command on Linux will
> show IPv6 addresses marked as "scope global" if you do have delegated
> IPv6 addressing.
>
> Do you run a local DNS server for your network? How are the IP
> addresses of your devices specified to MythTV - do you use hostnames
> or IP addresses?
>
> Do you have any hard drives on the mythfrontend or mythbackend PCs
> that stop rotating and sleep when they are not being used? Do they
> need to be started for MythTV to use?

I just tested on a Core i7 desktop remote frontend with no remote,
standard install only 5 programs in the database. System built yesterday.

starting from the launch icon it took 10 seconds to get to the menu.

If if started from xterm: mythfrontend -O libCECEnabled=0   it took 7
seconds.

I have a really long delay on a Shield TV where the TV has CEC disabled
but it's capable.  I just don't know how to start mythfrontend on the
Shield TV with CEC disabled (-O libCECEnabled=0)

Jim A


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On Mon, 3 Aug 2020 12:26:28 +0800, you wrote:

>Stephen thanks for input
>
>> There are lots of things that can affect the startup time for
>> mythfrontend. In my case, I have a huge database, and I have been
>> attributing slow startup to that. My mother's system has a much
>> smaller database and mythfrontend starts faster there than on mine,
>> but there is still a significant wait, and I am not sure there is any
>> good reason for it. But finding the source of the slowness will
>> probably need more detailed debug output.
>>
>> In your case, some questions to rule out some obvious things.
>>
>> Is your local network IPv6 capable? Does it have IPv6 connection to
>> the Internet with delegated IPv6 addressing so that your devices have
>> global unicast IPv6 addresses? The "ip addr" command on Linux will
>> show IPv6 addresses marked as "scope global" if you do have delegated
>> IPv6 addressing.
>
>There is no ipv6 on my network

You are very likely wrong about that. Unless you have manually
disabled IPv6, it will be working but only using link-local addresses,
and so can only be being used for connections between devices on the
same subnet. Windows, Linux and Mac all do this. If you look at the
output of the "ip addr" command, you will see "inet6" lines, with the
link-local addresses, which start with "fe80:". Those lines should
end with "scope link".

The log you posted shows mythfrontend listening on IPv6. That does
not mean that it is actually doing IPv6 connections though - that
would only happen if you gave it link-local IPv6 addresses to connect
to. So unless you have done that, the fact that things are listening
on IPv6 sockets is of no consequence. It certainly will not be
causing delays.

>> Do you run a local DNS server for your network? How are the IP
>> addresses of your devices specified to MythTV - do you use hostnames
>> or IP addresses?
>
>I do run a local DNS server. I found dnsmasq does what I want. All mythtv refs are by IP not by name.

So that is irrelevant also, as you are not doing DNS lookups.

>> Do you have any hard drives on the mythfrontend or mythbackend PCs
>> that stop rotating and sleep when they are not being used? Do they
>> need to be started for MythTV to use?
>
>The main disk is m2 - hdparm says about 2500 M/S
>/store is a SATA SSH. hdparm says about 530 M/S
>
>I run trim once per day (at 4 ayem)

Ok, that is not the problem then. Even if SSDs do go into low power
modes (and I have not checked if they do), the startup times will not
be significant.

So then, how do we find out what is causing the delays? The first
thing I can think of is to run Wireshark on either the frontend or
backend box and have it capture all traffic between the frontend and
backend. A simple "host <IP address> capture filter should be all
that is needed. Then start mythfrontend exactly at a known time and
see when the traffic from mythfrontend happens and what ports it is
going to, as well as the content. To start mythfrontend at a specific
time, you can do it from a command prompt, rather than the GUI, like
this:

sleepuntil 22:25; mythfrontend

You can get the sleepuntil script from my web server:

http://www.jsw.gen.nz/mythtv/sleepuntil

You can also increase the logging of mythfrontend:

mythfrontend.real --setloglevel debug

And also the verbosity - see the output of these for the options:

mythfrontend.real -h
mythfrontend.real -v help
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 03/08/2020 10:05, Jim Abernathy wrote:
>
>
> I just tested on a Core i7 desktop remote frontend with no remote,
> standard install only 5 programs in the database. System built yesterday.
>
> starting from the launch icon it took 10 seconds to get to the menu.
>
> If if started from xterm: mythfrontend -O libCECEnabled=0   it took 7
> seconds.
>
> I have a really long delay on a Shield TV where the TV has CEC disabled
> but it's capable.  I just don't know how to start mythfrontend on the
> Shield TV with CEC disabled (-O libCECEnabled=0)
>
> Jim A
>
My firetvstick 4k also pauses on mythfrontend startup for what seems
'quite long' but on testing looks like less than 20 seconds. Maybe it's
longer after an update.

Its frontend log (adb logcat mfe:D *:S) complains about a bad locale
setting and multiple missing instances of themeinfo.xml files; gives
info on font substitutions and enumerates codecs. After that it
'attempted to flush to a non-raster surface' and suggests (consider
using Qt::WA_PaintOnScreen to exclude from backingstore sync) before
displaying the frontend menu.

It works well with UK DVB-T SD content but some 1080 stuff suffers from
a lack of available power.

John P
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 8/3/20 5:05 AM, Jim Abernathy wrote:
> I have a really long delay on a Shield TV where the TV has CEC
> disabled but it's capable.  I just don't know how to start
> mythfrontend on the Shield TV with CEC disabled (-O libCECEnabled=0)

There is now a setting on mythfrontend
Setup->General->Remote Control->Enable CEC where you can turn CEC on or
off instead of using -O libCECEnabled
I am not sure when that was added but it is in V31 and master, pehaps
also V30.

CEC on Android does not use the MythTV CEC code, so even if you turn off
CEC in MythTV it will still work through android.

Peter


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 03/08/2020 05:26, jam wrote:
> Stephen thanks for input
>
>> There are lots of things that can affect the startup time for
>> mythfrontend. In my case, I have a huge database, and I have been
>> attributing slow startup to that. My mother's system has a much
>> smaller database and mythfrontend starts faster there than on mine,
>> but there is still a significant wait, and I am not sure there is any
>> good reason for it. But finding the source of the slowness will
>> probably need more detailed debug output.
>>
>> In your case, some questions to rule out some obvious things.
>>
>> Is your local network IPv6 capable? Does it have IPv6 connection to
>> the Internet with delegated IPv6 addressing so that your devices have
>> global unicast IPv6 addresses? The "ip addr" command on Linux will
>> show IPv6 addresses marked as "scope global" if you do have delegated
>> IPv6 addressing.
>
> There is no ipv6 on my network
>
>> Do you run a local DNS server for your network? How are the IP
>> addresses of your devices specified to MythTV - do you use hostnames
>> or IP addresses?
>
> I do run a local DNS server. I found dnsmasq does what I want. All mythtv refs are by IP not by name.

by IP addresses, which are IPv4, therefore IPv6 is irrelevant

Even if you run full dual stack (like i do) you will find that
normally connections are over ipv4 anyway.

Having said that, there is slowness to shutdown. I have seen that,
clearly some of the threads aren't shutting down in a timely manner.
(also applies to the backend)

I'll keep an eye out for startup slowness, but i've not seen that.


Regards
Stuart
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On Mon, Aug 3, 2020 at 9:30 AM Peter Bennett <pb.mythtv@gmail.com> wrote:

>
>
> On 8/3/20 5:05 AM, Jim Abernathy wrote:
> > I have a really long delay on a Shield TV where the TV has CEC
> > disabled but it's capable. I just don't know how to start
> > mythfrontend on the Shield TV with CEC disabled (-O libCECEnabled=0)
>
> There is now a setting on mythfrontend
> Setup->General->Remote Control->Enable CEC where you can turn CEC on or
> off instead of using -O libCECEnabled
> I am not sure when that was added but it is in V31 and master, pehaps
> also V30.
>
> CEC on Android does not use the MythTV CEC code, so even if you turn off
> CEC in MythTV it will still work through android.
>
> Peter
>

This is good to know. I set it on a PC based v31 frontend and it knocked
the startup from 10 sec to 7 sec.
BTW, I didn't see that option in the android mythfrontend. But as you
stated...

The Shield TV starts up mythfrontend in 10 seconds for me.
The FireTV 4K starts up in 20 seconds.
Jim A
Re: Getting slower [ In reply to ]
On 8/2/20 4:00 PM, jam@tigger.ws wrote:
> Over the last few releases mythtv has got slower to start and stop.
> What is the delay looking for ipv6 dtuff?
>
> This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>
> If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>
> James
>
> 00.730068 I Setup Interrupt: 2 handler
> 00.730091 I Setup Terminated: 15 handler
> 00.730098 I Setup Segmentation fault: 11 handler
> 00.730104 I Setup Abort trap: 6 handler
> 00.730109 I Setup Bus error: 10 handler
> 00.730115 I Setup Floating point exception: 8 handler
> 00.730123 I Setup Illegal instruction: 4 handler
> 00.730130 I Setup User defined signal 1: 30 handler
> 00.730137 I Setup User defined signal 2: 31 handler
> .....

I finally caught a slow startup (my wife usually has it started by the
time I get to it) and here's the frontend output:

> /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
libCECEnabled=0 -geometry 1920x1080+1920+0
qt.core.logging: Ignoring malformed logging rule: '’*.debug=false’'
"Display: Requesting EGL for 'Mesa Project, 1.4'"
2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Interrupt handler
2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Terminated handler
2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Segmentation fault handler
2020-08-08 20:44:32.526300 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Aborted handler
2020-08-08 20:44:32.526311 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Bus error handler
2020-08-08 20:44:32.526321 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Floating point exception
handler
2020-08-08 20:44:32.526344 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Illegal instruction handler
2020-08-08 20:44:32.526358 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Real-time signal 0 handler
2020-08-08 20:44:32.526378 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup User defined signal 1
handler
2020-08-08 20:44:32.526387 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup User defined signal 2
handler
2020-08-08 20:44:32.526402 I [2264517/2264517] thread_unknown
signalhandling.cpp:191:SetHandlerPrivate  Setup Hangup handler
2020-08-08 20:44:32.526587 C [2264517/2264517] thread_unknown
mythcommandlineparser.cpp:2602:ConfigureLogging  mythfrontend version:
fixes/31 [v31.0-v31.0-47-gfc90482281] www.mythtv.org
2020-08-08 20:44:32.526606 C [2264517/2264517] thread_unknown
mythcommandlineparser.cpp:2606:ConfigureLogging  Qt version: compile:
5.13.2, runtime: 5.13.2
2020-08-08 20:44:32.526669 I [2264517/2264517] thread_unknown
mythcommandlineparser.cpp:2608:ConfigureLogging  Fedora 31 (Workstation
Edition) (x86_64)
2020-08-08 20:44:32.526674 N [2264517/2264517] thread_unknown
mythcommandlineparser.cpp:2610:ConfigureLogging  Enabled verbose msgs: 
general
2020-08-08 20:44:32.863781 E [2264517/2264517] CoreContext
mythdb.cpp:181:DBError  DB Error (StorageGroup::StorageGroup()):
Query was:

Driver error was [1/]:
Driver not loaded
Database error was:
Driver not loaded

2020-08-08 20:44:32.969563 E [2264517/2264517] CoreContext
serverpool.cpp:550:bind  Failed binding to UDP [::]:0 - Error 10:
Protocol type not supported
libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
2020-08-08 20:44:37.078916 E [2264517/2264517] CoreContext
serverpool.cpp:427:listen  Failed listening on TCP [::]:6547 - Error 10:
Protocol type not supported
libva info: VA-API version 1.6.0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
libva info: VA-API version 1.6.0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
Cannot load libcuda.so.1

The above lines come out very quickly, then the hard drive thrashes for
a long time before the next line comes up and the menu appears on the
screen.  The difference between the timestamps (20:44:37 to 20:45:25) is
pretty much the time the hard drive is working (48 secs).

2020-08-08 20:45:25.153977 A [2264517/2264517] CoreContext
mediamonitor-unix.cpp:204:CheckMountable  MMUnix:CheckMountable: DBus
interface error: The name is not activatable
2020-08-08 20:45:25.155653 W [2264517/2264517] CoreContext
mediamonitor-unix.cpp:212:CheckMountable  MMUnix:UDisks2 service found.
Media Monitor does not support this yet!
2020-08-08 20:45:25.204403 W [2264517/2264517] CoreContext
mythplugin.cpp:110:MythPluginManager  No libraries in plugins directory
/usr/lib64/mythtv/plugins

All is normal after that.  Should I increase the verbosity?  Will it
tell me what's going on during all that hard drive activity? After this
startup, I exited and re-ran the frontend and it was ready to go in
about 6 seconds.  Here's that output:

2020-08-08 20:50:11.231130 I [2265508/2265508] thread_unknown
mythcommandlineparser.cpp:2608:ConfigureLogging  Fedora 31 (Workstation
Edition) (x86_64)
2020-08-08 20:50:11.231131 N [2265508/2265508] thread_unknown
mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs: 
general
2020-08-08 20:50:11.341611 E [2265508/2265508] CoreContext
mythdb.cpp:181:DBError  DB Error (StorageGroup::StorageGroup()):
Query was:

Driver error was [1/]:
Driver not loaded
Database error was:
Driver not loaded

2020-08-08 20:50:11.388052 E [2265508/2265508] CoreContext
serverpool.cpp:550:bind  Failed binding to UDP [::]:0 - Error 10:
Protocol type not supported
libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
2020-08-08 20:50:14.259651 E [2265508/2265508] CoreContext
serverpool.cpp:427:listen  Failed listening on TCP [::]:6547 - Error 10:
Protocol type not supported
libva info: VA-API version 1.6.0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
libva info: VA-API version 1.6.0
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
Cannot load libcuda.so.1
2020-08-08 20:50:17.821604 A [2265508/2265508] CoreContext
mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
interface error: The name is not activatable
2020-08-08 20:50:17.822071 W [2265508/2265508] CoreContext
mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
Media Monitor does not support this yet!

Same output, very different startup time.  What's the difference?

Dave D.


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On Sat, 8 Aug 2020 21:12:41 -0700, you wrote:

>On 8/2/20 4:00 PM, jam@tigger.ws wrote:
>> Over the last few releases mythtv has got slower to start and stop.
>> What is the delay looking for ipv6 dtuff?
>>
>> This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>>
>> If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>>
>> James
>>
>> 00.730068 I Setup Interrupt: 2 handler
>> 00.730091 I Setup Terminated: 15 handler
>> 00.730098 I Setup Segmentation fault: 11 handler
>> 00.730104 I Setup Abort trap: 6 handler
>> 00.730109 I Setup Bus error: 10 handler
>> 00.730115 I Setup Floating point exception: 8 handler
>> 00.730123 I Setup Illegal instruction: 4 handler
>> 00.730130 I Setup User defined signal 1: 30 handler
>> 00.730137 I Setup User defined signal 2: 31 handler
>> .....
>
>I finally caught a slow startup (my wife usually has it started by the
>time I get to it) and here's the frontend output:
>
> > /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
>libCECEnabled=0 -geometry 1920x1080+1920+0
>qt.core.logging: Ignoring malformed logging rule: '?*.debug=false?'
>"Display: Requesting EGL for 'Mesa Project, 1.4'"
>2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Interrupt handler
>2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Terminated handler
>2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Segmentation fault handler
>2020-08-08 20:44:32.526300 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Aborted handler
>2020-08-08 20:44:32.526311 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Bus error handler
>2020-08-08 20:44:32.526321 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Floating point exception
>handler
>2020-08-08 20:44:32.526344 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Illegal instruction handler
>2020-08-08 20:44:32.526358 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Real-time signal 0 handler
>2020-08-08 20:44:32.526378 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup User defined signal 1
>handler
>2020-08-08 20:44:32.526387 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup User defined signal 2
>handler
>2020-08-08 20:44:32.526402 I [2264517/2264517] thread_unknown
>signalhandling.cpp:191:SetHandlerPrivate? Setup Hangup handler
>2020-08-08 20:44:32.526587 C [2264517/2264517] thread_unknown
>mythcommandlineparser.cpp:2602:ConfigureLogging? mythfrontend version:
>fixes/31 [v31.0-v31.0-47-gfc90482281] www.mythtv.org
>2020-08-08 20:44:32.526606 C [2264517/2264517] thread_unknown
>mythcommandlineparser.cpp:2606:ConfigureLogging? Qt version: compile:
>5.13.2, runtime: 5.13.2
>2020-08-08 20:44:32.526669 I [2264517/2264517] thread_unknown
>mythcommandlineparser.cpp:2608:ConfigureLogging? Fedora 31 (Workstation
>Edition) (x86_64)
>2020-08-08 20:44:32.526674 N [2264517/2264517] thread_unknown
>mythcommandlineparser.cpp:2610:ConfigureLogging? Enabled verbose msgs:?
>general
>2020-08-08 20:44:32.863781 E [2264517/2264517] CoreContext
>mythdb.cpp:181:DBError? DB Error (StorageGroup::StorageGroup()):
>Query was:
>
>Driver error was [1/]:
>Driver not loaded
>Database error was:
>Driver not loaded
>
>2020-08-08 20:44:32.969563 E [2264517/2264517] CoreContext
>serverpool.cpp:550:bind? Failed binding to UDP [::]:0 - Error 10:
>Protocol type not supported
>libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>2020-08-08 20:44:37.078916 E [2264517/2264517] CoreContext
>serverpool.cpp:427:listen? Failed listening on TCP [::]:6547 - Error 10:
>Protocol type not supported
>libva info: VA-API version 1.6.0
>libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>libva info: Found init function __vaDriverInit_1_6
>libva info: va_openDriver() returns 0
>libva info: VA-API version 1.6.0
>libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>libva info: Found init function __vaDriverInit_1_6
>libva info: va_openDriver() returns 0
>Cannot load libcuda.so.1
>
>The above lines come out very quickly, then the hard drive thrashes for
>a long time before the next line comes up and the menu appears on the
>screen.? The difference between the timestamps (20:44:37 to 20:45:25) is
>pretty much the time the hard drive is working (48 secs).
>
>2020-08-08 20:45:25.153977 A [2264517/2264517] CoreContext
>mediamonitor-unix.cpp:204:CheckMountable? MMUnix:CheckMountable: DBus
>interface error: The name is not activatable
>2020-08-08 20:45:25.155653 W [2264517/2264517] CoreContext
>mediamonitor-unix.cpp:212:CheckMountable? MMUnix:UDisks2 service found.
>Media Monitor does not support this yet!
>2020-08-08 20:45:25.204403 W [2264517/2264517] CoreContext
>mythplugin.cpp:110:MythPluginManager? No libraries in plugins directory
>/usr/lib64/mythtv/plugins
>
>All is normal after that.? Should I increase the verbosity?? Will it
>tell me what's going on during all that hard drive activity? After this
>startup, I exited and re-ran the frontend and it was ready to go in
>about 6 seconds.? Here's that output:
>
>2020-08-08 20:50:11.231130 I [2265508/2265508] thread_unknown
>mythcommandlineparser.cpp:2608:ConfigureLogging? Fedora 31 (Workstation
>Edition) (x86_64)
>2020-08-08 20:50:11.231131 N [2265508/2265508] thread_unknown
>mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs:?
>general
>2020-08-08 20:50:11.341611 E [2265508/2265508] CoreContext
>mythdb.cpp:181:DBError? DB Error (StorageGroup::StorageGroup()):
>Query was:
>
>Driver error was [1/]:
>Driver not loaded
>Database error was:
>Driver not loaded
>
>2020-08-08 20:50:11.388052 E [2265508/2265508] CoreContext
>serverpool.cpp:550:bind? Failed binding to UDP [::]:0 - Error 10:
>Protocol type not supported
>libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>2020-08-08 20:50:14.259651 E [2265508/2265508] CoreContext
>serverpool.cpp:427:listen? Failed listening on TCP [::]:6547 - Error 10:
>Protocol type not supported
>libva info: VA-API version 1.6.0
>libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>libva info: Found init function __vaDriverInit_1_6
>libva info: va_openDriver() returns 0
>libva info: VA-API version 1.6.0
>libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>libva info: Found init function __vaDriverInit_1_6
>libva info: va_openDriver() returns 0
>Cannot load libcuda.so.1
>2020-08-08 20:50:17.821604 A [2265508/2265508] CoreContext
>mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>interface error: The name is not activatable
>2020-08-08 20:50:17.822071 W [2265508/2265508] CoreContext
>mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>Media Monitor does not support this yet!
>
>Same output, very different startup time.? What's the difference?
>
>Dave D.

Do you have the Media Monitor looking for disks in the CD/DVD drive?
Is there a disk in the CD/DVD drive? The time when you are getting
the slowdown is about when mythfrontend will look for a disk to play,
if there is one. However, it will only do that if you have the Media
Monitor enabled. What does this SQL show?

select * from settings where value like '%monitord%';

I get this as I have it disabled on all frontends:

MariaDB [mythconverg]> select * from settings where value like
'%monitord%';
+---------------+------+----------+
| value | data | hostname |
+---------------+------+----------+
| MonitorDrives | 0 | mypvr |
| MonitorDrives | 0 | gt70 |
| MonitorDrives | 0 | lith |
| MonitorDrives | 0 | crw-pvr |
+---------------+------+----------+
4 rows in set (0.00 sec)

If mythfrontend has to wait while an optical disk is spun up and read,
that would explain the long delay. When mythfrontend is restarted, it
is likely that the data from the disk that it need to read is still
cached and that would explain the lack of delay.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
> On 9 Aug 2020, at 2:17 pm, Stephen Worthington <stephen_agent@jsw.gen.nz> wrote:
>
> On Sat, 8 Aug 2020 21:12:41 -0700, you wrote:
>
>> On 8/2/20 4:00 PM, jam@tigger.ws wrote:
>>> Over the last few releases mythtv has got slower to start and stop.
>>> What is the delay looking for ipv6 dtuff?
>>>
>>> This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>>>
>>> If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>>>
>>> James
>>>
>>> 00.730068 I Setup Interrupt: 2 handler
>>> 00.730091 I Setup Terminated: 15 handler
>>> 00.730098 I Setup Segmentation fault: 11 handler
>>> 00.730104 I Setup Abort trap: 6 handler
>>> 00.730109 I Setup Bus error: 10 handler
>>> 00.730115 I Setup Floating point exception: 8 handler
>>> 00.730123 I Setup Illegal instruction: 4 handler
>>> 00.730130 I Setup User defined signal 1: 30 handler
>>> 00.730137 I Setup User defined signal 2: 31 handler
>>> .....
>>
>> I finally caught a slow startup (my wife usually has it started by the
>> time I get to it) and here's the frontend output:
>>
>>> /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
>> libCECEnabled=0 -geometry 1920x1080+1920+0
>> qt.core.logging: Ignoring malformed logging rule: '’*.debug=false’'
>> "Display: Requesting EGL for 'Mesa Project, 1.4'"
>> 2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Interrupt handler
>> 2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Terminated handler
>> 2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Segmentation fault handler
>> 2020-08-08 20:44:32.526300 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Aborted handler
>> 2020-08-08 20:44:32.526311 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Bus error handler
>> 2020-08-08 20:44:32.526321 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Floating point exception
>> handler
>> 2020-08-08 20:44:32.526344 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Illegal instruction handler
>> 2020-08-08 20:44:32.526358 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Real-time signal 0 handler
>> 2020-08-08 20:44:32.526378 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup User defined signal 1
>> handler
>> 2020-08-08 20:44:32.526387 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup User defined signal 2
>> handler
>> 2020-08-08 20:44:32.526402 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate Setup Hangup handler
>> 2020-08-08 20:44:32.526587 C [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2602:ConfigureLogging mythfrontend version:
>> fixes/31 [v31.0-v31.0-47-gfc90482281] www.mythtv.org
>> 2020-08-08 20:44:32.526606 C [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2606:ConfigureLogging Qt version: compile:
>> 5.13.2, runtime: 5.13.2
>> 2020-08-08 20:44:32.526669 I [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2608:ConfigureLogging Fedora 31 (Workstation
>> Edition) (x86_64)
>> 2020-08-08 20:44:32.526674 N [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs:
>> general
>> 2020-08-08 20:44:32.863781 E [2264517/2264517] CoreContext
>> mythdb.cpp:181:DBError DB Error (StorageGroup::StorageGroup()):
>> Query was:
>>
>> Driver error was [1/]:
>> Driver not loaded
>> Database error was:
>> Driver not loaded
>>
>> 2020-08-08 20:44:32.969563 E [2264517/2264517] CoreContext
>> serverpool.cpp:550:bind Failed binding to UDP [::]:0 - Error 10:
>> Protocol type not supported
>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>> 2020-08-08 20:44:37.078916 E [2264517/2264517] CoreContext
>> serverpool.cpp:427:listen Failed listening on TCP [::]:6547 - Error 10:
>> Protocol type not supported
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> Cannot load libcuda.so.1
>>
>> The above lines come out very quickly, then the hard drive thrashes for
>> a long time before the next line comes up and the menu appears on the
>> screen. The difference between the timestamps (20:44:37 to 20:45:25) is
>> pretty much the time the hard drive is working (48 secs).
>>
>> 2020-08-08 20:45:25.153977 A [2264517/2264517] CoreContext
>> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>> interface error: The name is not activatable
>> 2020-08-08 20:45:25.155653 W [2264517/2264517] CoreContext
>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>> Media Monitor does not support this yet!
>> 2020-08-08 20:45:25.204403 W [2264517/2264517] CoreContext
>> mythplugin.cpp:110:MythPluginManager No libraries in plugins directory
>> /usr/lib64/mythtv/plugins
>>
>> All is normal after that. Should I increase the verbosity? Will it
>> tell me what's going on during all that hard drive activity? After this
>> startup, I exited and re-ran the frontend and it was ready to go in
>> about 6 seconds. Here's that output:
>>
>> 2020-08-08 20:50:11.231130 I [2265508/2265508] thread_unknown
>> mythcommandlineparser.cpp:2608:ConfigureLogging Fedora 31 (Workstation
>> Edition) (x86_64)
>> 2020-08-08 20:50:11.231131 N [2265508/2265508] thread_unknown
>> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs:
>> general
>> 2020-08-08 20:50:11.341611 E [2265508/2265508] CoreContext
>> mythdb.cpp:181:DBError DB Error (StorageGroup::StorageGroup()):
>> Query was:
>>
>> Driver error was [1/]:
>> Driver not loaded
>> Database error was:
>> Driver not loaded
>>
>> 2020-08-08 20:50:11.388052 E [2265508/2265508] CoreContext
>> serverpool.cpp:550:bind Failed binding to UDP [::]:0 - Error 10:
>> Protocol type not supported
>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>> 2020-08-08 20:50:14.259651 E [2265508/2265508] CoreContext
>> serverpool.cpp:427:listen Failed listening on TCP [::]:6547 - Error 10:
>> Protocol type not supported
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> Cannot load libcuda.so.1
>> 2020-08-08 20:50:17.821604 A [2265508/2265508] CoreContext
>> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>> interface error: The name is not activatable
>> 2020-08-08 20:50:17.822071 W [2265508/2265508] CoreContext
>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>> Media Monitor does not support this yet!
>>
>> Same output, very different startup time. What's the difference?
>>
>> Dave D.
>
> Do you have the Media Monitor looking for disks in the CD/DVD drive?
> Is there a disk in the CD/DVD drive? The time when you are getting
> the slowdown is about when mythfrontend will look for a disk to play,
> if there is one. However, it will only do that if you have the Media
> Monitor enabled. What does this SQL show?
>
> select * from settings where value like '%monitord%';
>
> I get this as I have it disabled on all frontends:
>
> MariaDB [mythconverg]> select * from settings where value like
> '%monitord%';
> +---------------+------+----------+
> | value | data | hostname |
> +---------------+------+----------+
> | MonitorDrives | 0 | mypvr |
> | MonitorDrives | 0 | gt70 |
> | MonitorDrives | 0 | lith |
> | MonitorDrives | 0 | crw-pvr |
> +---------------+------+----------+
> 4 rows in set (0.00 sec)
>
> If mythfrontend has to wait while an optical disk is spun up and read,
> that would explain the long delay. When mythfrontend is restarted, it
> is likely that the data from the disk that it need to read is still
> cached and that would explain the lack of delay.

What troubles me is that ALL the front ends are slow. There have been lots of sugestions but none seem to go anythere. eg

mysql> select * from settings where value like '%monitord%';
+---------------+------+--------------------------+
| value | data | hostname |
+---------------+------+--------------------------+
| MonitorDrives | 0 | sandypit |
| MonitorDrives | 0 | haycorn.local |
| MonitorDrives | 0 | twill |
| MonitorDrives | 0 | haycorn |
| MonitorDrives | 0 | haycorn.home |
| MonitorDrives | 0 | twill.home |
| MonitorDrives | 0 | jamess-macbook.local |
| MonitorDrives | 0 | dropbear |
| MonitorDrives | 0 | ws101.home |
| MonitorDrives | 0 | jamess-macbook-pro.local |
| MonitorDrives | 0 | piglet.home |
| MonitorDrives | 0 | twill.local |
| MonitorDrives | 0 | ws123.home |
| MonitorDrives | 0 | ws120.home |
| MonitorDrives | 0 | plasma.home |
| MonitorDrives | 0 | clydesdale |
| MonitorDrives | 0 | sanders |
| MonitorDrives | 0 | ws104.home |
| MonitorDrives | 0 | blackbeauty |
| MonitorDrives | 0 | mipad.home |
+---------------+------+--------------------------+

James

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 8/8/20 11:52 PM, jam@tigger.ws wrote:
>
>> On 9 Aug 2020, at 2:17 pm, Stephen Worthington <stephen_agent@jsw.gen.nz> wrote:
>>
>> On Sat, 8 Aug 2020 21:12:41 -0700, you wrote:
>>
>>> On 8/2/20 4:00 PM, jam@tigger.ws wrote:
>>>> Over the last few releases mythtv has got slower to start and stop.
>>>> What is the delay looking for ipv6 dtuff?
>>>>
>>>> This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>>>>
>>>> If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>>>>
>>>> James
>>>>
>>>> 00.730068 I Setup Interrupt: 2 handler
>>>> 00.730091 I Setup Terminated: 15 handler
>>>> 00.730098 I Setup Segmentation fault: 11 handler
>>>> 00.730104 I Setup Abort trap: 6 handler
>>>> 00.730109 I Setup Bus error: 10 handler
>>>> 00.730115 I Setup Floating point exception: 8 handler
>>>> 00.730123 I Setup Illegal instruction: 4 handler
>>>> 00.730130 I Setup User defined signal 1: 30 handler
>>>> 00.730137 I Setup User defined signal 2: 31 handler
>>>> .....
>>> I finally caught a slow startup (my wife usually has it started by the
>>> time I get to it) and here's the frontend output:
>>>
>>>> /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
>>> libCECEnabled=0 -geometry 1920x1080+1920+0
>>> qt.core.logging: Ignoring malformed logging rule: '’*.debug=false’'
>>> "Display: Requesting EGL for 'Mesa Project, 1.4'"
>>> 2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Interrupt handler
>>> 2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Terminated handler
>>> 2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Segmentation fault handler
>>> 2020-08-08 20:44:32.526300 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Aborted handler
>>> 2020-08-08 20:44:32.526311 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Bus error handler
>>> 2020-08-08 20:44:32.526321 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Floating point exception
>>> handler
>>> 2020-08-08 20:44:32.526344 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Illegal instruction handler
>>> 2020-08-08 20:44:32.526358 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Real-time signal 0 handler
>>> 2020-08-08 20:44:32.526378 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup User defined signal 1
>>> handler
>>> 2020-08-08 20:44:32.526387 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup User defined signal 2
>>> handler
>>> 2020-08-08 20:44:32.526402 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Hangup handler
>>> 2020-08-08 20:44:32.526587 C [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2602:ConfigureLogging mythfrontend version:
>>> fixes/31 [v31.0-v31.0-47-gfc90482281] www.mythtv.org
>>> 2020-08-08 20:44:32.526606 C [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2606:ConfigureLogging Qt version: compile:
>>> 5.13.2, runtime: 5.13.2
>>> 2020-08-08 20:44:32.526669 I [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2608:ConfigureLogging Fedora 31 (Workstation
>>> Edition) (x86_64)
>>> 2020-08-08 20:44:32.526674 N [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs:
>>> general
>>> 2020-08-08 20:44:32.863781 E [2264517/2264517] CoreContext
>>> mythdb.cpp:181:DBError DB Error (StorageGroup::StorageGroup()):
>>> Query was:
>>>
>>> Driver error was [1/]:
>>> Driver not loaded
>>> Database error was:
>>> Driver not loaded
>>>
>>> 2020-08-08 20:44:32.969563 E [2264517/2264517] CoreContext
>>> serverpool.cpp:550:bind Failed binding to UDP [::]:0 - Error 10:
>>> Protocol type not supported
>>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>>> 2020-08-08 20:44:37.078916 E [2264517/2264517] CoreContext
>>> serverpool.cpp:427:listen Failed listening on TCP [::]:6547 - Error 10:
>>> Protocol type not supported
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> Cannot load libcuda.so.1
>>>
>>> The above lines come out very quickly, then the hard drive thrashes for
>>> a long time before the next line comes up and the menu appears on the
>>> screen. The difference between the timestamps (20:44:37 to 20:45:25) is
>>> pretty much the time the hard drive is working (48 secs).
>>>
>>> 2020-08-08 20:45:25.153977 A [2264517/2264517] CoreContext
>>> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>>> interface error: The name is not activatable
>>> 2020-08-08 20:45:25.155653 W [2264517/2264517] CoreContext
>>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>>> Media Monitor does not support this yet!
>>> 2020-08-08 20:45:25.204403 W [2264517/2264517] CoreContext
>>> mythplugin.cpp:110:MythPluginManager No libraries in plugins directory
>>> /usr/lib64/mythtv/plugins
>>>
>>> All is normal after that. Should I increase the verbosity? Will it
>>> tell me what's going on during all that hard drive activity? After this
>>> startup, I exited and re-ran the frontend and it was ready to go in
>>> about 6 seconds. Here's that output:
>>>
>>> 2020-08-08 20:50:11.231130 I [2265508/2265508] thread_unknown
>>> mythcommandlineparser.cpp:2608:ConfigureLogging Fedora 31 (Workstation
>>> Edition) (x86_64)
>>> 2020-08-08 20:50:11.231131 N [2265508/2265508] thread_unknown
>>> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs:
>>> general
>>> 2020-08-08 20:50:11.341611 E [2265508/2265508] CoreContext
>>> mythdb.cpp:181:DBError DB Error (StorageGroup::StorageGroup()):
>>> Query was:
>>>
>>> Driver error was [1/]:
>>> Driver not loaded
>>> Database error was:
>>> Driver not loaded
>>>
>>> 2020-08-08 20:50:11.388052 E [2265508/2265508] CoreContext
>>> serverpool.cpp:550:bind Failed binding to UDP [::]:0 - Error 10:
>>> Protocol type not supported
>>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>>> 2020-08-08 20:50:14.259651 E [2265508/2265508] CoreContext
>>> serverpool.cpp:427:listen Failed listening on TCP [::]:6547 - Error 10:
>>> Protocol type not supported
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> Cannot load libcuda.so.1
>>> 2020-08-08 20:50:17.821604 A [2265508/2265508] CoreContext
>>> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>>> interface error: The name is not activatable
>>> 2020-08-08 20:50:17.822071 W [2265508/2265508] CoreContext
>>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>>> Media Monitor does not support this yet!
>>>
>>> Same output, very different startup time. What's the difference?
>>>
>>> Dave D.
>> Do you have the Media Monitor looking for disks in the CD/DVD drive?
>> Is there a disk in the CD/DVD drive? The time when you are getting
>> the slowdown is about when mythfrontend will look for a disk to play,
>> if there is one. However, it will only do that if you have the Media
>> Monitor enabled. What does this SQL show?
>>
>> select * from settings where value like '%monitord%';
>>
>> I get this as I have it disabled on all frontends:
>>
>> MariaDB [mythconverg]> select * from settings where value like
>> '%monitord%';
>> +---------------+------+----------+
>> | value | data | hostname |
>> +---------------+------+----------+
>> | MonitorDrives | 0 | mypvr |
>> | MonitorDrives | 0 | gt70 |
>> | MonitorDrives | 0 | lith |
>> | MonitorDrives | 0 | crw-pvr |
>> +---------------+------+----------+
>> 4 rows in set (0.00 sec)
>>
>> If mythfrontend has to wait while an optical disk is spun up and read,
>> that would explain the long delay. When mythfrontend is restarted, it
>> is likely that the data from the disk that it need to read is still
>> cached and that would explain the lack of delay.
> What troubles me is that ALL the front ends are slow. There have been lots of sugestions but none seem to go anythere. eg
>
> mysql> select * from settings where value like '%monitord%';
> +---------------+------+--------------------------+
> | value | data | hostname |
> +---------------+------+--------------------------+
> | MonitorDrives | 0 | sandypit |
> | MonitorDrives | 0 | haycorn.local |
> | MonitorDrives | 0 | twill |
> | MonitorDrives | 0 | haycorn |
> | MonitorDrives | 0 | haycorn.home |
> | MonitorDrives | 0 | twill.home |
> | MonitorDrives | 0 | jamess-macbook.local |
> | MonitorDrives | 0 | dropbear |
> | MonitorDrives | 0 | ws101.home |
> | MonitorDrives | 0 | jamess-macbook-pro.local |
> | MonitorDrives | 0 | piglet.home |
> | MonitorDrives | 0 | twill.local |
> | MonitorDrives | 0 | ws123.home |
> | MonitorDrives | 0 | ws120.home |
> | MonitorDrives | 0 | plasma.home |
> | MonitorDrives | 0 | clydesdale |
> | MonitorDrives | 0 | sanders |
> | MonitorDrives | 0 | ws104.home |
> | MonitorDrives | 0 | blackbeauty |
> | MonitorDrives | 0 | mipad.home |
> +---------------+------+--------------------------+
>
> James

Mine, too, are all zero.  I rarely use my other frontends and expect
them to be slow, anyway, since they are low power machines.  My main
frontend in the living room is a hot, (relatively) new I7 with modern,
fast (although not SSD fast) hard drives.  Also, the spin-up wait
wouldn't account for the difference in startup times.  The hard drive is
working constantly during that 48 seconds of no output (light doesn't
even flicker once).  This machine is also my master backend so next time
I'll watch the BACKEND log to see if it gives a clue.

Dave D.


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
This must be ‘problem between keyboard and seat’ Don’t know how I sent an old posting to you! Sorry!
James

> On 9 Aug 2020, at 2:52 pm, jam@tigger.ws wrote:
>
>
>
>> On 9 Aug 2020, at 2:17 pm, Stephen Worthington <stephen_agent@jsw.gen.nz> wrote:
>>
>> On Sat, 8 Aug 2020 21:12:41 -0700, you wrote:
>>
>>> On 8/2/20 4:00 PM, jam@tigger.ws wrote:
>>>> Over the last few releases mythtv has got slower to start and stop.
>>>> What is the delay looking for ipv6 dtuff?
>>>>
>>>> This trace is from my mac frontrnd, my linux frontend start is similar, the stop takes 3 sec.
>>>>
>>>> If the issue is not my config should we not gently think about start and stop times from a dev point of view?
>>>>
>>>> James
>>>>
>>>> 00.730068 I Setup Interrupt: 2 handler
>>>> 00.730091 I Setup Terminated: 15 handler
>>>> 00.730098 I Setup Segmentation fault: 11 handler
>>>> 00.730104 I Setup Abort trap: 6 handler
>>>> 00.730109 I Setup Bus error: 10 handler
>>>> 00.730115 I Setup Floating point exception: 8 handler
>>>> 00.730123 I Setup Illegal instruction: 4 handler
>>>> 00.730130 I Setup User defined signal 1: 30 handler
>>>> 00.730137 I Setup User defined signal 2: 31 handler
>>>> .....
>>>
>>> I finally caught a slow startup (my wife usually has it started by the
>>> time I get to it) and here's the frontend output:
>>>
>>>> /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
>>> libCECEnabled=0 -geometry 1920x1080+1920+0
>>> qt.core.logging: Ignoring malformed logging rule: '’*.debug=false’'
>>> "Display: Requesting EGL for 'Mesa Project, 1.4'"
>>> 2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Interrupt handler
>>> 2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Terminated handler
>>> 2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Segmentation fault handler
>>> 2020-08-08 20:44:32.526300 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Aborted handler
>>> 2020-08-08 20:44:32.526311 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Bus error handler
>>> 2020-08-08 20:44:32.526321 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Floating point exception
>>> handler
>>> 2020-08-08 20:44:32.526344 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Illegal instruction handler
>>> 2020-08-08 20:44:32.526358 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Real-time signal 0 handler
>>> 2020-08-08 20:44:32.526378 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup User defined signal 1
>>> handler
>>> 2020-08-08 20:44:32.526387 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup User defined signal 2
>>> handler
>>> 2020-08-08 20:44:32.526402 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate Setup Hangup handler
>>> 2020-08-08 20:44:32.526587 C [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2602:ConfigureLogging mythfrontend version:
>>> fixes/31 [v31.0-v31.0-47-gfc90482281] www.mythtv.org
>>> 2020-08-08 20:44:32.526606 C [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2606:ConfigureLogging Qt version: compile:
>>> 5.13.2, runtime: 5.13.2
>>> 2020-08-08 20:44:32.526669 I [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2608:ConfigureLogging Fedora 31 (Workstation
>>> Edition) (x86_64)
>>> 2020-08-08 20:44:32.526674 N [2264517/2264517] thread_unknown
>>> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs:
>>> general
>>> 2020-08-08 20:44:32.863781 E [2264517/2264517] CoreContext
>>> mythdb.cpp:181:DBError DB Error (StorageGroup::StorageGroup()):
>>> Query was:
>>>
>>> Driver error was [1/]:
>>> Driver not loaded
>>> Database error was:
>>> Driver not loaded
>>>
>>> 2020-08-08 20:44:32.969563 E [2264517/2264517] CoreContext
>>> serverpool.cpp:550:bind Failed binding to UDP [::]:0 - Error 10:
>>> Protocol type not supported
>>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>>> 2020-08-08 20:44:37.078916 E [2264517/2264517] CoreContext
>>> serverpool.cpp:427:listen Failed listening on TCP [::]:6547 - Error 10:
>>> Protocol type not supported
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> Cannot load libcuda.so.1
>>>
>>> The above lines come out very quickly, then the hard drive thrashes for
>>> a long time before the next line comes up and the menu appears on the
>>> screen. The difference between the timestamps (20:44:37 to 20:45:25) is
>>> pretty much the time the hard drive is working (48 secs).
>>>
>>> 2020-08-08 20:45:25.153977 A [2264517/2264517] CoreContext
>>> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>>> interface error: The name is not activatable
>>> 2020-08-08 20:45:25.155653 W [2264517/2264517] CoreContext
>>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>>> Media Monitor does not support this yet!
>>> 2020-08-08 20:45:25.204403 W [2264517/2264517] CoreContext
>>> mythplugin.cpp:110:MythPluginManager No libraries in plugins directory
>>> /usr/lib64/mythtv/plugins
>>>
>>> All is normal after that. Should I increase the verbosity? Will it
>>> tell me what's going on during all that hard drive activity? After this
>>> startup, I exited and re-ran the frontend and it was ready to go in
>>> about 6 seconds. Here's that output:
>>>
>>> 2020-08-08 20:50:11.231130 I [2265508/2265508] thread_unknown
>>> mythcommandlineparser.cpp:2608:ConfigureLogging Fedora 31 (Workstation
>>> Edition) (x86_64)
>>> 2020-08-08 20:50:11.231131 N [2265508/2265508] thread_unknown
>>> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs:
>>> general
>>> 2020-08-08 20:50:11.341611 E [2265508/2265508] CoreContext
>>> mythdb.cpp:181:DBError DB Error (StorageGroup::StorageGroup()):
>>> Query was:
>>>
>>> Driver error was [1/]:
>>> Driver not loaded
>>> Database error was:
>>> Driver not loaded
>>>
>>> 2020-08-08 20:50:11.388052 E [2265508/2265508] CoreContext
>>> serverpool.cpp:550:bind Failed binding to UDP [::]:0 - Error 10:
>>> Protocol type not supported
>>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>>> 2020-08-08 20:50:14.259651 E [2265508/2265508] CoreContext
>>> serverpool.cpp:427:listen Failed listening on TCP [::]:6547 - Error 10:
>>> Protocol type not supported
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> libva info: VA-API version 1.6.0
>>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>>> libva info: Found init function __vaDriverInit_1_6
>>> libva info: va_openDriver() returns 0
>>> Cannot load libcuda.so.1
>>> 2020-08-08 20:50:17.821604 A [2265508/2265508] CoreContext
>>> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>>> interface error: The name is not activatable
>>> 2020-08-08 20:50:17.822071 W [2265508/2265508] CoreContext
>>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>>> Media Monitor does not support this yet!
>>>
>>> Same output, very different startup time. What's the difference?
>>>
>>> Dave D.
>>
>> Do you have the Media Monitor looking for disks in the CD/DVD drive?
>> Is there a disk in the CD/DVD drive? The time when you are getting
>> the slowdown is about when mythfrontend will look for a disk to play,
>> if there is one. However, it will only do that if you have the Media
>> Monitor enabled. What does this SQL show?
>>
>> select * from settings where value like '%monitord%';
>>
>> I get this as I have it disabled on all frontends:
>>
>> MariaDB [mythconverg]> select * from settings where value like
>> '%monitord%';
>> +---------------+------+----------+
>> | value | data | hostname |
>> +---------------+------+----------+
>> | MonitorDrives | 0 | mypvr |
>> | MonitorDrives | 0 | gt70 |
>> | MonitorDrives | 0 | lith |
>> | MonitorDrives | 0 | crw-pvr |
>> +---------------+------+----------+
>> 4 rows in set (0.00 sec)
>>
>> If mythfrontend has to wait while an optical disk is spun up and read,
>> that would explain the long delay. When mythfrontend is restarted, it
>> is likely that the data from the disk that it need to read is still
>> cached and that would explain the lack of delay.
>
> What troubles me is that ALL the front ends are slow. There have been lots of sugestions but none seem to go anythere. eg
>
> mysql> select * from settings where value like '%monitord%';
> +---------------+------+--------------------------+
> | value | data | hostname |
> +---------------+------+--------------------------+
> | MonitorDrives | 0 | sandypit |
> | MonitorDrives | 0 | haycorn.local |
> | MonitorDrives | 0 | twill |
> | MonitorDrives | 0 | haycorn |
> | MonitorDrives | 0 | haycorn.home |
> | MonitorDrives | 0 | twill.home |
> | MonitorDrives | 0 | jamess-macbook.local |
> | MonitorDrives | 0 | dropbear |
> | MonitorDrives | 0 | ws101.home |
> | MonitorDrives | 0 | jamess-macbook-pro.local |
> | MonitorDrives | 0 | piglet.home |
> | MonitorDrives | 0 | twill.local |
> | MonitorDrives | 0 | ws123.home |
> | MonitorDrives | 0 | ws120.home |
> | MonitorDrives | 0 | plasma.home |
> | MonitorDrives | 0 | clydesdale |
> | MonitorDrives | 0 | sanders |
> | MonitorDrives | 0 | ws104.home |
> | MonitorDrives | 0 | blackbeauty |
> | MonitorDrives | 0 | mipad.home |
> +---------------+------+--------------------------+
>
> James
>

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 09/08/2020 05:12, DaveD wrote:
> On 8/2/20 4:00 PM, jam@tigger.ws wrote:
>> Over the last few releases mythtv has got slower to start and stop.
>> What is the delay looking for ipv6 dtuff?
>>
>> This trace is from my mac frontrnd, my linux frontend start is
>> similar, the stop takes 3 sec.
>>
>> If the issue is not my config should we not gently think about start
>> and stop times from a dev point of view?
>>
>> James
>>
>> 00.730068 I  Setup Interrupt: 2 handler
>> 00.730091 I  Setup Terminated: 15 handler
>> 00.730098 I  Setup Segmentation fault: 11 handler
>> 00.730104 I  Setup Abort trap: 6 handler
>> 00.730109 I  Setup Bus error: 10 handler
>> 00.730115 I  Setup Floating point exception: 8 handler
>> 00.730123 I  Setup Illegal instruction: 4 handler
>> 00.730130 I  Setup User defined signal 1: 30 handler
>> 00.730137 I  Setup User defined signal 2: 31 handler
>> .....
>
> I finally caught a slow startup (my wife usually has it started by the
> time I get to it) and here's the frontend output:
>
>> /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
> libCECEnabled=0 -geometry 1920x1080+1920+0
> qt.core.logging: Ignoring malformed logging rule: '’*.debug=false’'
> "Display: Requesting EGL for 'Mesa Project, 1.4'"
> 2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Interrupt handler
> 2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Terminated handler
> 2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Segmentation fault handler
> 2020-08-08 20:44:32.526300 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Aborted handler
> 2020-08-08 20:44:32.526311 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Bus error handler
> 2020-08-08 20:44:32.526321 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Floating point exception
> handler
> 2020-08-08 20:44:32.526344 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Illegal instruction handler
> 2020-08-08 20:44:32.526358 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Real-time signal 0 handler
> 2020-08-08 20:44:32.526378 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup User defined signal 1
> handler
> 2020-08-08 20:44:32.526387 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup User defined signal 2
> handler
> 2020-08-08 20:44:32.526402 I [2264517/2264517] thread_unknown
> signalhandling.cpp:191:SetHandlerPrivate  Setup Hangup handler
> 2020-08-08 20:44:32.526587 C [2264517/2264517] thread_unknown
> mythcommandlineparser.cpp:2602:ConfigureLogging  mythfrontend version:
> fixes/31 [v31.0-v31.0-47-gfc90482281] www.mythtv.org
> 2020-08-08 20:44:32.526606 C [2264517/2264517] thread_unknown
> mythcommandlineparser.cpp:2606:ConfigureLogging  Qt version: compile:
> 5.13.2, runtime: 5.13.2
> 2020-08-08 20:44:32.526669 I [2264517/2264517] thread_unknown
> mythcommandlineparser.cpp:2608:ConfigureLogging  Fedora 31 (Workstation
> Edition) (x86_64)
> 2020-08-08 20:44:32.526674 N [2264517/2264517] thread_unknown
> mythcommandlineparser.cpp:2610:ConfigureLogging  Enabled verbose msgs: 
> general
> 2020-08-08 20:44:32.863781 E [2264517/2264517] CoreContext
> mythdb.cpp:181:DBError  DB Error (StorageGroup::StorageGroup()):
> Query was:
>
> Driver error was [1/]:
> Driver not loaded
> Database error was:
> Driver not loaded
>
> 2020-08-08 20:44:32.969563 E [2264517/2264517] CoreContext
> serverpool.cpp:550:bind  Failed binding to UDP [::]:0 - Error 10:
> Protocol type not supported
> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
> 2020-08-08 20:44:37.078916 E [2264517/2264517] CoreContext
> serverpool.cpp:427:listen  Failed listening on TCP [::]:6547 - Error 10:
> Protocol type not supported
> libva info: VA-API version 1.6.0
> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
> libva info: Found init function __vaDriverInit_1_6
> libva info: va_openDriver() returns 0
> libva info: VA-API version 1.6.0
> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
> libva info: Found init function __vaDriverInit_1_6
> libva info: va_openDriver() returns 0
> Cannot load libcuda.so.1
>
> The above lines come out very quickly, then the hard drive thrashes for
> a long time before the next line comes up and the menu appears on the
> screen.  The difference between the timestamps (20:44:37 to 20:45:25) is
> pretty much the time the hard drive is working (48 secs).
>
> 2020-08-08 20:45:25.153977 A [2264517/2264517] CoreContext
> mediamonitor-unix.cpp:204:CheckMountable  MMUnix:CheckMountable: DBus
> interface error: The name is not activatable
> 2020-08-08 20:45:25.155653 W [2264517/2264517] CoreContext
> mediamonitor-unix.cpp:212:CheckMountable  MMUnix:UDisks2 service found.
> Media Monitor does not support this yet!
> 2020-08-08 20:45:25.204403 W [2264517/2264517] CoreContext
> mythplugin.cpp:110:MythPluginManager  No libraries in plugins directory
> /usr/lib64/mythtv/plugins
>
> All is normal after that.  Should I increase the verbosity?  Will it
> tell me what's going on during all that hard drive activity? After this
> startup, I exited and re-ran the frontend and it was ready to go in
> about 6 seconds.  Here's that output:
>
> 2020-08-08 20:50:11.231130 I [2265508/2265508] thread_unknown
> mythcommandlineparser.cpp:2608:ConfigureLogging  Fedora 31 (Workstation
> Edition) (x86_64)
> 2020-08-08 20:50:11.231131 N [2265508/2265508] thread_unknown
> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs: 
> general
> 2020-08-08 20:50:11.341611 E [2265508/2265508] CoreContext
> mythdb.cpp:181:DBError  DB Error (StorageGroup::StorageGroup()):
> Query was:
>
> Driver error was [1/]:
> Driver not loaded
> Database error was:
> Driver not loaded
>
> 2020-08-08 20:50:11.388052 E [2265508/2265508] CoreContext
> serverpool.cpp:550:bind  Failed binding to UDP [::]:0 - Error 10:
> Protocol type not supported
> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
> 2020-08-08 20:50:14.259651 E [2265508/2265508] CoreContext
> serverpool.cpp:427:listen  Failed listening on TCP [::]:6547 - Error 10:
> Protocol type not supported
> libva info: VA-API version 1.6.0
> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
> libva info: Found init function __vaDriverInit_1_6
> libva info: va_openDriver() returns 0
> libva info: VA-API version 1.6.0
> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
> libva info: Found init function __vaDriverInit_1_6
> libva info: va_openDriver() returns 0
> Cannot load libcuda.so.1
> 2020-08-08 20:50:17.821604 A [2265508/2265508] CoreContext
> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
> interface error: The name is not activatable
> 2020-08-08 20:50:17.822071 W [2265508/2265508] CoreContext
> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
> Media Monitor does not support this yet!
>
> Same output, very different startup time.  What's the difference?
>

Right, I know what is going on here.

The first time it starts up, it's trying to connect via DBus to the
service "org.freedesktop.UDisks" which fails to activate.

"CheckMountable MMUnix:CheckMountable: DBus interface error: The name is
not activatable" <-- That's the error. Code is here [1]

The second time through, DBus knows the service can't be activated
(or caches the result of the first time), and returns quickly with
the activation failure.

Regarding these DBus endpoints. UDisks is so old, it's deprecation
notice now has mold on it. UDisks2 is newer, but nobody has been
sufficiently interested to write support for it.

Anyway, I suspect that your system(s) still advertise UDisks via
DBus and it is trying this that takes the time. Please send the
output of the following command

$ dbus-send --system --print-reply --dest=org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep
org.freedesktop.UDisks

Regards
Stuart

[1] -
https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmyth/mediamonitor-unix.cpp#L193

> Dave D.
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 18/08/2020 22:09, Stuart Auchterlonie wrote:
> On 09/08/2020 05:12, DaveD wrote:
>> On 8/2/20 4:00 PM, jam@tigger.ws wrote:
>>> Over the last few releases mythtv has got slower to start and stop.
>>> What is the delay looking for ipv6 dtuff?
>>>
>>> This trace is from my mac frontrnd, my linux frontend start is
>>> similar, the stop takes 3 sec.
>>>
>>> If the issue is not my config should we not gently think about start
>>> and stop times from a dev point of view?
>>>
>>> James
>>>
>>> 00.730068 I  Setup Interrupt: 2 handler
>>> 00.730091 I  Setup Terminated: 15 handler
>>> 00.730098 I  Setup Segmentation fault: 11 handler
>>> 00.730104 I  Setup Abort trap: 6 handler
>>> 00.730109 I  Setup Bus error: 10 handler
>>> 00.730115 I  Setup Floating point exception: 8 handler
>>> 00.730123 I  Setup Illegal instruction: 4 handler
>>> 00.730130 I  Setup User defined signal 1: 30 handler
>>> 00.730137 I  Setup User defined signal 2: 31 handler
>>> .....
>>
>> I finally caught a slow startup (my wife usually has it started by the
>> time I get to it) and here's the frontend output:
>>
>>> /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
>> libCECEnabled=0 -geometry 1920x1080+1920+0
>> qt.core.logging: Ignoring malformed logging rule: '’*.debug=false’'
>> "Display: Requesting EGL for 'Mesa Project, 1.4'"
>> 2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Interrupt handler
>> 2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Terminated handler
>> 2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Segmentation fault handler
>> 2020-08-08 20:44:32.526300 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Aborted handler
>> 2020-08-08 20:44:32.526311 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Bus error handler
>> 2020-08-08 20:44:32.526321 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Floating point exception
>> handler
>> 2020-08-08 20:44:32.526344 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Illegal instruction handler
>> 2020-08-08 20:44:32.526358 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Real-time signal 0 handler
>> 2020-08-08 20:44:32.526378 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup User defined signal 1
>> handler
>> 2020-08-08 20:44:32.526387 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup User defined signal 2
>> handler
>> 2020-08-08 20:44:32.526402 I [2264517/2264517] thread_unknown
>> signalhandling.cpp:191:SetHandlerPrivate  Setup Hangup handler
>> 2020-08-08 20:44:32.526587 C [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2602:ConfigureLogging  mythfrontend version:
>> fixes/31 [v31.0-v31.0-47-gfc90482281] www.mythtv.org
>> 2020-08-08 20:44:32.526606 C [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2606:ConfigureLogging  Qt version: compile:
>> 5.13.2, runtime: 5.13.2
>> 2020-08-08 20:44:32.526669 I [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2608:ConfigureLogging  Fedora 31 (Workstation
>> Edition) (x86_64)
>> 2020-08-08 20:44:32.526674 N [2264517/2264517] thread_unknown
>> mythcommandlineparser.cpp:2610:ConfigureLogging  Enabled verbose msgs: 
>> general
>> 2020-08-08 20:44:32.863781 E [2264517/2264517] CoreContext
>> mythdb.cpp:181:DBError  DB Error (StorageGroup::StorageGroup()):
>> Query was:
>>
>> Driver error was [1/]:
>> Driver not loaded
>> Database error was:
>> Driver not loaded
>>
>> 2020-08-08 20:44:32.969563 E [2264517/2264517] CoreContext
>> serverpool.cpp:550:bind  Failed binding to UDP [::]:0 - Error 10:
>> Protocol type not supported
>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>> 2020-08-08 20:44:37.078916 E [2264517/2264517] CoreContext
>> serverpool.cpp:427:listen  Failed listening on TCP [::]:6547 - Error 10:
>> Protocol type not supported
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> Cannot load libcuda.so.1
>>
>> The above lines come out very quickly, then the hard drive thrashes for
>> a long time before the next line comes up and the menu appears on the
>> screen.  The difference between the timestamps (20:44:37 to 20:45:25) is
>> pretty much the time the hard drive is working (48 secs).
>>
>> 2020-08-08 20:45:25.153977 A [2264517/2264517] CoreContext
>> mediamonitor-unix.cpp:204:CheckMountable  MMUnix:CheckMountable: DBus
>> interface error: The name is not activatable
>> 2020-08-08 20:45:25.155653 W [2264517/2264517] CoreContext
>> mediamonitor-unix.cpp:212:CheckMountable  MMUnix:UDisks2 service found.
>> Media Monitor does not support this yet!
>> 2020-08-08 20:45:25.204403 W [2264517/2264517] CoreContext
>> mythplugin.cpp:110:MythPluginManager  No libraries in plugins directory
>> /usr/lib64/mythtv/plugins
>>
>> All is normal after that.  Should I increase the verbosity?  Will it
>> tell me what's going on during all that hard drive activity? After this
>> startup, I exited and re-ran the frontend and it was ready to go in
>> about 6 seconds.  Here's that output:
>>
>> 2020-08-08 20:50:11.231130 I [2265508/2265508] thread_unknown
>> mythcommandlineparser.cpp:2608:ConfigureLogging  Fedora 31 (Workstation
>> Edition) (x86_64)
>> 2020-08-08 20:50:11.231131 N [2265508/2265508] thread_unknown
>> mythcommandlineparser.cpp:2610:ConfigureLogging Enabled verbose msgs: 
>> general
>> 2020-08-08 20:50:11.341611 E [2265508/2265508] CoreContext
>> mythdb.cpp:181:DBError  DB Error (StorageGroup::StorageGroup()):
>> Query was:
>>
>> Driver error was [1/]:
>> Driver not loaded
>> Database error was:
>> Driver not loaded
>>
>> 2020-08-08 20:50:11.388052 E [2265508/2265508] CoreContext
>> serverpool.cpp:550:bind  Failed binding to UDP [::]:0 - Error 10:
>> Protocol type not supported
>> libEGL warning: FIXME: egl/x11 doesn't support front buffer rendering.
>> 2020-08-08 20:50:14.259651 E [2265508/2265508] CoreContext
>> serverpool.cpp:427:listen  Failed listening on TCP [::]:6547 - Error 10:
>> Protocol type not supported
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> libva info: VA-API version 1.6.0
>> libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_1_6
>> libva info: va_openDriver() returns 0
>> Cannot load libcuda.so.1
>> 2020-08-08 20:50:17.821604 A [2265508/2265508] CoreContext
>> mediamonitor-unix.cpp:204:CheckMountable MMUnix:CheckMountable: DBus
>> interface error: The name is not activatable
>> 2020-08-08 20:50:17.822071 W [2265508/2265508] CoreContext
>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>> Media Monitor does not support this yet!
>>
>> Same output, very different startup time.  What's the difference?
>>
>
> Right, I know what is going on here.
>
> The first time it starts up, it's trying to connect via DBus to the
> service "org.freedesktop.UDisks" which fails to activate.
>
> "CheckMountable MMUnix:CheckMountable: DBus interface error: The name is
> not activatable" <-- That's the error. Code is here [1]
>
> The second time through, DBus knows the service can't be activated
> (or caches the result of the first time), and returns quickly with
> the activation failure.
>
> Regarding these DBus endpoints. UDisks is so old, it's deprecation
> notice now has mold on it. UDisks2 is newer, but nobody has been
> sufficiently interested to write support for it.
>
> Anyway, I suspect that your system(s) still advertise UDisks via
> DBus and it is trying this that takes the time. Please send the
> output of the following command
>
> $ dbus-send --system --print-reply --dest=org.freedesktop.DBus
> /org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep
> org.freedesktop.UDisks
>
> Regards
> Stuart
>
> [1] -
> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmyth/mediamonitor-unix.cpp#L193
>

Acutally, looking at
https://code.mythtv.org/trac/ticket/12307#comment:11

we weren't checking to see if the user had disabled
the media monitor early enough, so it was still calling
out to dbus.

I've committed a fix to respect the user setting thereby
bypassing this check at startup, and backported it to
fixes/31. This should be in updated packages in the next
24hrs or so.


Regards
Stuart

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 8/18/20 3:01 PM, Stuart Auchterlonie wrote:
> On 18/08/2020 22:09, Stuart Auchterlonie wrote:
>> On 09/08/2020 05:12, DaveD wrote:
>>> On 8/2/20 4:00 PM, jam@tigger.ws wrote:
>>>> Over the last few releases mythtv has got slower to start and stop.
>>>> What is the delay looking for ipv6 dtuff?
>>>>
>>>> This trace is from my mac frontrnd, my linux frontend start is
>>>> similar, the stop takes 3 sec.
>>>>
>>>> If the issue is not my config should we not gently think about start
>>>> and stop times from a dev point of view?
>>>>
>>>> James
>>>>
>>>> 00.730068 I  Setup Interrupt: 2 handler
>>>> 00.730091 I  Setup Terminated: 15 handler
>>>> 00.730098 I  Setup Segmentation fault: 11 handler
>>>> 00.730104 I  Setup Abort trap: 6 handler
>>>> 00.730109 I  Setup Bus error: 10 handler
>>>> 00.730115 I  Setup Floating point exception: 8 handler
>>>> 00.730123 I  Setup Illegal instruction: 4 handler
>>>> 00.730130 I  Setup User defined signal 1: 30 handler
>>>> 00.730137 I  Setup User defined signal 2: 31 handler
>>>> .....
>>> I finally caught a slow startup (my wife usually has it started by the
>>> time I get to it) and here's the frontend output:
>>>
>>>> /usr/bin/mythfrontend --loglevel warning -O PowerOffTVOnExit=0 -O
>>> libCECEnabled=0 -geometry 1920x1080+1920+0
>>> qt.core.logging: Ignoring malformed logging rule: '’*.debug=false’'
>>> "Display: Requesting EGL for 'Mesa Project, 1.4'"
>>> 2020-08-08 20:44:32.526210 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate  Setup Interrupt handler
>>> 2020-08-08 20:44:32.526259 I [2264517/2264517] thread_unknown
>>> signalhandling.cpp:191:SetHandlerPrivate  Setup Terminated handler
>>> 2020-08-08 20:44:32.526288 I [2264517/2264517] thread_unknown
>>> ..... snip .....
>>> mediamonitor-unix.cpp:212:CheckMountable MMUnix:UDisks2 service found.
>>> Media Monitor does not support this yet!
>>>
>>> Same output, very different startup time.  What's the difference?
>>>
>> Right, I know what is going on here.
>>
>> The first time it starts up, it's trying to connect via DBus to the
>> service "org.freedesktop.UDisks" which fails to activate.
>>
>> "CheckMountable MMUnix:CheckMountable: DBus interface error: The name is
>> not activatable" <-- That's the error. Code is here [1]
>>
>> The second time through, DBus knows the service can't be activated
>> (or caches the result of the first time), and returns quickly with
>> the activation failure.
>>
>> Regarding these DBus endpoints. UDisks is so old, it's deprecation
>> notice now has mold on it. UDisks2 is newer, but nobody has been
>> sufficiently interested to write support for it.
>>
>> Anyway, I suspect that your system(s) still advertise UDisks via
>> DBus and it is trying this that takes the time. Please send the
>> output of the following command
>>
>> $ dbus-send --system --print-reply --dest=org.freedesktop.DBus
>> /org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep
>> org.freedesktop.UDisks
>>
>> Regards
>> Stuart
>>
>> [1] -
>> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmyth/mediamonitor-unix.cpp#L193
> Acutally, looking at
> https://code.mythtv.org/trac/ticket/12307#comment:11
>
> we weren't checking to see if the user had disabled
> the media monitor early enough, so it was still calling
> out to dbus.
>
> I've committed a fix to respect the user setting thereby
> bypassing this check at startup, and backported it to
> fixes/31. This should be in updated packages in the next
> 24hrs or so.
>
>
> Regards
> Stuart

This is very encouraging.  I hope you have it figured out.  That said, I
don't know enough about dbus to fit your model into my experience.

I use a firewire to a cable box and that firewire interface is extremely
fragile.  If the cable box gets turned off (remote in wrong mode!), I
have to reboot to get mythbackend to get it's connection back where it
can change channels again.  Some times I can pull and re-plug the
firewire cable and restart mythbackend, sometimes I just need to restart
mythbackend, sometimes I can unload the firewire module and re-modprobe
it, etc, etc.  But I digress.

A week or so ago, I had to both turn off the power to my computer and
unplug the cable box then fire it back up to re-establish the
connection.  After that, mythfrontend started up every day with no
delay; < 10 seconds from hitting the key on the remote to recordings
list.  Every time.  Until it didn't.  No idea what changed to make it
sluggish again, but it takes > 50 seconds, now.

What you said about dbus timing out the first time and not later does
not quite fit the experience of it working, time after time, and then
inexplicably stop working.  I'm wondering if there's something else I
did to get the dbus daemon into a different state?  I think I'll try
rebooting and get it working reliably again, then pay close attention to
what I do to see if I can figure out what makes it change.

As I wrote this, it occurred to me that maybe the problem is the
firewire connection being broken so I started mythfrontend, waiting
nearly a minute for it to start, and then tried tuning a cable channel
and, indeed, the connection had been lost.  After restarting
mythbackend, the connection was re-established and mythfrontend started
up normally.

So, it seems I have discovered the problem.  I don't understand why the
lack of a connection of the backend to a cable box ("tuner") causes a
slow startup of the frontend, but it seems that it certainly does.  It's
actually a good thing as now I know that if it starts up slow, I need to
restart the backend (at least) so it will be ready when needed (I have
lost recordings due to the lack of connection).

It seems my  problem was not related to dbus nor was it related to media
monitoring.  Others with slow startup will likely not be helped by my
discovery, but it seems all hardware connections should be suspect.

If anyone knows of some way to programmatically check the firewire
connection and, ideally, re-establish it programmatically, I would love
to hear it.

Dave D.


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
>> I've committed a fix to respect the user setting thereby
>> bypassing this check at startup, and backported it to
>> fixes/31. This should be in updated packages in the next
>> 24hrs or so.

Thanks Stuart that indeed fixes the DBUS delay

James
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: Getting slower [ In reply to ]
On 19/08/2020 04:46, DaveD wrote:
> On 8/18/20 3:01 PM, Stuart Auchterlonie wrote:
>> Acutally, looking at
>> https://code.mythtv.org/trac/ticket/12307#comment:11
>>
>> we weren't checking to see if the user had disabled
>> the media monitor early enough, so it was still calling
>> out to dbus.
>>
>> I've committed a fix to respect the user setting thereby
>> bypassing this check at startup, and backported it to
>> fixes/31. This should be in updated packages in the next
>> 24hrs or so.
>>
>>
>> Regards
>> Stuart
>
> This is very encouraging.  I hope you have it figured out.  That said, I
> don't know enough about dbus to fit your model into my experience.
>
> I use a firewire to a cable box and that firewire interface is extremely
> fragile.  If the cable box gets turned off (remote in wrong mode!), I
> have to reboot to get mythbackend to get it's connection back where it
> can change channels again.  Some times I can pull and re-plug the
> firewire cable and restart mythbackend, sometimes I just need to restart
> mythbackend, sometimes I can unload the firewire module and re-modprobe
> it, etc, etc.  But I digress.
>
> A week or so ago, I had to both turn off the power to my computer and
> unplug the cable box then fire it back up to re-establish the
> connection.  After that, mythfrontend started up every day with no
> delay; < 10 seconds from hitting the key on the remote to recordings
> list.  Every time.  Until it didn't.  No idea what changed to make it
> sluggish again, but it takes > 50 seconds, now.
>
> What you said about dbus timing out the first time and not later does
> not quite fit the experience of it working, time after time, and then
> inexplicably stop working.  I'm wondering if there's something else I
> did to get the dbus daemon into a different state?  I think I'll try
> rebooting and get it working reliably again, then pay close attention to
> what I do to see if I can figure out what makes it change.
>
> As I wrote this, it occurred to me that maybe the problem is the
> firewire connection being broken so I started mythfrontend, waiting
> nearly a minute for it to start, and then tried tuning a cable channel
> and, indeed, the connection had been lost.  After restarting
> mythbackend, the connection was re-established and mythfrontend started
> up normally.
>
> So, it seems I have discovered the problem.  I don't understand why the
> lack of a connection of the backend to a cable box ("tuner") causes a
> slow startup of the frontend, but it seems that it certainly does.  It's
> actually a good thing as now I know that if it starts up slow, I need to
> restart the backend (at least) so it will be ready when needed (I have
> lost recordings due to the lack of connection).
>
> It seems my  problem was not related to dbus nor was it related to media
> monitoring.  Others with slow startup will likely not be helped by my
> discovery, but it seems all hardware connections should be suspect.
>
> If anyone knows of some way to programmatically check the firewire
> connection and, ideally, re-establish it programmatically, I would love
> to hear it.
>

There are 2 different problems here.

1) slow frontend startup due to DBus requests for the UDisks service.
2) your firewire issues with the backend described above

My fix will address #1, but has nothing todo with #2

Firewire communication between the backend and the STB does not use
DBus at all.


Regards
Stuart

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org