Upgrade from 0.25 to 0.27

Tonyr63 · Post by **Tonyr63** » Thu Sep 03, 2015 2:30 pm

Hello

I run the following command hoping to upgrade.
sudo add-apt-repository ppa:mythbuntu/0.27
sudo apt-get update
sudo apt-get install mythtv

It all seemed to work however I still seem to be on version 0.25. I checked the repo and they are showing 0.27.

then I ran
sudo apt-get install mythtv-backend-master
as well as
sudo apt-get install mythtv-frontend

all seemed to run without error but still on 0.25
If I repeat the two commands above I now get the message that I am already on the latest version but I am not. Synaptic Package Manager says I am still on 0.25 but strangely says the latest version is 0.25 and not 0.27 so it thinks I am up to date yet the repos show 0.27 so why does Refresh not now show MythTv as behind the latest version 0.27

How do I trigger the upgrade? Many of my frontends will not connect saying the dB schema is 18 versions old. Only XBMC 13.2 can connect from Windows.

ctmjr · Post by **ctmjr** » Thu Sep 03, 2015 2:37 pm

Hello, did you stop the old backend and frontend before upgrading? Then try to start them. Or better yet try a reboot.

Tonyr63 · Post by **Tonyr63** » Fri Sep 04, 2015 9:10 am

Hello

Yes stopped the backend before upgrading and have restarted the system completely before posting my problem.

Tonyr63 · Post by **Tonyr63** » Fri Sep 04, 2015 10:19 am

How do you Shut down all mythfrontend processes? I assumed on my Backend machine as I had not opened the frontend it did not need to be shutdown but does this mean that there are background processes running that need to be shutdown? The instruction does not show you how to Shut down all mythfrontend processes or provide the command to use. In windows you can stop and start services in the services applet how do you in Linux shut down all mythfrontend processes
Here is the instruction I was reviewing.

https://www.mythtv.org/wiki/Backend_migration

Post by **paulh** » Sat Sep 05, 2015 7:03 am

It's difficult to say from your description but it sounds like you have a mix of systems using 0.27 and 0.25 which wont work.

You will have to update ALL systems to 0.27 including whatever plugin XBMC is using.

The first time you start either mythtv-setup or mythbackend there will be a long pause while the database is first backed up then upgraded to the new version.

As always the logs are your friend to tell you what is happening.

Tonyr63 · Post by **Tonyr63** » Sat Sep 05, 2015 10:44 am

Hello

The log file is not friendly as it tells me nothing I can understand. I reviewed the setup log file is there any more I should look at?

Why does the system report "mythtv is at the newest version" when it is not?

Post by **paulh** » Sat Sep 05, 2015 3:01 pm

Maybe you somehow have two versions installed in different directories and 0.25 is the first in the path so loads first? Have you compiled your own version and installed from packages which are usually installed in different places

If you attach or pastebin the logs maybe we will be able to help you. Lets start with the mythbackend log to see if it is starting up OK and it is the version you think it is

Post by **dizygotheca** » Sat Sep 05, 2015 5:44 pm

Package Manager says I am still on 0.25 but strangely says the latest version is 0.25 and not 0.27 so it thinks I am up to date yet the repos show 0.27 so why does Refresh not now show MythTv as behind the latest version 0.27

If you're coming from 0.25 then some dependencies probably need upgrading before 0.27 will install.

I'm no expert on apt-get but

Code: Select all

apt-get -sV install mythtv
apt-get -sV upgrade

may give some clues. Because of the "-s" (simulate) they won't change anything.

How do you Shut down all mythfrontend processes? I assumed on my Backend machine as I had not opened the frontend it did not need to be shutdown but does this mean that there are background processes running that need to be shutdown? The instruction does not show you how to Shut down all mythfrontend processes or provide the command to use. In windows you can stop and start services in the services applet how do you in Linux shut down all mythfrontend processes

"mythfrontend processes" just refers to any frontends (local and remote, Myth/Kodi) that are connected to the backend. If you don't shut them down manually before upgrading the backend they'll lose connection & fail to re-connect to the updated backend - messy but not a problem. There are no frontend "services" on the backend.

Tonyr63 · Post by **Tonyr63** » Mon Sep 07, 2015 9:59 am

paulh wrote:Maybe you somehow have two versions installed in different directories and 0.25 is the first in the path so loads first? Have you compiled your own version and installed from packages which are usually installed in different places

If you attach or pastebin the logs maybe we will be able to help you. Lets start with the mythbackend log to see if it is starting up OK and it is the version you think it is

I installed using the following command hoping to upgrade.
sudo add-apt-repository ppa:mythbuntu/0.27
sudo apt-get update
sudo apt-get install mythtv

I have not compiled my own version or know how to do so.

The backend log is as follows:

Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: C thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging) mythbackend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: C thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLogging) Qt version: compile: 4.8.6, runtime: 4.8.6
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: N thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) Enabled verbose msgs: general
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: N thread_unknown logging.cpp:914 (logStart) Setting Log Level to LOG_INFO
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I Logger logging.cpp:315 (run) Added logging to the console
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: N thread_unknown mythdirs.cpp:55 (InitializeMythDirs) Using runtime prefix = /usr
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: N thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Sep 7 18:28:48 Telelinux mythbackend: mythbackend[1927]: I CoreContext mythcorecontext.cpp:254 (Init) Assumed character encoding: en_AU.UTF-8
Sep 7 18:28:49 Telelinux mythbackend: mythbackend[1927]: N CoreContext mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Sep 7 18:28:49 Telelinux mythbackend: mythbackend[1927]: I CoreContext mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost value of Telelinux
Sep 7 18:28:49 Telelinux mythbackend: mythbackend[1927]: I LogForward loggingserver.cpp:1372 (forwardMessage) New Client: (#1)
Sep 7 18:28:49 Telelinux mythbackend: mythbackend[1927]: I LogForward loggingserver.cpp:295 (SyslogLogger) Added syslogging
Sep 7 18:28:49 Telelinux mythbackend: mythbackend[1927]: E CoreContext mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Sep 7 18:28:49 Telelinux mythbackend: mythbackend[1927]: E CoreContext mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: Unable to connect#012Database error was:#012Access denied for user 'mythtv'@'localhost' (using password: YES)
Sep 7 18:28:49 Telelinux mythbackend: mythbackend[1927]: C CoreContext main.cpp:116 (main) Failed to init MythContext.
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: C thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging) mythbackend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: C thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLogging) Qt version: compile: 4.8.6, runtime: 4.8.6
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: N thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) Enabled verbose msgs: general
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: N thread_unknown logging.cpp:914 (logStart) Setting Log Level to LOG_INFO
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I Logger logging.cpp:315 (run) Added logging to the console
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: N thread_unknown mythdirs.cpp:55 (InitializeMythDirs) Using runtime prefix = /usr
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: N thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I CoreContext mythcorecontext.cpp:254 (Init) Assumed character encoding: en_AU.UTF-8
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: N CoreContext mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: I CoreContext mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost value of Telelinux
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: E CoreContext mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: E CoreContext mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: Unable to connect#012Database error was:#012Access denied for user 'mythtv'@'localhost' (using password: YES)
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2004]: C CoreContext main.cpp:116 (main) Failed to init MythContext.
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: C thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging) mythbackend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: C thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLogging) Qt version: compile: 4.8.6, runtime: 4.8.6
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: N thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) Enabled verbose msgs: general
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: N thread_unknown logging.cpp:914 (logStart) Setting Log Level to LOG_INFO
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: N thread_unknown mythdirs.cpp:55 (InitializeMythDirs) Using runtime prefix = /usr
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: N thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I CoreContext mythcorecontext.cpp:254 (Init) Assumed character encoding: en_AU.UTF-8
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I Logger logging.cpp:315 (run) Added logging to the console
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: N CoreContext mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I CoreContext mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost value of Telelinux
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: E CoreContext mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: E CoreContext mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: Unable to connect#012Database error was:#012Access denied for user 'mythtv'@'localhost' (using password: YES)
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: C CoreContext main.cpp:116 (main) Failed to init MythContext.
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I LogForward loggingserver.cpp:1372 (forwardMessage) New Client: (#1)
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: I LogForward loggingserver.cpp:295 (SyslogLogger) Added syslogging
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: C thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging) mythbackend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: C thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLogging) Qt version: compile: 4.8.6, runtime: 4.8.6
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: N thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) Enabled verbose msgs: general
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: N thread_unknown logging.cpp:914 (logStart) Setting Log Level to LOG_INFO
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I Logger logging.cpp:315 (run) Added logging to the console
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: N thread_unknown mythdirs.cpp:55 (InitializeMythDirs) Using runtime prefix = /usr
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: N thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I CoreContext mythcorecontext.cpp:254 (Init) Assumed character encoding: en_AU.UTF-8
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: N CoreContext mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I CoreContext mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost value of Telelinux
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I LogForward loggingserver.cpp:1372 (forwardMessage) New Client: (#1)
Sep 7 18:37:09 Telelinux mythbackend: mythbackend[1926]: I LogForward loggingserver.cpp:295 (SyslogLogger) Added syslogging
Sep 7 18:37:10 Telelinux mythbackend: mythbackend[1926]: E CoreContext mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Sep 7 18:37:10 Telelinux mythbackend: mythbackend[1926]: E CoreContext mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: Unable to connect#012Database error was:#012Access denied for user 'mythtv'@'localhost' (using password: YES)
Sep 7 18:37:10 Telelinux mythbackend: mythbackend[1926]: C CoreContext main.cpp:116 (main) Failed to init MythContext.
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: C thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging) mythbackend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: C thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLogging) Qt version: compile: 4.8.6, runtime: 4.8.6
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: N thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) Enabled verbose msgs: general
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: N thread_unknown logging.cpp:914 (logStart) Setting Log Level to LOG_INFO
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: N thread_unknown mythdirs.cpp:55 (InitializeMythDirs) Using runtime prefix = /usr
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: N thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I CoreContext mythcorecontext.cpp:254 (Init) Assumed character encoding: en_AU.UTF-8
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: N CoreContext mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I CoreContext mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost value of Telelinux
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: I Logger logging.cpp:315 (run) Added logging to the console
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: E CoreContext mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: E CoreContext mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: Unable to connect#012Database error was:#012Access denied for user 'mythtv'@'localhost' (using password: YES)
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2005]: C CoreContext main.cpp:116 (main) Failed to init MythContext.
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: C thread_unknown mythcommandlineparser.cpp:2595 (ConfigureLogging) mythbackend version: fixes/0.27 [v0.27-193-g8ee257c] www.mythtv.org
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: C thread_unknown mythcommandlineparser.cpp:2597 (ConfigureLogging) Qt version: compile: 4.8.6, runtime: 4.8.6
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: N thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging) Enabled verbose msgs: general
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: N thread_unknown logging.cpp:914 (logStart) Setting Log Level to LOG_INFO
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Interrupt handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Terminated handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Segmentation fault handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Aborted handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus error handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Floating point exception handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Illegal instruction handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Real-time signal 0 handler
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: N thread_unknown mythdirs.cpp:55 (InitializeMythDirs) Using runtime prefix = /usr
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: N thread_unknown mythdirs.cpp:68 (InitializeMythDirs) Using configuration directory = /home/mythtv/.mythtv
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I CoreContext mythcorecontext.cpp:254 (Init) Assumed character encoding: en_AU.UTF-8
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: N CoreContext mythcontext.cpp:504 (LoadDatabaseSettings) Empty LocalHostName.
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I CoreContext mythcontext.cpp:512 (LoadDatabaseSettings) Using localhost value of Telelinux
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: E CoreContext mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: E CoreContext mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: Unable to connect#012Database error was:#012Access denied for user 'mythtv'@'localhost' (using password: YES)
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: C CoreContext main.cpp:116 (main) Failed to init MythContext.
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I Logger logging.cpp:315 (run) Added logging to the console
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I LogForward loggingserver.cpp:1372 (forwardMessage) New Client: (#1)
Sep 7 18:37:11 Telelinux mythbackend: mythbackend[2025]: I LogForward loggingserver.cpp:295 (SyslogLogger) Added syslogging

Tonyr63 · Post by **Tonyr63** » Mon Sep 07, 2015 10:41 am

Having so many problems with mythtv not upgrading I decided to try to upgrade Ubuntu as it was still running 10.04
I backed up my data and upgraded to 14.04 LTR and the upgrade whet OK without any errors except MythTv.
The upgrade reported that it upgraded All application except MythTv and and advised I upgrade manually.
I used the software centre applet and chose MythTv which installed a backend and Frontend version 2:0.27.0 + fixes. I tried this because the apt get commands failed before.
When I went to start the backend admn program I got prompted with the looping setup screens which recognized my location and correctly saw all my old config and had the correct backend password but will not connect.
I don't understand why if it has the correct IP, port and password what is the problem?
I am out of ideas. MythTv is installed in the default location on my system and has never been altered.
Surprised that apt get install failed so completely and why does the upgrade program not know which services to stop and which folders to update.
I don't understand why the installed MythTv version seeing my config cannot update the schema on first run if this is the issue?
Does this mean that the new myth install has created a fresh mySQL db? I cannot see how it would and not prompt for name and password information? How is mythtv supposed to be enabled on a system if installed using the software install applet? I does more than download so is supposed to install for use so why does it not prompt for information if it requires settings?

Here is an extract from the MySQL log file that might mean something to those with more understanding of MythTv.

AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld in /etc/apparmor.d/usr.sbin.mysqld at line 44: Could not open 'local/usr.sbin.mysqld'
150906 17:30:52 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150906 17:30:52 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0ubuntu0.14.04.1) starting as process 9007 ...
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)'
Checking for tables which need an upgrade, are corrupt or were
not closed cleanly.

Post by **dizygotheca** » Mon Sep 07, 2015 11:08 am

Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: E CoreContext mythdbcon.cpp:216 (OpenDatabase) Unable to connect to database!
Sep 7 18:28:50 Telelinux mythbackend: mythbackend[2019]: E CoreContext mythdbcon.cpp:217 (OpenDatabase) Driver error was [1/1045]:#012QMYSQL: Unable to connect#012Database error was:#012Access denied for user 'mythtv'@'localhost' (using password: YES)

The Software Centre repositories are old and contain a packaging error that can corrupt the password set within MySql.

The end of this thread explains more and has a possible fix. Read it all before trying anything...
viewtopic.php?f=36&t=67

Tonyr63 · Post by **Tonyr63** » Mon Sep 07, 2015 1:29 pm

Hello

Thanks for the pointer. I will review carefully and advise.
Kind Regards

Tonyr63 · Post by **Tonyr63** » Mon Sep 07, 2015 2:29 pm

Hello

I read completely through the article and though I had a handle on the issue.

Then I tried to follow these instructions.

Myth requires the password to be set in 4 places;

/etc/mythtv/config.xml for the backend
/home/<user>/.mythtv/config.xml for the frontend
MySql access
MySql permissions

/etc/mythtv/config.xml for the backend has some obscure password so i reset it to what the old backend password used to be.
This made no difference to my problem.

Then I checked /home/<user>/.mythtv/config.xml for the frontend but realised that this is just a symlink (shortcut) to the same file in /etc/mythtv /config.xml and it now had the correct password.

Then I ran from the terminal:
$ mysql -p -u root mythconverg
Enter password: Use the admin password you set when MySql was installed
mysql> select user,host,password from mysql.user where user = 'mythtv';
mysql> show grants for mythtv;
mysql> exit

And NOTHING happened. After 5 minutes waiting I went to close the terminal and it warned that a process was still running - what process?
Then I realised I needed to run each line at a time an ignoe the explicit instruction Code Select All.

Anyway I got to see my pwd 77670917F286B3C007525AA595067A4C5B2972E6. Now how does that help me? If I paste this in my backend will it start? Of coused that did not work.

Perhaps before I do some real damage I should check exactly do i need to do to fix?
I follow the logic of purgeing the old config files however I do not follow where I set the new password as I do not want to have it set a random automatically?

Where in this block do I get to set a new password?

$ mysql -p -u root mythconverg
Enter password: Use the admin password you set when MySql was installed
mysql> drop user 'mythtv'@'%';
mysql> drop user 'mythtv'@'localhost';
mysql> flush privileges;
mysql> exit.

Tonyr63 · Post by **Tonyr63** » Mon Sep 07, 2015 2:42 pm

Hi
When I ran..

mysql> drop user 'mythtv'@'%';
Query OK, 0 rows affected (0.44 sec)

mysql> drop user 'mythtv'@'localhost';
Query OK, 0 rows affected (0.00 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

mysql> exit
Bye

Does 0 rows affected mean the commands did not work? Should I proceed?

Post by **dizygotheca** » Mon Sep 07, 2015 8:42 pm

/etc/mythtv/config.xml for the backend has some obscure password

This was the random password created by installing from Software Centre

Anyway I got to see my pwd 77670917F286B3C007525AA595067A4C5B2972E6

This is the MySql encrypted version of your password. No-one can derive your password from it but we need to confirm that all your passwords are set to the same.

To illustrate: the password "mythtv" is encrypted to:

Code: Select all

mysql> select password('mythtv');
+-------------------------------------------+
| password('mythtv')                        |
+-------------------------------------------+
| *CC8F35F587CA5A556B4132C2407E556D92172FFC |
+-------------------------------------------+
1 row in set (0.00 sec)

Here you can see that the MySql passwords & privileges for mythtv are set to the same value...

Code: Select all

mysql> select user,host,password from mysql.user where user = 'mythtv';
+--------+-----------+-------------------------------------------+
| user   | host      | password                                  |
+--------+-----------+-------------------------------------------+
| mythtv | localhost | *CC8F35F587CA5A556B4132C2407E556D92172FFC |
| mythtv | %         | *CC8F35F587CA5A556B4132C2407E556D92172FFC |
+--------+-----------+-------------------------------------------+
2 rows in set (0.00 sec)

mysql> show grants for mythtv;
+----------------------------------------------------------------------------------------------------------------+
| Grants for mythtv@%                                                                                            |
+----------------------------------------------------------------------------------------------------------------+
| GRANT ALL PRIVILEGES ON *.* TO 'mythtv'@'%' IDENTIFIED BY PASSWORD '*CC8F35F587CA5A556B4132C2407E556D92172FFC' |
+----------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

So the mythtv user can connect to MySql:

Code: Select all

$ mysql -p -u mythtv mythconverg
Enter password: mythtv
Welcome to the MySQL monitor.  Commands end with ; or \g.
mysql>

And providing the config.xmls contain the password "mythtv" then both frontend & backend will run happily.

Where in this block do I get to set a new password?

You don't. Probably isn't difficult to research the SQL to set it directly, but the (safer, simpler ?) idea here is to flush the MySql settings out so that the installer will set *everything* correctly when you reconfigure (reinstall) them. It only does this if the passwords don't already exist. That way, *when* you install the Mythbuntu repository and upgrade to 27.5 (27.0 is very old) it won't disturb the passwords again!

I do not want to have it set a random automatically

Not sure what Software Centre does but when you reconfigure from the terminal you will get a chance to specify your password.

Does 0 rows affected mean the commands did not work? Should I proceed?

It means there is nothing to clear (you probably ran the command previously). That's good.
Now reconfigure the packages and enter your password, when asked.

Code: Select all

$ sudo dpkg-reconfigure mythtv-common
$ sudo dpkg-reconfigure mythtv-database

and create your frontend config.xml

Code: Select all

$ ln -s /etc/mythtv/config.xml /home/<user>/.mythtv/

If you then check your passwords/grants again they should all now be showing 77670917F286B3C007525AA595067A4C5B2972E6 and your config.xmls should all have the correct password set.

MythTV Official Community Forum

Upgrade from 0.25 to 0.27

Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27

Re: Upgrade from 0.25 to 0.27