package mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Bug #1382815 reported by Mark Lundy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mythbuntu
Invalid
Undecided
Unassigned

Bug Description

mythtv database not updating. Frontend complains that schema is 18 versions behind

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27]
ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25
Uname: Linux 3.8.0-44-generic i686
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythfilldatabase.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythtranscode.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu17.7
Architecture: i386
CrashDB: mythbuntu
Date: Fri Oct 17 18:31:19 2014
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release i386 (20130820)
Installed_mythtv_dbg: 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1
MarkForUpload: True
PackageArchitecture: all
SourcePackage: mythtv
Title: package mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Mark Lundy (mark-lundy) wrote :
Revision history for this message
Thomas Mashos (tgm4883) wrote :

It appears you had incorrect info in your /etc/mythtv/config.xml file

Changed in mythbuntu:
status: New → Invalid
Revision history for this message
Mark Lundy (mark-lundy) wrote : Re: [Bug 1382815] Re: package mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Many thanks Thomas

Regards

Mark

On 11/01/15 01:47, Thomas Mashos wrote:
> It appears you had incorrect info in your /etc/mythtv/config.xml file
>
> ** Changed in: mythbuntu
> Status: New => Invalid
>

Revision history for this message
Mark Lundy (mark-lundy) wrote :

Hi Thomas

Which incorrect info in /etc/mythtv/config.xml? (I am new(ish) to linux\ubuntu)
It all looks OK to me?

<Configuration>
  <UPnP>
    <MythFrontend>
      <DefaultBackend>
        <!--
Set the <LocalHostName> hostname override below only if you want to use
something other than the machine's real hostname for identifying settings
in the database. This is useful if your hostname changes often, as
otherwise you'll need to reconfigure mythtv every time.

NO TWO HOSTS MAY USE THE SAME VALUE
-->
        <DBHostName>192.168.1.13</DBHostName>
        <DBUserName>mythtv</DBUserName>
        <DBPassword>mythtv</DBPassword>
        <DBName>mythconverg</DBName>
        <DBPort>3306</DBPort>
      </DefaultBackend>
    </MythFrontend>

(.13 is static IP)

Thank you for looking
M

Revision history for this message
Thomas Mashos (tgm4883) wrote : Re: [Mythbuntu-bugs] [Bug 1382815] Re: package mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Download full text (3.5 KiB)

Are you sure that the DB info is correct? The DB password usually
isn't 'mythtv' (it's not by default). Can you login to mysql on your
backend by doing

mysql -u mythtv -pmythtv -h 192.168.1.13 mythconverg

On Thu, Jan 15, 2015 at 12:01 PM, Mark Lundy <email address hidden> wrote:
> Hi Thomas
>
> Which incorrect info in /etc/mythtv/config.xml? (I am new(ish) to linux\ubuntu)
> It all looks OK to me?
>
>
> <Configuration>
> <UPnP>
> <MythFrontend>
> <DefaultBackend>
> <!--
> Set the <LocalHostName> hostname override below only if you want to use
> something other than the machine's real hostname for identifying settings
> in the database. This is useful if your hostname changes often, as
> otherwise you'll need to reconfigure mythtv every time.
>
> NO TWO HOSTS MAY USE THE SAME VALUE
> -->
> <DBHostName>192.168.1.13</DBHostName>
> <DBUserName>mythtv</DBUserName>
> <DBPassword>mythtv</DBPassword>
> <DBName>mythconverg</DBName>
> <DBPort>3306</DBPort>
> </DefaultBackend>
> </MythFrontend>
>
> (.13 is static IP)
>
> Thank you for looking
> M
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
> https://bugs.launchpad.net/bugs/1382815
>
> Title:
> package mythtv-database
> 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-
> mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess
> installed post-installation script returned error exit status 1
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> Invalid
>
> Bug description:
> mythtv database not updating. Frontend complains that schema is 18
> versions behind
>
> ProblemType: Package
> DistroRelease: Ubuntu 12.04
> Package: mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27]
> ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25
> Uname: Linux 3.8.0-44-generic i686
> .var.log.mythtv.mythavtest.log:
>
> .var.log.mythtv.mythccextractor.log:
>
> .var.log.mythtv.mythfilldatabase.log:
>
> .var.log.mythtv.mythjobqueue.log:
>
> .var.log.mythtv.mythlcdserver.log:
>
> .var.log.mythtv.mythmediaserver.log:
>
> .var.log.mythtv.mythshutdown.log:
>
> .var.log.mythtv.mythtranscode.log:
>
> .var.log.mythtv.mythutil.log:
>
> .var.log.mythtv.mythwelcome.log:
>
> ApportVersion: 2.0.1-0ubuntu17.7
> Architecture: i386
> CrashDB: mythbuntu
> Date: Fri Oct 17 18:31:19 2014
> ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
> InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release i386 (20130820)
> Installed_mythtv_dbg: 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1
> MarkForUpload: True
> PackageArchitecture: all
> SourcePackage: mythtv
> Title: package mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
> UpgradeStatus: No upgrade log present (probably fresh install)
>
...

Read more...

Revision history for this message
Mark Lundy (mark-lundy) wrote :
Download full text (4.5 KiB)

Hi Thomas

As I say, I am Newish. I have had Mythtv going for some time. (I
access it from Raspbmc). Getting by on a wing and a prayer. I suspect
that I followed this link at some stage.

http://www.mythtv.org/wiki/Category:MySQL

(I did install the Parker1 install instructions). This would be my 2nd
attempt. (Got a larger HD and did a fresh install).

Yes - I can log into mysql with that command.

The machine had been off since about October. I turned it on at
Christmas. It wouldn't boot to desktop. I logged into recovery mode
and did all the easy fixes. It now boots to Desktop and logs onto the
network. I can access recordings from another machine -but, can't
record anything because it also seems to have lost the TV Card. A
tricky card to find initially (7133).

But, one thing at a time.

Regards

Mark

On 15/01/15 20:57, Thomas Mashos wrote:
> Are you sure that the DB info is correct? The DB password usually
> isn't 'mythtv' (it's not by default). Can you login to mysql on your
> backend by doing
>
> mysql -u mythtv -pmythtv -h 192.168.1.13 mythconverg
>
>
> On Thu, Jan 15, 2015 at 12:01 PM, Mark Lundy <email address hidden> wrote:
>> Hi Thomas
>>
>> Which incorrect info in /etc/mythtv/config.xml? (I am new(ish) to linux\ubuntu)
>> It all looks OK to me?
>>
>>
>> <Configuration>
>> <UPnP>
>> <MythFrontend>
>> <DefaultBackend>
>> <!--
>> Set the <LocalHostName> hostname override below only if you want to use
>> something other than the machine's real hostname for identifying settings
>> in the database. This is useful if your hostname changes often, as
>> otherwise you'll need to reconfigure mythtv every time.
>>
>> NO TWO HOSTS MAY USE THE SAME VALUE
>> -->
>> <DBHostName>192.168.1.13</DBHostName>
>> <DBUserName>mythtv</DBUserName>
>> <DBPassword>mythtv</DBPassword>
>> <DBName>mythconverg</DBName>
>> <DBPort>3306</DBPort>
>> </DefaultBackend>
>> </MythFrontend>
>>
>> (.13 is static IP)
>>
>> Thank you for looking
>> M
>>
>> --
>> You received this bug notification because you are a member of Mythbuntu
>> Bug Team, which is subscribed to Mythbuntu.
>> https://bugs.launchpad.net/bugs/1382815
>>
>> Title:
>> package mythtv-database
>> 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-
>> mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess
>> installed post-installation script returned error exit status 1
>>
>> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
>> Invalid
>>
>> Bug description:
>> mythtv database not updating. Frontend complains that schema is 18
>> versions behind
>>
>> ProblemType: Package
>> DistroRelease: Ubuntu 12.04
>> Package: mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27]
>> ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25
>> Uname: Linux 3.8.0-44-generic i686
>> .var.log.mythtv.mythavtest.log:
>>
>> .var.log.mythtv.mythccextractor.log:
>>
>> .var.log.mythtv.mythfilldatabase.log:
>>
>> .var.log.mythtv.mythjobqueue.log:
>>
>> .var.log.mythtv.mythlc...

Read more...

Revision history for this message
Thomas Mashos (tgm4883) wrote :
Download full text (7.2 KiB)

Mark,

Are you still getting the error message that prompted create this ticket?

On Fri, Jan 16, 2015 at 10:04 AM, Mark Lundy <email address hidden> wrote:
> Hi Thomas
>
> As I say, I am Newish. I have had Mythtv going for some time. (I
> access it from Raspbmc). Getting by on a wing and a prayer. I suspect
> that I followed this link at some stage.
>
> http://www.mythtv.org/wiki/Category:MySQL
>
> (I did install the Parker1 install instructions). This would be my 2nd
> attempt. (Got a larger HD and did a fresh install).
>
>
> Yes - I can log into mysql with that command.
>
> The machine had been off since about October. I turned it on at
> Christmas. It wouldn't boot to desktop. I logged into recovery mode
> and did all the easy fixes. It now boots to Desktop and logs onto the
> network. I can access recordings from another machine -but, can't
> record anything because it also seems to have lost the TV Card. A
> tricky card to find initially (7133).
>
> But, one thing at a time.
>
> Regards
>
> Mark
>
>
> On 15/01/15 20:57, Thomas Mashos wrote:
>> Are you sure that the DB info is correct? The DB password usually
>> isn't 'mythtv' (it's not by default). Can you login to mysql on your
>> backend by doing
>>
>> mysql -u mythtv -pmythtv -h 192.168.1.13 mythconverg
>>
>>
>> On Thu, Jan 15, 2015 at 12:01 PM, Mark Lundy <email address hidden> wrote:
>>> Hi Thomas
>>>
>>> Which incorrect info in /etc/mythtv/config.xml? (I am new(ish) to linux\ubuntu)
>>> It all looks OK to me?
>>>
>>>
>>> <Configuration>
>>> <UPnP>
>>> <MythFrontend>
>>> <DefaultBackend>
>>> <!--
>>> Set the <LocalHostName> hostname override below only if you want to use
>>> something other than the machine's real hostname for identifying settings
>>> in the database. This is useful if your hostname changes often, as
>>> otherwise you'll need to reconfigure mythtv every time.
>>>
>>> NO TWO HOSTS MAY USE THE SAME VALUE
>>> -->
>>> <DBHostName>192.168.1.13</DBHostName>
>>> <DBUserName>mythtv</DBUserName>
>>> <DBPassword>mythtv</DBPassword>
>>> <DBName>mythconverg</DBName>
>>> <DBPort>3306</DBPort>
>>> </DefaultBackend>
>>> </MythFrontend>
>>>
>>> (.13 is static IP)
>>>
>>> Thank you for looking
>>> M
>>>
>>> --
>>> You received this bug notification because you are a member of Mythbuntu
>>> Bug Team, which is subscribed to Mythbuntu.
>>> https://bugs.launchpad.net/bugs/1382815
>>>
>>> Title:
>>> package mythtv-database
>>> 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-
>>> mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess
>>> installed post-installation script returned error exit status 1
>>>
>>> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
>>> Invalid
>>>
>>> Bug description:
>>> mythtv database not updating. Frontend complains that schema is 18
>>> versions behind
>>>
>>> ProblemType: Package
>>> DistroRelease: Ubuntu 12.04
>>> Package: mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27]
>>> ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-g...

Read more...

Revision history for this message
Mark Lundy (mark-lundy) wrote :
Download full text (7.7 KiB)

Hi Thomas

Yes - I got the same error when I asked it to update after being off for
a while. Can't find my TV Card and grep -i dvb /var/log/messages
doesn't work?

M

On 16/01/15 20:39, Thomas Mashos wrote:
> Mark,
>
> Are you still getting the error message that prompted create this
> ticket?
>
> On Fri, Jan 16, 2015 at 10:04 AM, Mark Lundy <email address hidden> wrote:
>> Hi Thomas
>>
>> As I say, I am Newish. I have had Mythtv going for some time. (I
>> access it from Raspbmc). Getting by on a wing and a prayer. I suspect
>> that I followed this link at some stage.
>>
>> http://www.mythtv.org/wiki/Category:MySQL
>>
>> (I did install the Parker1 install instructions). This would be my 2nd
>> attempt. (Got a larger HD and did a fresh install).
>>
>>
>> Yes - I can log into mysql with that command.
>>
>> The machine had been off since about October. I turned it on at
>> Christmas. It wouldn't boot to desktop. I logged into recovery mode
>> and did all the easy fixes. It now boots to Desktop and logs onto the
>> network. I can access recordings from another machine -but, can't
>> record anything because it also seems to have lost the TV Card. A
>> tricky card to find initially (7133).
>>
>> But, one thing at a time.
>>
>> Regards
>>
>> Mark
>>
>>
>> On 15/01/15 20:57, Thomas Mashos wrote:
>>> Are you sure that the DB info is correct? The DB password usually
>>> isn't 'mythtv' (it's not by default). Can you login to mysql on your
>>> backend by doing
>>>
>>> mysql -u mythtv -pmythtv -h 192.168.1.13 mythconverg
>>>
>>>
>>> On Thu, Jan 15, 2015 at 12:01 PM, Mark Lundy <email address hidden> wrote:
>>>> Hi Thomas
>>>>
>>>> Which incorrect info in /etc/mythtv/config.xml? (I am new(ish) to linux\ubuntu)
>>>> It all looks OK to me?
>>>>
>>>>
>>>> <Configuration>
>>>> <UPnP>
>>>> <MythFrontend>
>>>> <DefaultBackend>
>>>> <!--
>>>> Set the <LocalHostName> hostname override below only if you want to use
>>>> something other than the machine's real hostname for identifying settings
>>>> in the database. This is useful if your hostname changes often, as
>>>> otherwise you'll need to reconfigure mythtv every time.
>>>>
>>>> NO TWO HOSTS MAY USE THE SAME VALUE
>>>> -->
>>>> <DBHostName>192.168.1.13</DBHostName>
>>>> <DBUserName>mythtv</DBUserName>
>>>> <DBPassword>mythtv</DBPassword>
>>>> <DBName>mythconverg</DBName>
>>>> <DBPort>3306</DBPort>
>>>> </DefaultBackend>
>>>> </MythFrontend>
>>>>
>>>> (.13 is static IP)
>>>>
>>>> Thank you for looking
>>>> M
>>>>
>>>> --
>>>> You received this bug notification because you are a member of Mythbuntu
>>>> Bug Team, which is subscribed to Mythbuntu.
>>>> https://bugs.launchpad.net/bugs/1382815
>>>>
>>>> Title:
>>>> package mythtv-database
>>>> 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-
>>>> mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess
>>>> installed post-installation script returned error exit status 1
>>>>
>>>> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
>>>> Invalid
>>>>
>>>> Bug description:
>>>> mythtv dat...

Read more...

Revision history for this message
Thomas Mashos (tgm4883) wrote :

From your log, I see

Setting up mythtv-database (2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 columns wide.)
debconf: falling back to frontend: Readline
ERROR 1046 (3D000) at line 22: No database selected

So it looks like it's trying to prompt you for info, can't because the dialog box isn't big enough, can't find the DB so it exits. Every time I've seen this error it's from an upgrade to 0.27 where /etc/mythtv/config.xml doesn't have the right info.

Can you check if /root/.mythtv/config.xml contains the same info.

Can you try doing the update from the command line? "apt-get upgrade"

Revision history for this message
Mark Lundy (mark-lundy) wrote : Re: [Bug 1382815] Re: package mythtv-database 2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.27] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Hi Thomas

Hopefully - I'll get a look at this tomorrow?

Thanks for your time

M

On 16/01/15 23:33, Thomas Mashos wrote:
> >From your log, I see
>
> Setting up mythtv-database (2:0.27.4+fixes.20141017.e830993-0ubuntu0mythbuntu1) ...
> debconf: unable to initialize frontend: Dialog
> debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 columns wide.)
> debconf: falling back to frontend: Readline
> ERROR 1046 (3D000) at line 22: No database selected
>
> So it looks like it's trying to prompt you for info, can't because the
> dialog box isn't big enough, can't find the DB so it exits. Every time
> I've seen this error it's from an upgrade to 0.27 where
> /etc/mythtv/config.xml doesn't have the right info.
>
> Can you check if /root/.mythtv/config.xml contains the same info.
>
> Can you try doing the update from the command line? "apt-get upgrade"
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.