mytbackend denies opening ports

[Special K]

when i start mythbackend (mythtv ) i can't connect from any frontend even localhost.

mythbackend does not open any tcp port, ver 0.19 did with no problems.

Code: Select all

# netstat -pan | grep myth
unix  3      [ ]         STREAM     CONNECTED     89429  20428/mythbackend   
unix  3      [ ]         STREAM     CONNECTED     89427  20428/mythbackend   
unix  3      [ ]         STREAM     CONNECTED     89402  20428/mythbackend  

# mythbackend -v important,general,file,network,socket

Code: Select all

2007-04-02 00:10:37.284 Using runtime prefix = /usr
2007-04-02 00:10:37.455 New DB connection, total: 1
2007-04-02 00:10:37.552 Connected to database 'mythconverg' at host: localhost
2007-04-02 00:10:37.566 Current Schema Version: 1160
Starting up as the master server.
2007-04-02 00:10:37.616 New DB connection, total: 2
2007-04-02 00:10:37.618 Connected to database 'mythconverg' at host: localhost
2007-04-02 00:10:37.624 New DB connection, total: 3
2007-04-02 00:10:37.626 Connected to database 'mythconverg' at host: localhost
2007-04-02 00:10:37.637 EITHelper: localtime offset 2:00:00 
2007-04-02 00:10:37.915 EITHelper: localtime offset 2:00:00 
2007-04-02 00:10:37.925 TVRec(3) Error: Start channel invalid, setting to 'dummy' on input MPEG2TS instead.
2007-04-02 00:10:37.926 TVRec(3) Error: DBOX2 card configured on video device , 
but MythTV was not compiled with DBOX2 support. 

i think those dbox2 stuff doesn't matter, cause i'm not using dbox2 any more.

How can I get mythbackend to open tcp ports like 0.19 did?? [/glsa]

[Hobbes-X]

i think those dbox2 stuff doesn't matter, cause i'm not using dbox2 any more.

How can I get mythbackend to open tcp ports like 0.19 did?? [/glsa]

Unless mythbackend dies after the errors- does

Code: Select all

 $ ps aux | grep mythbackend

show it as running?

[Special K]

it is running despite the error:

Code: Select all

# ps aux | grep mythbackend
root     28455  4.7  2.8  50356 13848 pts/2    S+   15:17   0:00 mythbackend -v socket,timestamp,file,general,important
root     28457  0.0  2.8  50356 13848 pts/2    S+   15:17   0:00 mythbackend -v socket,timestamp,file,general,important
root     28458  0.0  2.8  50356 13848 pts/2    S+   15:17   0:00 mythbackend -v socket,timestamp,file,general,important
root     28461  0.0  2.8  50356 13848 pts/2    SN+  15:17   0:00 mythbackend -v socket,timestamp,file,general,important
root     28462  0.0  2.8  50356 13848 pts/2    S+   15:17   0:00 mythbackend -v socket,timestamp,file,general,important
root     28463  0.0  2.8  50356 13848 pts/2    SN+  15:17   0:00 mythbackend -v socket,timestamp,file,general,important
root     28603  0.0  0.0   1500   460 pts/3    S+   15:18   0:00 grep --colour=auto mythbackend

it has open unix sockets but neither tcp ports, although in my configuration i used with 0.19 all tcp stuff was working

[Hobbes-X]

Hmm... I'm stumped. I've never found it necessary to do anything to get it to open the ports.

Everything goes just fine for me, without any hoop-jumping:

Code: Select all

netstat -pan | grep myth
tcp        0      0 0.0.0.0:6543            0.0.0.0:*               LISTEN      9992/mythbackend
tcp        0      0 0.0.0.0:6544            0.0.0.0:*               LISTEN      9992/mythbackend
udp        0      0 0.0.0.0:6549            0.0.0.0:*                           9992/mythbackend
udp        0      0 255.255.255.255:1900    0.0.0.0:*                           9992/mythbackend
udp        0      0 239.255.255.250:1900    0.0.0.0:*                           9992/mythbackend
unix  3      [ ]         STREAM     CONNECTED     8012726 9992/mythbackend
unix  3      [ ]         STREAM     CONNECTED     8012724 9992/mythbackend
unix  3      [ ]         STREAM     CONNECTED     8007336 9992/mythbackend
unix  3      [ ]         STREAM     CONNECTED     7828646 9992/mythbackend
unix  2      [ ]         STREAM     CONNECTED     7823277 9992/mythbackend

Perhaps the failure of the DBOX stuff is causing some initilization not to finish?

[Special K]

I have just updated to the unstable ~x86 -0.20_p13053
but no change.

so finally I wiped out the database and killed all inputs and cards an recreated my mpeg capturecard input and now all works fine. SOLVED
mythbackend silently hooked up on a bad cardinput config, while the older 0.19 ignored the strange configuration.

I hope the unstable 0.20_p13053 isn't that unstable it sounds

by the way mythtv has collected a lot of waste in its database the last years.

[Hobbes-X]

I hope the unstable 0.20_p13053 isn't that unstable it sounds

by the way mythtv has collected a lot of waste in its database the last years.

Each of the 0.20 ebuilds are based on snapshots of the mythtv 0.20-fixes branch, so really each progressive release of 0.20_p* is likely to be more stable than the last.

Unused tables from the database don't usually get cleaned up for at least a release after the information isn't necessary, so some database cruft can come from that. Also, lots of the past program information is kept around for future scheduling reference- myth wouldn't be able to identify duplicates if it didn't have past shows available to compare to.

[CoreDump]

Hello,

I have exactly the same symptoms, but it's on a random basis (mostly cold boot).
It's not a database problem since it was on a fresh install.
If I turn on all debug, the problem disappears... Very strange.