[mythtv-users] Problem upgrading from 0.25fixes to 0.26

[Peter Foulkes]

Fixed it!

For the benefit of anyone else who has the same problem, here is how I fixed 
it:
I used netstat -lp | grep 6948 (the port number that was being reported as 
already used), to discover what was using that port. Mythfrontend was 
automatically reloading and using the port so I stopped mythfrontend from 
loading and then ran mythbackend-setup.

Problem solved. The schema upgrades and it all works.

Cheers,

Peter


----- Original Message ----- 
From: "Peter Foulkes" <peter.foulkes at nilpanic.co.uk>
To: <mythtv-users at mythtv.org>
Sent: Sunday, January 20, 2013 2:03 PM
Subject: Re: Problem upgrading from 0.25fixes to 0.26


> Subject: Re: [mythtv-users] Problem upgrading from 0.25fixes to 0.26
>
>>On Wed, 2013-01-16 at 11:41 +0000, Peter Foulkes wrote:
>>> When frontend runs I get the message "This version of MythTV requires an
>>> updated database. (schema is 8 versions behind)"
>>> I guess this is to be expected.
>>>
>>> When I run mythbackend-setup it always gets stuck on "Waiting for 
>>> database
>>> schema upgrade lock"
>>>
>>> Looking through the mythtb-setup.log I do come across an error, "Failed
>>> binding to UDP. Error 8. The bound address is already in use"
>>> Could this be the problem?