Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Commits
Ticket #10302: Backend socket problems on Centos 6
 

Index | Next | Previous | View Flat


noreply at mythtv

Feb 1, 2012, 1:52 PM


Views: 274
Permalink
Ticket #10302: Backend socket problems on Centos 6

#10302: Backend socket problems on Centos 6
-------------------------------------+-------------------------------------
Reporter: Jonathan Martens | Type: Bug Report -
<jonathan@…> | General
Status: new | Priority: minor
Milestone: unknown | Component: MythTV - General
Version: Master Head | Severity: medium
Keywords: | Ticket locked: 0
-------------------------------------+-------------------------------------
I have seen there are a few bugs concerning the communication between the
backend and frontend on CentOS 6.x.

I am also running into this issue with latest trunk, which manifests
itself in mythfrontends logs like this:

{{{
2012-02-01 22:37:28.763081 I MythCoreContext: Connecting to backend
server: 10.0.10.228:6543 (try 1 of 1)
2012-02-01 22:37:28.763523 I MythSocket(27b03a0:44): IP is local, using
loopback address instead
2012-02-01 22:37:28.763538 I MythSocket(27b03a0:44): attempting connect()
to (127.0.0.1:6543)
2012-02-01 22:37:28.763573 I MSocketDevice::connect: setting Protocol to
IPv4
2012-02-01 22:37:28.763579 I MSocketDevice::connect: attempting to create
new socket
2012-02-01 22:37:28.763928 I MythSocket(27b03a0:44): write -> 44 30
MYTH_PROTO_VERSION 72 D78EFD6F
2012-02-01 22:37:35.765089 E MythSocket(27b03a0:44): readStringList:
Error, timed out after 7000 ms.
2012-02-01 22:37:35.765181 C Protocol version check failure.
The response to MYTH_PROTO_VERSION was empty.
This happens when the backend is too busy to
respond,
or has deadlocked in due to bugs or hardware
failure.
2012-02-01 22:37:35.765231 C Unable to determine master backend time zone
settings. If those settings differ from local settings, some
functionality will fail.
}}}

While investigating this I started looking through my mythbackend logs and
found no evidence off the command ever arriving at the backend, tcpdump
confirms that no reaction is given at all by the backend.

If I look at the output of netstat I see the following after the error:

{{{
[jonathan [at] localhos ~]$ sudo netstat -tonp | grep 6543
tcp 39 0 127.0.0.1:6543 127.0.0.1:51125
CLOSE_WAIT - off (0.00/0/0)
tcp 39 0 127.0.0.1:6543 127.0.0.1:51126
CLOSE_WAIT - off (0.00/0/0)
[jonathan [at] localhos ~]$
}}}

A little googling on the internet made me stumble on this:
http://www.sunmanagers.org/pipermail/summaries/2006-January/007068.html

This seems to indicate that:
"CLOSE_WAIT connections indicate an error in the software.

It's a connection which has been torn down but your side of things
still has a filedescriptor open."

For the record the version numbers:

Backend:
{{{
[jonathan [at] localhos ~]$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.25pre-4297-ga043706
MythTV Branch : master
Network Protocol : 72
Library API : 0.25.20120201-1
QT Version : 4.6.2
Options compiled in:
linux profile use_hidesyms using_oss using_backend using_bindings_perl
using_bindings_python using_bindings_php using_dvb using_frontend
using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv
using_joystick_menu using_libcrypto using_libudf using_lirc using_mheg
using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2
using_v4l1 using_x11 using_xrandr using_bindings_perl
using_bindings_python using_bindings_php using_mythtranscode using_opengl
using_ffmpeg_threads using_live using_mheg using_libudf
[jonathan [at] localhos ~]$
}}}

Frontend:
{{{
[jonathan [at] localhos ~]$ mythfrontend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.25pre-4297-ga043706
MythTV Branch : master
Network Protocol : 72
Library API : 0.25.20120201-1
QT Version : 4.6.2
Options compiled in:
linux profile use_hidesyms using_oss using_backend using_bindings_perl
using_bindings_python using_bindings_php using_dvb using_frontend
using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv
using_joystick_menu using_libcrypto using_libudf using_lirc using_mheg
using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2
using_v4l1 using_x11 using_xrandr using_bindings_perl
using_bindings_python using_bindings_php using_mythtranscode using_opengl
using_ffmpeg_threads using_live using_mheg using_libudf
[jonathan [at] localhos ~]$
}}}

Is there anything I can do to debug this or help in troubleshooting this
issue?

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10302>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-commits

Subject User Time
Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 1, 2012, 1:52 PM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 5, 2012, 9:20 AM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 5, 2012, 11:50 AM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 5, 2012, 12:19 PM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 5, 2012, 12:23 PM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 13, 2012, 9:45 AM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 20, 2012, 9:48 AM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv Feb 25, 2012, 4:19 AM
    Re: Ticket #10302: Backend socket problems on Centos 6 noreply at mythtv May 23, 2012, 7:05 PM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.