mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

The actual problem doesn't appear to be that too many files are opened -
the first problem is that it's not able to connect to the device, and
then it tries to do some action over and over causing too many file to
open up.

Were you having some weird network issues by chance?  Errors with your
network driver maybe?

Please double check all of your hardware and check ifconfig output for
TX or RX errors.

It doesn't look like there has been any changes to the HDHR library
support since you filed this bug
(http://svn.mythtv.org/trac/browser/branches/release-0-22-fixes/mythtv/libs/libmythtv)
but before we forward this upstream, they generally ask that you are
running the latest -fixes checkout.

The Mythbuntu team has builds of newer versions of MythTV available on a PPA if
you are interested in upgrading. Please follow the directions at http://mythbuntu.org/auto-builds
to enable them. 

** Changed in: mythtv (Ubuntu)
       Status: New => Incomplete

** Summary changed:

- Too many files open error in mythbackend 
+ Error connecting to HDHR causes too many files open

-- 
Error connecting to HDHR causes too many files open
https://bugs.launchpad.net/bugs/478895
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in ubuntu.

Status in “mythtv” package in Ubuntu: Incomplete

Bug description:
Binary package hint: mythtv

New to 0.22 and Karmic, I have started getting too many file open errors with my myth backend which is very disconcerting (it may be stopping my recordings). The symptom is not being able to start watching live TV (the computer is a dual backend + frontend)

When this happens, I see this in my mythbackend.log:
2009-11-05 07:09:12.719 TVRec(5): Changing from None to Watching WatchingLiveTV
2009-11-05 07:09:12.767 TVRec(5): HW Tuner: 5->5
2009-11-05 07:09:12.792 HDHRSH(10173A3D-1) Error: Unable to connect to device
2009-11-05 07:09:12.839 HDHRSH(10173A3D-1) Error: Get request failed
                       eno: Too many open files (24)
2009-11-05 07:09:12.858 HDHRSH(10173A3D-1) Error: Set request failed
                       eno: Too many open files (24)
2009-11-05 07:09:12.883 HDHRSH(10173A3D-1) Error: Get request failed
                       eno: Too many open files (24)
2009-11-05 07:09:12.909 HDHRSH(10173A3D-1) Error: Set request failed
                       eno: Too many open files (24)
2009-11-05 07:09:12.934 TVRec(5) Error: Failed to set channel to 91. Reverting to kState_None
2009-11-05 07:09:12.959 TVRec(5): Changing from Watching WatchingLiveTV to None
2009-11-05 07:09:12.984 HDHRSH(10173A3D-1) Error: Get request failed
                       eno: Too many open files (24)
2009-11-05 07:09:13.009 HDHRSH(10173A3D-1) Error: Set request failed
                       eno: Too many open files (24)

It seems that the problem is either in the backend or in the hdhomerun libraries. Restarting the backend temporarily addresses the issue. The problem seems to be occurring at least once a day.

I have attempted to change my number of open files for the mythtv group, but that did not help

Snippet from /etc/security/limits.conf:
@mythtv        hard    nofile         65535
@mythtv        soft    nofile         65535

Max-files open:
cat /proc/sys/fs/file-max
87309

cat /proc/sys/fs/file-nr
4832    0       87309

I keep forgetting to run lsof before restarting the backend, but I'll attach that next time it happens. This never happened to me while running Jaunty on this computer.

ProblemType: Bug
Architecture: i386
Date: Sun Nov  8 22:03:05 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Mythbuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091021)
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.22.0+fixes22594-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: mythtv
Uname: Linux 2.6.31-14-generic i686
XsessionErrors: (polkit-gnome-authentication-agent-1:2705): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed