[mythtv-commits] Ticket #10985: upgraded from 0.25 to 0.25.2 via atrpms, backend no longer has open port to listen
MythTV
noreply at mythtv.org
Thu Aug 9 21:18:11 UTC 2012
#10985: upgraded from 0.25 to 0.25.2 via atrpms, backend no longer has open port to
listen
------------------------------------+--------------------------------
Reporter: johnny@… | Owner:
Type: Bug Report - General | Status: infoneeded_new
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25-fixes
Severity: medium | Resolution:
Keywords: backend port listening | Ticket locked: 0
------------------------------------+--------------------------------
Changes (by wagnerrp):
* version: Unspecified => 0.25-fixes
* milestone: 0.25.2 => unknown
Comment:
Within a few seconds of starting the backend, you should be seeing the
http and protocol servers coming online with...
{{{
2012-07-27 02:15:41.201245 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP 127.0.0.1:6544
2012-07-27 02:15:41.201320 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP 192.168.10.5:6544
2012-07-27 02:15:41.201515 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP [0:0:0:0:0:0:0:1]:6544
2012-07-27 02:15:41.201610 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP [fe80:1:0:0:0:0:0:1%lo0]:6544
2012-07-27 02:15:42.014819 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP 127.0.0.1:6543
2012-07-27 02:15:42.014852 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP 192.168.10.5:6543
2012-07-27 02:15:42.014918 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP [0:0:0:0:0:0:0:1]:6543
2012-07-27 02:15:42.014956 I [5557/102783] CoreContext serverpool.cpp:395
(listen) - Listening on TCP [fe80:1:0:0:0:0:0:1%lo0]:6543
}}}
Or you should see some kind of error indicating the IP address you
specified was not available on the system. Or you should see some kind of
error indicating why it failed to listen on a certain address. Or you
should see some error in the scheduler indicating a fault it detected that
would prevent normal operation. At the default general/info log level you
are using, there should be some kind of warning indicating something, but
I see nothing. Could you increase the log verbosity and try again?
--
Ticket URL: <http://code.mythtv.org/trac/ticket/10985#comment:6>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list