[mythtv-users] Issues with 0.25
michael at thewatsonfamily.id.au
Mon Feb 27 02:32:53 UTC 2012
Firstly, I know that 0.25 is still under development. This is not a whine.
MBE - Ubuntu 10.04 Server 2.6.32-38-server, x86_64, MythBuntu Repos -
SBE/FE - Mythbuntu 10.04 2.6.32-39-generic, x86_64, MythBuntu Repos -
FE - Ubuntu 10.04 Server 2.6.32-38-generic-pae, MythBuntu Repos -
Unable to add new recording rules using 'mythfrontend' [TV - Schedule
Recordings - Program Guide -> M -> Record This]. No errors are
reported, and the new recording rule is NOT created.
I can create new recording rules using MythWeb successfully.
Unable to use Downloadable Themes
Update Downloadable Themes works,
Selecting a Downloadable theme reports "ERROR Downloading Theme
package on master backend"
Most commercial flagging jobs fail with status code 139, a few have
failed with status code 130. Currently running one of the failed jobs
with gdm debugging enabled. I will upload when this job finishes (Its
taking much longer than usual commflag job)
When Rerunning the commflag on the failed jobs, most run successfully,
but some still fail with 'status code 139'
I have had to increase the max_connections for mysql to 100 (from 60
that work perfectly well under 0.24-fixes) to prevent the MBE from
failing and reporting "Driver error was [1/1040]:#012QMYSQL: Unable to
connect#012Database error was:#012Too many connections"
I have noticed that the MBE has used (backend upto 50 connections,
commflag 2 connections), the SBE/FE (backend 29 connections, frontend 7
Connections, commflag 2 connections), and the FE upto 7 Connections.
Since increasing the max_connections for mysql to 100, it has been very
stable apart from the commercial flagging issue (I can live with that,
it has not been very accurate here for a loong time.)
If anybody has any suggestions (or wants more information) on these
issues, I am happy to provide / try out any.
More information about the mythtv-users