Mailing List Archive: Muthbuntu baffling issue - backend on wrong port somehow

Muthbuntu baffling issue - backend on wrong port somehow

Sep 20, 2007, 7:19 PM

Post #1 of 4 (2666 views)

I recently upgraded my working mythbuntu generic Alpha 4 install to
the mythbuntu weekly trunk builds, and after upgrading I'm having a
baffling issue with the master backend.

It is set up for ports 6543 and 6544 (defaults) through mythtv-setup/
General. However, when the backend is run, it shows up on ports 6544
(the status port) and 6549 (the MB port).

netstat -nlp | grep 654
tcp 0 0 0.0.0.0:6544 0.0.0.0:*
LISTEN 16697/mythbackend
udp 0 0 0.0.0.0:6549
0.0.0.0:* 16697/mythbackend

If I change the database to reflect other ports (6544 port, 6549
status ) and restart the backend:

# netstat -nlp | grep 654
tcp 0 0 0.0.0.0:6549 0.0.0.0:*
LISTEN 17192/mythbackend
udp 0 0 0.0.0.0:6549
0.0.0.0:* 17192/mythbackend

Of course no frontend or mythweb will run because it can't connect to
the backend port, but the backend seems to be recording shows just
fine according to the log.

Currently 1 master backend dedicated box, and an addtional frontend box.

I've uninstalled myth and re-installed it to make sure everything was
up to date. Same issues, but the database was not changed.

Versions installed:
Mythbuntu Alpha 4
Linux 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64
GNU/Linux

mythtv-transcode-utils/feisty uptodate 0.20.99
+trunk14489-0ubuntu0~mythbuntu2
mythtv-database/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
mythtv-backend/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
libmyth-0.20/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
mythtv-backend-master/feisty uptodate 0.20.99
+trunk14489-0ubuntu0~mythbuntu2
mythweb/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
mythtv-common/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2

Joel

Re: Muthbuntu baffling issue - backend on wrong port somehow [ In reply to ]

mikemacleod at gmail

Sep 21, 2007, 5:17 AM

Post #2 of 4 (2574 views)

Permalink

I upgraded from the weekly -fixes builds to the trunk builds, and I too ran
into port related issues. Mine were easily solved by re-running
mythtv-setup, but it certainly appears that the default ports have changed
in the trunk builds.

The bigger problem I've run into is that on my frontend system
ubuntu-mythtv-frontend wont install properly. apt-get install
ubuntu-mythtv-frontend will install it, but if I apt-get upgrade after that,
it's listed as needing to be updated. Clearly this weeks builds are not
stable or even usable.

On 9/20/07, Joel Jameson <karib@spamcop.net> wrote:
>
> I recently upgraded my working mythbuntu generic Alpha 4 install to the
> mythbuntu weekly trunk builds, and after upgrading I'm having a baffling
> issue with the master backend.
> It is set up for ports 6543 and 6544 (defaults) through
> mythtv-setup/General. However, when the backend is run, it shows up on ports
> 6544 (the status port) and 6549 (the MB port).
>
> netstat -nlp | grep 654
> tcp 0 0 0.0.0.0:6544 0.0.0.0:* LISTEN
> 16697/mythbackend
> udp 0 0 0.0.0.0:6549 0.0.0.0:*
> 16697/mythbackend
>
> If I change the database to reflect other ports (6544 port, 6549 status )
> and restart the backend:
>
> # netstat -nlp | grep 654
> tcp 0 0 0.0.0.0:6549 0.0.0.0:* LISTEN
> 17192/mythbackend
> udp 0 0 0.0.0.0:6549 0.0.0.0:*
> 17192/mythbackend
>
>
> Of course no frontend or mythweb will run because it can't connect to the
> backend port, but the backend seems to be recording shows just fine
> according to the log.
>
> Currently 1 master backend dedicated box, and an addtional frontend box.
>
> I've uninstalled myth and re-installed it to make sure everything was up
> to date. Same issues, but the database was not changed.
>
> Versions installed:
> Mythbuntu Alpha 4
> Linux 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64
> GNU/Linux
>
> mythtv-transcode-utils/feisty uptodate
> 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythtv-database/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythtv-backend/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> libmyth-0.20/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythtv-backend-master/feisty uptodate
> 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythweb/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythtv-common/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
>
> Joel
>
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>

Re: Muthbuntu baffling issue - backend on wrong port somehow [ In reply to ]

karib at spamcop

Sep 21, 2007, 12:12 PM

Post #3 of 4 (2595 views)

Permalink

Update:

Upgraded to the new mythbuntu packages today (version was 20.99
+trunk14495), port 6543 was non-existent, just the TCP status port.
So same issues with the new weekly build.

Removed everything related to the trunk builds, and re-installed with
the 20-2 fixes packages from the weekly builds on mythbuntu:

mythtv-transcode-utils/feisty upgradeable from 0.20.2
+fixes14472-0ubuntu0~mythbuntu1 to 0.20.99
+trunk14495-0ubuntu0~mythbuntu2
mythtv-database/feisty upgradeable from 0.20.2
+fixes14472-0ubuntu0~mythbuntu1 to 0.20.99
+trunk14495-0ubuntu0~mythbuntu2
mythtv-backend/feisty upgradeable from 0.20.2
+fixes14472-0ubuntu0~mythbuntu1 to 0.20.99
+trunk14495-0ubuntu0~mythbuntu2
mythtv-backend-master/feisty upgradeable from 0.20.2
+fixes14472-0ubuntu0~mythbuntu1 to 0.20.99
+trunk14495-0ubuntu0~mythbuntu2
mythtv-common/feisty upgradeable from 0.20.2
+fixes14472-0ubuntu0~mythbuntu1 to 0.20.99
+trunk14495-0ubuntu0~mythbuntu2

netstat -lpt | grep myth
tcp 0 0 *:6543 *:*
LISTEN 16098/mythbackend
tcp 0 0 *:6544 *:*
LISTEN 16098/mythbackend

The backend is now correctly working, and I'm able to connect again
with the frontends/mythweb.

Was there any known issue with these 2 particular trunk builds? I
didn't see anything on the commit list.

Joel

On Sep 20, 2007, at 9:19 PM, Joel Jameson wrote:

> I recently upgraded my working mythbuntu generic Alpha 4 install to
> the mythbuntu weekly trunk builds, and after upgrading I'm having a
> baffling issue with the master backend.
>
> It is set up for ports 6543 and 6544 (defaults) through mythtv-
> setup/General. However, when the backend is run, it shows up on
> ports 6544 (the status port) and 6549 (the MB port).
>
> netstat -nlp | grep 654
> tcp 0 0 0.0.0.0:6544 0.0.0.0:*
> LISTEN 16697/mythbackend
> udp 0 0 0.0.0.0:6549
> 0.0.0.0:* 16697/mythbackend
>
> If I change the database to reflect other ports (6544 port, 6549
> status ) and restart the backend:
>
> # netstat -nlp | grep 654
> tcp 0 0 0.0.0.0:6549 0.0.0.0:*
> LISTEN 17192/mythbackend
> udp 0 0 0.0.0.0:6549
> 0.0.0.0:* 17192/mythbackend
>
>
> Of course no frontend or mythweb will run because it can't connect
> to the backend port, but the backend seems to be recording shows
> just fine according to the log.
>
> Currently 1 master backend dedicated box, and an addtional frontend
> box.
>
> I've uninstalled myth and re-installed it to make sure everything
> was up to date. Same issues, but the database was not changed.
>
> Versions installed:
> Mythbuntu Alpha 4
> Linux 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64
> GNU/Linux
>
> mythtv-transcode-utils/feisty uptodate 0.20.99
> +trunk14489-0ubuntu0~mythbuntu2
> mythtv-database/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythtv-backend/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> libmyth-0.20/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythtv-backend-master/feisty uptodate 0.20.99
> +trunk14489-0ubuntu0~mythbuntu2
> mythweb/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
> mythtv-common/feisty uptodate 0.20.99+trunk14489-0ubuntu0~mythbuntu2
>
> Joel
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Joel
karib@spamcop.net

Re: Muthbuntu baffling issue - backend on wrong port somehow [ In reply to ]

mythtv at quakerporn

Oct 1, 2008, 6:10 AM

Post #4 of 4 (2262 views)

Permalink

Hey, folks; responding to an old message from the archives, but one I
haven't found an answer to.

Having been running a hand-compiled 0.21-fixes successfully for some time,
I completely rebuilt my PVR machine so I could install a hardware RAID
card. I figured I'd try out Mythbuntu, in the process.

Having installed it, however, I discovered that the backend was only
listening on tcp/udp port 6549, not the 6543 and 6544 ports specified in
mythtv-setup. When I fired up the frontend, it complained about not being
able to contact the backend.

Before I go to recompile mythtv by hand, I was curious if anyone else had
run into this since the OP, and if so, any pointers. Thanks!

Original message:
http://www.gossamer-threads.com/lists/mythtv/users/291266?search_string=6549;#291266

Adam

--
<Adam Hirsch> Q: Why do we treat those we love so badly?
<adam@baz.org> A: Who else would put up with it?
<http://web.baz.org/~adam/> -- Matt Groening
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users