[mythtv-users] Problem with 0.20 mythbackend not binding to ports

[Tim Stuart]

I am struggling to finish an upgrade from MythTV 0.18 to 0.20 (on gentoo 
2.6.18-r6).  I have most of it working, but the mythbackend doesn't seem 
to bind to it's two designated ports (6543 & 6544). Therefore, 
myth-setup and mythfrontend are not able to communicate to mythbackend.

By looking at a detailed mythbackend.log, I can tell that mythbackend is 
doing work such as successfully connecting to the database and looking 
for expired content, etc.  But no indication of opening sockets to the 
ports, and netstat doesn't show those ports being used.  Mythbackend 
starts and stops OK.  I set verbosity to "all" and ran mythbackend from 
both the init.d script as well as interactively and got the same results.

Questions...
1) I am suspicious about the Qt stuff as I think it contains the socket 
routines that are being used.  I have both Qt 3 & 4 installed, but I 
believe MythTV only uses 3.  Besides when I ran "ldd mythbackend" only 
the Qt3 library appeared.  Should I try removing Qt 4?

2) Any way to get more detailed mythbackend logs beyond verbosity setting?

3) Does mythbackend usually log the successful port binding?  I see the 
fetch from the database for the ports.  Is the binding right after that?

Thanks for any assistance.

-- Tim