Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

Problem with Ubuntu upgrade 0.24 to 0.25

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


myth at surr

May 7, 2012, 12:42 PM

Post #1 of 24 (3425 views)
Permalink
Problem with Ubuntu upgrade 0.24 to 0.25

Hello all,

Well, sometimes it goes smoothly, sometimes not. A few days ago, I
switched over my Ubuntu install of mythtv (Mythbuntu on top of an Ubuntu
setup) from the 0,24 repositories to the 0.25 repositories. After
running the Update Manager, it suggested that I do a 'partial upgrade'.

Most of the update went without a hitch, except for upgrading the
mythtv.cnf file. I got a message asking me if I wanted to keep the
current file or accept the changes. I've been stung by this sort of
thing before, so I cut and pasted the differences. Here's what was
displayed during the install:

--- /etc/mysql/conf.d/mythtv.cnf 2012-04-18 20:27:49.000000000 +0100
+++ /etc/mysql/conf.d/mythtv.cnf.dpkg-new 2012-05-03
00:07:41.000000000 +0100
@@ -1,2 +1,3 @@
[mysqld]
-bind-address=0.0.0.0
+#bind-address=0.0.0.0
+max_connections=100

I believe I told it to keep the current file. Here's the contents of my
mythtv.cnf file as it is today:

[mysqld]
bind-address=0.0.0.0
max_connections=100

The install then continued as normal and finished. Now the fun begins :-)

I tried to run the frontend (on the same system) and a little message at
the bottom of the screen (gnome) kept popping up saying that the
frontend was restarting. This popped up every few seconds, so it was in
some sort of loop.

I rebooted and still had the same problem.

If I try to go to the backand setup, I get asked if I would like to
start the mythtv backend, which implys that the back end isn't even
running any more. I click on 'yes' and am then asked if I would like to
run mythfilldatabase. I click 'yes' again. At no point am I taken into
the backend setup screens.

If I try to go into the backend setup again, I get asked if I want to
run mythtv backend again etc etc.

I've just had a look at /var/log/mythtv/mythbackend.log and it doesn't
seem to have had an entry since 3rd May. The
/var/log/mythtv/mythfrontend.log file hasn't had an entry since the 2nd May.

Where can I look for some information that could help to fix this?

Thanks
Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


jakommo at gmail

May 7, 2012, 1:15 PM

Post #2 of 24 (3373 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 05/07/2012 09:42 PM, Damian wrote:
> Hello all,
>
> Well, sometimes it goes smoothly, sometimes not. A few days ago, I
> switched over my Ubuntu install of mythtv (Mythbuntu on top of an
> Ubuntu setup) from the 0,24 repositories to the 0.25 repositories.
> After running the Update Manager, it suggested that I do a 'partial
> upgrade'.
>
> Most of the update went without a hitch, except for upgrading the
> mythtv.cnf file. I got a message asking me if I wanted to keep the
> current file or accept the changes. I've been stung by this sort of
> thing before, so I cut and pasted the differences. Here's what was
> displayed during the install:
>
> --- /etc/mysql/conf.d/mythtv.cnf 2012-04-18 20:27:49.000000000 +0100
> +++ /etc/mysql/conf.d/mythtv.cnf.dpkg-new 2012-05-03
> 00:07:41.000000000 +0100
> @@ -1,2 +1,3 @@
> [mysqld]
> -bind-address=0.0.0.0
> +#bind-address=0.0.0.0
> +max_connections=100
>
> I believe I told it to keep the current file. Here's the contents of
> my mythtv.cnf file as it is today:
>
> [mysqld]
> bind-address=0.0.0.0
> max_connections=100
>
> The install then continued as normal and finished. Now the fun begins :-)
>
> I tried to run the frontend (on the same system) and a little message
> at the bottom of the screen (gnome) kept popping up saying that the
> frontend was restarting. This popped up every few seconds, so it was
> in some sort of loop.
>
> I rebooted and still had the same problem.
>
> If I try to go to the backand setup, I get asked if I would like to
> start the mythtv backend, which implys that the back end isn't even
> running any more. I click on 'yes' and am then asked if I would like
> to run mythfilldatabase. I click 'yes' again. At no point am I taken
> into the backend setup screens.
>
> If I try to go into the backend setup again, I get asked if I want to
> run mythtv backend again etc etc.
>
> I've just had a look at /var/log/mythtv/mythbackend.log and it doesn't
> seem to have had an entry since 3rd May. The
> /var/log/mythtv/mythfrontend.log file hasn't had an entry since the
> 2nd May.
>
> Where can I look for some information that could help to fix this?
>
> Thanks
> Damian
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
Hi,

you can check if the backend is runnig by issuing the following in a
terminal:
ps auxw | grep mythbackend
it should output something like this:
root [at] mytht:~# ps auxw | grep mythbackend
mythtv 1065 7.9 2.7 422412 57036 ? Ssl 21:23 3:35
/usr/bin/mythbackend --logfile /var/log/mythtv/mythbackend.log --user mythtv
root 2571 0.0 0.0 4012 756 pts/0 S+ 22:09 0:00 grep
--color=auto mythbackend

If you only get the line saying grep ... its not running, you could then
try to start it manually by running
sudo service mythbackend restart
or you could start it by hand in verbose mode by running:
mythbackend -v
and post the output here.
You could also run mythtv-setup in a shell and check the output.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


keemllib at gmail

May 7, 2012, 1:20 PM

Post #3 of 24 (3371 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 05/07/2012 02:42 PM, Damian wrote:
...

Hi;

> I believe I told it to keep the current file. Here's the contents of my mythtv.cnf file as it is today:
>
> [mysqld]
> bind-address=0.0.0.0
> max_connections=100

/etc/mysql/conf.d/mythtv.cnf has the same bind-address in my (working 0.26-pre) system.
...
> I've just had a look at /var/log/mythtv/mythbackend.log and it doesn't seem to have had an entry since 3rd May.

Look in /etc/init for files that look MythTV related. That will tell you where
the logs are being kept. If you see --syslog blah, then look in /var/log/syslog.
If you see --logpath /whatever, look in that directory. myth{front|backend}.log
are no longer used.

These may be of help:
http://www.mythtv.org/wiki/Release_Notes_-_0.25#Special_Notices_.26_Instructions and
http://www.mythtv.org/wiki/Logging may be on interest to you.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 8, 2012, 11:48 AM

Post #4 of 24 (3353 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 07/05/2012 21:15, jakommo wrote:
> On 05/07/2012 09:42 PM, Damian wrote:
>> Hello all,
>>
>> Well, sometimes it goes smoothly, sometimes not. A few days ago, I
>> switched over my Ubuntu install of mythtv (Mythbuntu on top of an
>> Ubuntu setup) from the 0,24 repositories to the 0.25 repositories.
>> After running the Update Manager, it suggested that I do a 'partial
>> upgrade'.
>>
>> Most of the update went without a hitch, except for upgrading the
>> mythtv.cnf file. I got a message asking me if I wanted to keep the
>> current file or accept the changes. I've been stung by this sort of
>> thing before, so I cut and pasted the differences. Here's what was
>> displayed during the install:
>>
>> --- /etc/mysql/conf.d/mythtv.cnf 2012-04-18 20:27:49.000000000 +0100
>> +++ /etc/mysql/conf.d/mythtv.cnf.dpkg-new 2012-05-03
>> 00:07:41.000000000 +0100
>> @@ -1,2 +1,3 @@
>> [mysqld]
>> -bind-address=0.0.0.0
>> +#bind-address=0.0.0.0
>> +max_connections=100
>>
>> I believe I told it to keep the current file. Here's the contents of
>> my mythtv.cnf file as it is today:
>>
>> [mysqld]
>> bind-address=0.0.0.0
>> max_connections=100
>>
>> The install then continued as normal and finished. Now the fun begins
>> :-)
>>
>> I tried to run the frontend (on the same system) and a little message
>> at the bottom of the screen (gnome) kept popping up saying that the
>> frontend was restarting. This popped up every few seconds, so it was
>> in some sort of loop.
>>
>> I rebooted and still had the same problem.
>>
>> If I try to go to the backand setup, I get asked if I would like to
>> start the mythtv backend, which implys that the back end isn't even
>> running any more. I click on 'yes' and am then asked if I would like
>> to run mythfilldatabase. I click 'yes' again. At no point am I taken
>> into the backend setup screens.
>>
>> If I try to go into the backend setup again, I get asked if I want to
>> run mythtv backend again etc etc.
>>
>> I've just had a look at /var/log/mythtv/mythbackend.log and it
>> doesn't seem to have had an entry since 3rd May. The
>> /var/log/mythtv/mythfrontend.log file hasn't had an entry since the
>> 2nd May.
>>
>> Where can I look for some information that could help to fix this?
>>
>> Thanks
>> Damian
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users [at] mythtv
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
> Hi,
Hi Jakommo, thanks for taking a look at this for me.
>
> you can check if the backend is runnig by issuing the following in a
> terminal:
> ps auxw | grep mythbackend
> it should output something like this:
> root [at] mytht:~# ps auxw | grep mythbackend
> mythtv 1065 7.9 2.7 422412 57036 ? Ssl 21:23 3:35
> /usr/bin/mythbackend --logfile /var/log/mythtv/mythbackend.log --user
> mythtv
> root 2571 0.0 0.0 4012 756 pts/0 S+ 22:09 0:00 grep
> --color=auto mythbackend
"ps auxw | grep mythbackend" returns ...
damian 17525 0.0 0.0 12052 868 pts/1 S+ 19:39 0:00 grep
mythbackend

>
> If you only get the line saying grep ... its not running, you could
> then try to start it manually by running
> sudo service mythbackend restart
"sudo service mythbackend restart" returns ...
mythbackend: unrecognized service

> or you could start it by hand in verbose mode by running:
> mythbackend -v
> and post the output here.
"mythbackend -v" returns ...
mythbackend: symbol lookup error: /usr/lib/libva-x11.so.1: undefined
symbol: fool_postp

> You could also run mythtv-setup in a shell and check the output.
"mythtv-setup" asks me if I want to run mythbackend. I click "Yes" and
it returns ...
mythtv-backend start/running, process 17561
Then asks if I want to run mythfilldatabase.

After that, "ps auxw | grep mythbackend" still returns ..
damian 17584 0.0 0.0 12052 872 pts/1 S+ 19:44 0:00 grep
mythbackend

Any idea what I can try next?
Damian

*Damian Surr* /Magician/

www.magic-weddings.com
<http://www.magic-weddings.com/>|www.gingermagic.com
<http://www.gingermagic.com/>

www.christmaspartymagician.co.uk
<http://www.christmaspartymagician.co.uk> |Tel: 07712 575701

Facebook <http://www.facebook.com/gingermagic> Twitter
<http://twitter.com/damiansurr>
Attachments: facebook.png (0.52 KB)
  twitter.png (1.49 KB)
  pixel.png (90 B)


myth at surr

May 8, 2012, 11:56 AM

Post #5 of 24 (3357 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 07/05/2012 21:20, Bill Meek wrote:
> On 05/07/2012 02:42 PM, Damian wrote:
> ...
>
> Hi;
>
>> I believe I told it to keep the current file. Here's the contents of
>> my mythtv.cnf file as it is today:
>>
>> [mysqld]
>> bind-address=0.0.0.0
>> max_connections=100
>
> /etc/mysql/conf.d/mythtv.cnf has the same bind-address in my (working
> 0.26-pre) system.
> ...
>> I've just had a look at /var/log/mythtv/mythbackend.log and it
>> doesn't seem to have had an entry since 3rd May.
>
> Look in /etc/init for files that look MythTV related. That will tell
> you where
> the logs are being kept. If you see --syslog blah, then look in
> /var/log/syslog.
> If you see --logpath /whatever, look in that directory.
> myth{front|backend}.log
> are no longer used.
>
> These may be of help:
> http://www.mythtv.org/wiki/Release_Notes_-_0.25#Special_Notices_.26_Instructions
> and
> http://www.mythtv.org/wiki/Logging may be on interest to you.
>
Hi Bill,

The contents of /etc/init/mythtv-backend.conf has this line:
LANG=$LANG /usr/bin/mythbackend --syslog local7 --user mythtv
Which from your last message seems to indicate that the logs are now
kept in /var/log/syslog.

There's quite a lot of stuff in there. Should I post the whole contents
here, or just a section? What am I looking for?

Thanks
Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


keemllib at gmail

May 8, 2012, 12:56 PM

Post #6 of 24 (3346 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

>Damian wrote:
>The contents of /etc/init/mythtv-backend.conf has this line:
>LANG=$LANG /usr/bin/mythbackend --syslog local7 --user mythtv
>Which from your last message seems to indicate that the logs are now kept in /var/log/syslog.
>
>There's quite a lot of stuff in there. Should I post the whole contents here, or just a section? What am I looking for?

Hi;

Replying to this message because I couldn't "reply-to-list" on the above.

I'd suggest typing: grep mythbackend /var/log/syslog and pasting the output
of the most recent run to the pastebin of your choice. Or, if you don't
have one, pastebin.ca. Then post the link to your paste here. Be sure to
use reply-to-list to keep your response in the same thread.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 8, 2012, 2:49 PM

Post #7 of 24 (3343 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 08/05/2012 20:56, Bill Meek wrote:
> >Damian wrote:
> >The contents of /etc/init/mythtv-backend.conf has this line:
> >LANG=$LANG /usr/bin/mythbackend --syslog local7 --user mythtv
> >Which from your last message seems to indicate that the logs are now
> kept in /var/log/syslog.
> >
> >There's quite a lot of stuff in there. Should I post the whole
> contents here, or just a section? What am I looking for?
>
> Hi;
>
> I'd suggest typing: grep mythbackend /var/log/syslog and pasting the
> output
> of the most recent run to the pastebin of your choice. Or, if you don't
> have one, pastebin.ca. Then post the link to your paste here.

Hi Bill,

"grep mythbackend /var/log/syslog" returns nothing !?!

Where do I go from there?

Thanks again for helping
Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 8, 2012, 2:56 PM

Post #8 of 24 (3381 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 08/05/2012 22:15, jakommo wrote:
> Hi Damian,
>
>> "sudo service mythbackend restart" returns ...
>> mythbackend: unrecognized service
> oh sorry, typo. The init script is called mythtv-backend while the
> process is called mythbackend.
>
>> "mythbackend -v" returns ...
>> mythbackend: symbol lookup error: /usr/lib/libva-x11.so.1: undefined
>> symbol: fool_postp
> It seems your libva1 package is broken. You can try to remove and
> reinstall libva1 package by running
> sudo apt-get remove libva1
> sudo apt-get install libva1
> and then try again to run mythbackend -v
>

Hi Jakommo,

Thanks for staying with me!

It didn't seem to want to uninstall. Here's the output of it all ...

damian [at] MythBo:~$ sudo apt-get remove libva1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
libavcodec53 : Depends: libva1 (> 1.0.12~) but it is not going to be
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by he ld packages.


damian [at] MythBo:~$ sudo apt-get install libva1
Reading package lists... Done
Building dependency tree
Reading state information... Done
libva1 is already the newest version.
libva1 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.


damian [at] MythBo:~$ mythbackend -v
mythbackend: symbol lookup error: /usr/lib/libva-x11.so.1: undefined
symbol: fool_postp
damian [at] MythBo:~$

Any ideas?
Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


jmorris at beau

May 8, 2012, 3:05 PM

Post #9 of 24 (3343 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On Tue, 2012-05-08 at 22:49 +0100, Damian wrote:

> "grep mythbackend /var/log/syslog" returns nothing !?!
>
> Where do I go from there?

Look for /var/log/mythtv/mythbackend.log or something similar.
Attachments: signature.asc (0.19 KB)


jakommo at gmail

May 8, 2012, 3:23 PM

Post #10 of 24 (3352 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

> 0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.
you could try to run
sudo apt-get upgrade or apt-get dist-upgrade
to get the 43 upgrades installed, maybe this helps.
Also, do you have (or had) any ppa installed? You can check it with
ls /etc/apt/sources.list.d/
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


John.Veness.mythtv at pelago

May 9, 2012, 3:12 AM

Post #11 of 24 (3336 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 07/05/2012 20:42, Damian wrote:
> Well, sometimes it goes smoothly, sometimes not. A few days ago, I
> switched over my Ubuntu install of mythtv (Mythbuntu on top of an Ubuntu
> setup) from the 0,24 repositories to the 0.25 repositories. After
> running the Update Manager, it suggested that I do a 'partial upgrade'.

I think at least part of your problems may have been caused by the
partial upgrade. I believe when you use the Mythbuntu repos to upgrade a
whole MythTV version (e.g. 0.24 to 0.25) you need to do a full upgrade,
e.g. "sudo apt-get dist-upgrade". Or use Synaptic instead of Update
Manager to do the upgrade.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 10, 2012, 12:21 PM

Post #12 of 24 (3321 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 10/05/2012 04:49, Bill Meek wrote:
> On 05/08/2012 04:49 PM, Damian wrote:
> ...
>>
>> "grep mythbackend /var/log/syslog" returns nothing !?!
>>
>> Where do I go from there?
>
> Hey Damian;
>
> If not in syslog, then syslog.1 etc.
>
> However, it looks like there was another message that mentioned
> a partial upgrade. I agree, that's something to get resolved 1st.
> I can't duplicate that (and wouldn't dream of trying:)) If
> memory serves, I had that problem years ago and when I ran the
> update-manager, it came up with a warning box with a way to
> fix the problem.
>

It goes from bad to worse !

My machine seems to have completely died. I think it must be the power
supply and assume (?) that this has nothing to do with the problem I was
having.

Yesterday, following feedback from here, I decided to run all of the
updates so that I wasn't in the state of a 'partial update'. I updated
to Ubuntu 12.04 and made a note of all of the files that the update
wanted me to keep or replace. Here's the 'diff' info for those files:

http://pastebin.com/NBztMBdW (mythtv.cnf)

this change above was to mythtv.cnf during the initial 'partial' update.
All of the rest of the updates were from yesterdays 'full' update to 12.04

http://pastebin.com/6ydZ55xm (my.cnf)
http://pastebin.com/0rJfGd30 (crontab)
http://pastebin.com/C0nvSVfj (release-upgrades)
http://pastebin.com/Ybg6nNxd (menu.lst)
http://pastebin.com/HX2kyjvQ (usr.sbin.mysqld)
http://pastebin.com/UA3NQab1 (php.ini)

For all of the changes from yesterday, I opted to 'replace' the file
with the file from the update repositories, which is why I saved all of
the 'diff' files (even though I don't really understand them!).

With the initial file (mythtv.cnf) from the partial upgrade a few days
ago, I can't remember whether I kept the old file or took the new one.

The machine (which is effectively the house server and media centre) has
been on all day today. However, not only is MythTV still broken after
the 'full update', but I noticed that my Music boxes (SliMP3 and
Squeezeboxes) were no longer connecting to the server. I assume that
this is something to do with the changes that were made during the big
update yesterday. Can anyone advise me on what I need to put back the
way it was from looking at those 'diff' files?

I got home this evening with 'sorting Myth' top of my list. About 10
minutes after I got it, my Uninterruptable Power Supply started beeping.
There was no power cut, so I was confused by this. I have since tried
plugging the machine directly into main power and nothing at all happens
... silence!

My guess is that the Power Supply in the computer has died and needs
replacing. Do Uninterruptable Power Supplies beep if suddenly the thing
that is drawing power from them stops draining power? Is there any way
for me to check if it's the PSU before I spend money on a replacement?

I'm fairly convinced that the two events are a complete coincidence, but
I'm more than happy for anyone to enlighten me if they think differently.

This was all completely failing 'the wife test' before tonight's
additional complication! Hope to be back on track soon!!

Any tips GREATLY appreciated!
Thanks
Damian

PS I have just noticed that there are some comments from me within those
'diff' files. I must have made them based on previous changes/fixes,
probably based on information from this group. I don't understand any of
them myself, so tips on what to put back in place would be very
appreciated!!
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


greg12866 at nycap

May 10, 2012, 1:00 PM

Post #13 of 24 (3318 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 05/10/2012 03:21 PM, Damian wrote:
> On 10/05/2012 04:49, Bill Meek wrote:
>> On 05/08/2012 04:49 PM, Damian wrote:
>> ...
>>>
>>> "grep mythbackend /var/log/syslog" returns nothing !?!
>>>
>>> Where do I go from there?
>>
>> Hey Damian;
>>
>> If not in syslog, then syslog.1 etc.
>>
>> However, it looks like there was another message that mentioned
>> a partial upgrade. I agree, that's something to get resolved 1st.
>> I can't duplicate that (and wouldn't dream of trying:)) If
>> memory serves, I had that problem years ago and when I ran the
>> update-manager, it came up with a warning box with a way to
>> fix the problem.
>>
>
> It goes from bad to worse !
>
> My machine seems to have completely died. I think it must be the power
> supply and assume (?) that this has nothing to do with the problem I was
> having.
>
> Yesterday, following feedback from here, I decided to run all of the
> updates so that I wasn't in the state of a 'partial update'. I updated
> to Ubuntu 12.04 and made a note of all of the files that the update
> wanted me to keep or replace. Here's the 'diff' info for those files:
>
> http://pastebin.com/NBztMBdW (mythtv.cnf)
>
> this change above was to mythtv.cnf during the initial 'partial' update.
> All of the rest of the updates were from yesterdays 'full' update to 12.04
>
> http://pastebin.com/6ydZ55xm (my.cnf)
> http://pastebin.com/0rJfGd30 (crontab)
> http://pastebin.com/C0nvSVfj (release-upgrades)
> http://pastebin.com/Ybg6nNxd (menu.lst)
> http://pastebin.com/HX2kyjvQ (usr.sbin.mysqld)
> http://pastebin.com/UA3NQab1 (php.ini)
>
> For all of the changes from yesterday, I opted to 'replace' the file
> with the file from the update repositories, which is why I saved all of
> the 'diff' files (even though I don't really understand them!).
>
> With the initial file (mythtv.cnf) from the partial upgrade a few days
> ago, I can't remember whether I kept the old file or took the new one.
>
> The machine (which is effectively the house server and media centre) has
> been on all day today. However, not only is MythTV still broken after
> the 'full update', but I noticed that my Music boxes (SliMP3 and
> Squeezeboxes) were no longer connecting to the server. I assume that
> this is something to do with the changes that were made during the big
> update yesterday. Can anyone advise me on what I need to put back the
> way it was from looking at those 'diff' files?
>
> I got home this evening with 'sorting Myth' top of my list. About 10
> minutes after I got it, my Uninterruptable Power Supply started beeping.
> There was no power cut, so I was confused by this. I have since tried
> plugging the machine directly into main power and nothing at all happens
> ... silence!
>
> My guess is that the Power Supply in the computer has died and needs
> replacing. Do Uninterruptable Power Supplies beep if suddenly the thing
> that is drawing power from them stops draining power? Is there any way
> for me to check if it's the PSU before I spend money on a replacement?
>
> I'm fairly convinced that the two events are a complete coincidence, but
> I'm more than happy for anyone to enlighten me if they think differently.
>
> This was all completely failing 'the wife test' before tonight's
> additional complication! Hope to be back on track soon!!
>
> Any tips GREATLY appreciated!
> Thanks
> Damian
>
> PS I have just noticed that there are some comments from me within those
> 'diff' files. I must have made them based on previous changes/fixes,
> probably based on information from this group. I don't understand any of
> them myself, so tips on what to put back in place would be very
> appreciated!!
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
Most modern motherboards will have an led on the board that will light
up when power is supplied, pull the cover and look.. Check and make sure
that you or someone else in the home didn't shut off the switch on the
Power supply.. The only real way to check it is with an multi-meter or a
power supply tester...The next best way is to substitute a know good
supply with the suspected bad one.... Other than pulling the cover and
looking,I wouldn't suggest you do any of the other tests if you don't
have the proper tools or skill...
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 10, 2012, 1:09 PM

Post #14 of 24 (3312 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 10/05/2012 21:00, Greg wrote:
> On 05/10/2012 03:21 PM, Damian wrote:
>> On 10/05/2012 04:49, Bill Meek wrote:
>>> On 05/08/2012 04:49 PM, Damian wrote:
>>> ...
>>>>
>>>> "grep mythbackend /var/log/syslog" returns nothing !?!
>>>>
>>>> Where do I go from there?
>>>
>>> Hey Damian;
>>>
>>> If not in syslog, then syslog.1 etc.
>>>
>>> However, it looks like there was another message that mentioned
>>> a partial upgrade. I agree, that's something to get resolved 1st.
>>> I can't duplicate that (and wouldn't dream of trying:)) If
>>> memory serves, I had that problem years ago and when I ran the
>>> update-manager, it came up with a warning box with a way to
>>> fix the problem.
>>>
>>
>> It goes from bad to worse !
>>
>> My machine seems to have completely died. I think it must be the power
>> supply and assume (?) that this has nothing to do with the problem I was
>> having.
>>
>> Yesterday, following feedback from here, I decided to run all of the
>> updates so that I wasn't in the state of a 'partial update'. I updated
>> to Ubuntu 12.04 and made a note of all of the files that the update
>> wanted me to keep or replace. Here's the 'diff' info for those files:
>>
>> http://pastebin.com/NBztMBdW (mythtv.cnf)
>>
>> this change above was to mythtv.cnf during the initial 'partial' update.
>> All of the rest of the updates were from yesterdays 'full' update to
>> 12.04
>>
>> http://pastebin.com/6ydZ55xm (my.cnf)
>> http://pastebin.com/0rJfGd30 (crontab)
>> http://pastebin.com/C0nvSVfj (release-upgrades)
>> http://pastebin.com/Ybg6nNxd (menu.lst)
>> http://pastebin.com/HX2kyjvQ (usr.sbin.mysqld)
>> http://pastebin.com/UA3NQab1 (php.ini)
>>
>> For all of the changes from yesterday, I opted to 'replace' the file
>> with the file from the update repositories, which is why I saved all of
>> the 'diff' files (even though I don't really understand them!).
>>
>> With the initial file (mythtv.cnf) from the partial upgrade a few days
>> ago, I can't remember whether I kept the old file or took the new one.
>>
>> The machine (which is effectively the house server and media centre) has
>> been on all day today. However, not only is MythTV still broken after
>> the 'full update', but I noticed that my Music boxes (SliMP3 and
>> Squeezeboxes) were no longer connecting to the server. I assume that
>> this is something to do with the changes that were made during the big
>> update yesterday. Can anyone advise me on what I need to put back the
>> way it was from looking at those 'diff' files?
>>
>> I got home this evening with 'sorting Myth' top of my list. About 10
>> minutes after I got it, my Uninterruptable Power Supply started beeping.
>> There was no power cut, so I was confused by this. I have since tried
>> plugging the machine directly into main power and nothing at all happens
>> ... silence!
>>
>> My guess is that the Power Supply in the computer has died and needs
>> replacing. Do Uninterruptable Power Supplies beep if suddenly the thing
>> that is drawing power from them stops draining power? Is there any way
>> for me to check if it's the PSU before I spend money on a replacement?
>>
>> I'm fairly convinced that the two events are a complete coincidence, but
>> I'm more than happy for anyone to enlighten me if they think differently.
>>
>> This was all completely failing 'the wife test' before tonight's
>> additional complication! Hope to be back on track soon!!
>>
>> Any tips GREATLY appreciated!
>> Thanks
>> Damian
>>
>> PS I have just noticed that there are some comments from me within those
>> 'diff' files. I must have made them based on previous changes/fixes,
>> probably based on information from this group. I don't understand any of
>> them myself, so tips on what to put back in place would be very
>> appreciated!!
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users [at] mythtv
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
> Most modern motherboards will have an led on the board that will light
> up when power is supplied, pull the cover and look.. Check and make sure
> that you or someone else in the home didn't shut off the switch on the
> Power supply.. The only real way to check it is with an multi-meter or a
> power supply tester...The next best way is to substitute a know good
> supply with the suspected bad one.... Other than pulling the cover and
> looking,I wouldn't suggest you do any of the other tests if you don't
> have the proper tools or skill...

Hi Greg,

I'm comfortable with getting my hands dirty. I've build machines from
scratch several times and used to consider myself a 'geek' when I just
used Windows machines.

Linux makes me feel like a newbie, even though I've been running Ubuntu
and MythTV for years. I never seem to have a clue when something goes
wrong (that never happens to me in windows), but that's software.
Machines are still machines so I'm happy to operate on the PSU.

I'll check for the light.

Switches have all been checked and tried plugging into a different
socket with a different lead.

Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


Jim at Morton

May 10, 2012, 1:16 PM

Post #15 of 24 (3308 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 5/10/2012 3:21 PM, Damian wrote:
> It goes from bad to worse !
>
> About 10 minutes after I got it, my Uninterruptable Power Supply
> started beeping. There was no power cut, so I was confused by this. I
> have since tried plugging the machine directly into main power and
> nothing at all happens ... silence!

Plug a lamp or something in to test that outlet. If the UPS was beeping
it probably lost power. I've never heard of one beeping due to any
problem on the downline side.

--
_________________________________________________________

Jim Morton

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 10, 2012, 1:27 PM

Post #16 of 24 (3305 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 10/05/2012 21:16, Jim Morton wrote:
> On 5/10/2012 3:21 PM, Damian wrote:
>> It goes from bad to worse !
>>
>> About 10 minutes after I got it, my Uninterruptable Power Supply
>> started beeping. There was no power cut, so I was confused by this. I
>> have since tried plugging the machine directly into main power and
>> nothing at all happens ... silence!
>
> Plug a lamp or something in to test that outlet. If the UPS was
> beeping it probably lost power. I've never heard of one beeping due to
> any problem on the downline side.
>
The UPS was plugged into a multi socket adaptor. The lights to the
adaptor were still on, and everything else plugged into it was working
fine. That only leaves the power cord to the UPS, but I find it hard to
believe that would fail. I'll test it though.

Cheers
Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


keemllib at gmail

May 10, 2012, 1:39 PM

Post #17 of 24 (3306 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 05/10/2012 03:09 PM, Damian wrote:
...
>>> http://pastebin.com/HX2kyjvQ (usr.sbin.mysqld)
...
>>> ... but I noticed that my Music boxes (SliMP3 and
>>> Squeezeboxes) were no longer connecting to the server.
...
It appears that the Squeezebox entries in the pastebin above were deleted
(if I'm reading the diffs correctly.) I don't use that software, but if
they're not there, put them back. The entries in question start at line 43.

Perhaps, even better, see the last 2 lines and create the local/usr.sbin.mysql
file with the Squeezebox entries. Then next time you upgrade you won't
have this problem.

Then restart apparmor and mysqld, or better yet, just reboot.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


John.Veness.mythtv at pelago

May 11, 2012, 2:43 AM

Post #18 of 24 (3284 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 10/05/2012 20:21, Damian wrote:
> my Uninterruptable Power Supply started beeping.
> There was no power cut, so I was confused by this. I have since tried
> plugging the machine directly into main power and nothing at all happens
> ... silence!
>
> My guess is that the Power Supply in the computer has died and needs
> replacing. Do Uninterruptable Power Supplies beep if suddenly the thing
> that is drawing power from them stops draining power?

I've never heard of a UPS beeping because the thing that is drawing
power from them stops drawing power. A UPS would normally beep if it
loses mains power, or if the battery failed a self-test. It would depend
on exactly which model UPS you have.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


michael at thewatsonfamily

May 11, 2012, 8:02 AM

Post #19 of 24 (3275 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 11/05/2012 7:43 PM, John Veness wrote:
> On 10/05/2012 20:21, Damian wrote:
>> my Uninterruptable Power Supply started beeping.
>> There was no power cut, so I was confused by this. I have since tried
>> plugging the machine directly into main power and nothing at all happens
>> ... silence!
>>
>> My guess is that the Power Supply in the computer has died and needs
>> replacing. Do Uninterruptable Power Supplies beep if suddenly the thing
>> that is drawing power from them stops draining power?
>
> I've never heard of a UPS beeping because the thing that is drawing
> power from them stops drawing power. A UPS would normally beep if it
> loses mains power, or if the battery failed a self-test. It would
> depend on exactly which model UPS you have.
Some will beep if there is a short circuit, or overload, or earth
leakage problem.
>
> Cheers,
>
> John
>

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


zarthan at gmail

May 11, 2012, 8:23 AM

Post #20 of 24 (3272 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On Fri, May 11, 2012 at 10:02 AM, Michael Watson <
michael [at] thewatsonfamily> wrote:

> On 11/05/2012 7:43 PM, John Veness wrote:
>
>> On 10/05/2012 20:21, Damian wrote:
>>
>>> my Uninterruptable Power Supply started beeping.
>>> There was no power cut, so I was confused by this. I have since tried
>>> plugging the machine directly into main power and nothing at all happens
>>> ... silence!
>>>
>>> My guess is that the Power Supply in the computer has died and needs
>>> replacing. Do Uninterruptable Power Supplies beep if suddenly the thing
>>> that is drawing power from them stops draining power?
>>>
>>
>> I've never heard of a UPS beeping because the thing that is drawing power
>> from them stops drawing power. A UPS would normally beep if it loses mains
>> power, or if the battery failed a self-test. It would depend on exactly
>> which model UPS you have.
>>
> Some will beep if there is a short circuit, or overload, or earth leakage
> problem.
>
>>
>> And some beep when the battery is close to needing replacement.


watkinshome at gmail

May 11, 2012, 8:47 AM

Post #21 of 24 (3276 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

> My guess is that the Power Supply in the computer has died and needs
> replacing. Do Uninterruptable Power Supplies beep if suddenly the thing that
> is drawing power from them stops draining power? Is there any way for me to
> check if it's the PSU before I spend money on a replacement?

One plausible scenario is that as your computer PSU died it
momentarily draw a large enough current to trigger an overload warning
on the UPS. If that situation still existed when you plugged the PC
into the wall then it would have blown a fuse somewhere, possibly
inside the PSU if you're not using a fused plug.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 14, 2012, 4:15 AM

Post #22 of 24 (3173 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 10/05/2012 21:39, Bill Meek wrote:
> On 05/10/2012 03:09 PM, Damian wrote:
> ...
>>>> http://pastebin.com/HX2kyjvQ (usr.sbin.mysqld)
> ...
>>>> ... but I noticed that my Music boxes (SliMP3 and
>>>> Squeezeboxes) were no longer connecting to the server.
> ...
> It appears that the Squeezebox entries in the pastebin above were deleted
> (if I'm reading the diffs correctly.) I don't use that software, but if
> they're not there, put them back. The entries in question start at
> line 43.
>
> Perhaps, even better, see the last 2 lines and create the
> local/usr.sbin.mysql
> file with the Squeezebox entries. Then next time you upgrade you won't
> have this problem.
>
> Then restart apparmor and mysqld, or better yet, just reboot.
>
Thanks Bill,

I'll take a look at that once the new Power Supply arrives.

Damian

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 14, 2012, 4:18 AM

Post #23 of 24 (3178 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 11/05/2012 16:47, David Watkins wrote:
>> My guess is that the Power Supply in the computer has died and needs
>> replacing. Do Uninterruptable Power Supplies beep if suddenly the thing that
>> is drawing power from them stops draining power? Is there any way for me to
>> check if it's the PSU before I spend money on a replacement?
>
> One plausible scenario is that as your computer PSU died it
> momentarily draw a large enough current to trigger an overload warning
> on the UPS. If that situation still existed when you plugged the PC
> into the wall then it would have blown a fuse somewhere, possibly
> inside the PSU if you're not using a fused plug.

All I know is that the beeping from the UPS started, and to the best of
my deductive reasoning, the computer's PSU has died.

I've ordered a new one and will see if the machine comes back to life.

Then I can get back on with fixing Myth.

Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


myth at surr

May 15, 2012, 9:19 AM

Post #24 of 24 (3150 views)
Permalink
Re: Problem with Ubuntu upgrade 0.24 to 0.25 [In reply to]

On 10/05/2012 21:39, Bill Meek wrote:
> On 05/10/2012 03:09 PM, Damian wrote:
> ...
>>>> http://pastebin.com/HX2kyjvQ (usr.sbin.mysqld)
> ...
>>>> ... but I noticed that my Music boxes (SliMP3 and
>>>> Squeezeboxes) were no longer connecting to the server.
> ...
> It appears that the Squeezebox entries in the pastebin above were deleted
> (if I'm reading the diffs correctly.) I don't use that software, but if
> they're not there, put them back. The entries in question start at
> line 43.
>
> Perhaps, even better, see the last 2 lines and create the
> local/usr.sbin.mysql
> file with the Squeezebox entries. Then next time you upgrade you won't
> have this problem.
>
> Then restart apparmor and mysqld, or better yet, just reboot.
>

Right, I'm FINALLY back on track!!

New power supply is in place and the system is breathing again. The UPS
is still making funny beeping noises if I plug it in (maybe it was part
of what broke the internal PSU), so I'm just plugged into the standard
wall socket. That'll do for now.

Bill, I replaced those Squeezeboz entries into usr.sbin.mysqld, but my
Music boxes (SliMP3 and
Squeezeboxes) are still not connecting to the server.

That's maybe for another time though. It's MythTV I need to get back
into shape first before the family go mad!

What's shall I do first to get to the bottom of all of this? I now have
0.25 of Myhthbuntu running on Ubuntu 12.04, which is also running Gnome
of that's of any use.

What commands should I run and how can I give you all what you need from
the logs (which may have moved since the latest update).

Thanks for your patience,
Damian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.