[mythtv-users] Muthbuntu baffling issue - backend on wrong port somehow

[Joel Jameson]

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 at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Joel
karib at spamcop.net



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070921/ae86f33a/attachment.htm