[vdr] Frequent use of femon leads to Too many open files, frontend0 file handles aren't closed

[Brendon Higgins]

Hi,

I've encountered a problem with the femon plugin opening 
/dev/dvb/adapter0/frontend0 and not closing it. While tracking down a different 
issue I wrote a small script that would periodically (every 30 seconds, say) 
use svdrp and the femon plugin to grab some information about the current 
status of my DVB signal. After some hours of this running I discovered VDR 
would have some weird problems, and I've since narrowed it down to the fact 
that for whatever reason each loop of my script causes a new opening of 
/dev/dvb/adapter0/frontend0, which is never closed (even though I do send the 
femon quit command). I can keep track of how many open file handles there are 
using lsof | grep frontend0 | wc, which goes from one open instance at 
startup to several hundred after hours of running.

Ultimately, this causes VDR to stop working since the kernel won't allow it to 
open any more files beyond a limit. syslog says, as an example
vdr: [14876] ERROR (svdrp.c,126): Too many open files
last message repeated 175 times

Does anyone else see this behaviour, or is it just my setup?

VDR 1.6.0, femon 1.6.5, Debian Testing (mostly), Linux 2.6.28.

Peace,
Brendon



signature.asc
Description: This is a digitally signed message part.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Strange CPU usage cycling after user inactivity

[Brendon Higgins]

Hi Udo, list,

Udo Richter wrote (Sun, 1 Jul 2007):
 Brendon Higgins wrote:
  Jun 30 21:12:55 phi vdr: [3452] frontend 0 timed out while tuning to
  channel 0, tp 536
 
  I'm a bit confused that it's
  trying to access channel 0, since AFAICT there is *no* channel 0.

 'Channel 0' is usually the scan for new channels on currently unused
 transponders. The timeout means that this transponder probably doesn't
 transmit any DVB data streams at all at the moment. See Settings - DVB
 - Update channels - add new transponders.

 The CPU load problem may be a DVB device driver problem while trying to
 get a lock on an unused transponder.

That seems to have been it. Changing add new transponders to just add new 
channels means I don't see those timeouts anymore.

Thanks!

Brendon

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr