Hans Meine wrote:
> On Donnerstag 29 Januar 2009, Duncan Webb wrote:
>>> BTW: How do I enable the output of all the _debug_('...', 2) lines?  (I
>>> tried setting DEBUG and DEBUG_RECORDSERVER to 2, but that did not do the
>>> trick.)
>> Have you set?
>> LOGGING = logging.DEBUG
>> LOGGING_RECORDSERVER = logging.DEBUG
> 
> Sure.  I am getting all debug output from _debug_('...', DINFO) lines, but 
> not 
> from the _debug_('...', 2) ones (which usually contain method calls w/ 
> params).

Don't see why you're not getting level 2 debug messages, the full set of
debugging that I use is:

# Debugging settings
LOGGING = logging.DEBUG
LOGGING_RECORDSERVER = logging.DEBUG
LOGGING_ENCODINGSERVER = logging.DEBUG
LOGGING_RSSSERVER = logging.DEBUG
DEBUG_RECORDSERVER = 2
DEBUG_ENCODINGSERVER = 2
DEBUG_RSSSERVER = 1
DEBUG_WEBSERVER = 1
DEBUG_CHILDAPP = 1
DEBUG_TIME = 0
DEBUG = 1
DEBUG = 2
DEBUG_STDOUT = 0
DEBUG_SKIN = 0
DEBUG_IDLEBAR = 0
DEBUG_IDLEBAR_FONT = 'tiny0'
DEBUG_BENCHMARKING = 0
DEBUG_DEBUGGER = 1

The level 2 debug messages are in the recordserver-*.log.

>> Do check it in and you could change the WARNING to an ERROR or perhaps
>> restrict the exception handler not to be a catch all.
> 
> Hmm.  I don't know why or how I should change the exception handler.  
> Actually, the patch I sent to the list is obviously not related to the 
> problem I wanted to fix originally, namely that the recordserver does not 
> start up.  Instead, it happened again today, no recordings worked and my wife 
> is disappointed again.  There are no errors at all in the logs (stupid me 
> disabled the debug output after the patching).  FWIW, this is all I have:
> 
> ================================================================================
> Freevo 1.8.4-svn r11270 started at Sat Jan 31 21:17:46 2009
> --------------------------------------------------------------------------------
> 2009-01-31 21:17:46,194 INFO     config.py (531): 
> LOGDIR: /var/log /var/log/freevo
> 2009-01-31 21:17:46,196 INFO     config.py (532): 
> STATICDIR: /var/lib /var/lib/freevo
> 2009-01-31 21:17:46,197 INFO     config.py (533): 
> CACHEDIR: /var/cache /var/cache/freevo
> 2009-01-31 21:17:46,199 INFO     config.py (552): Loading freevo 
> configuration 
> file "/etc/freevo/freevo.conf"
> 2009-01-31 21:17:47,216 INFO     new process watcher instance
> 
> After that, the recording server simply vanished, no more output, no process.

This strange, which version of kaa are you using?

If you are using svn of kaa or freevo it is a good idea to remove the
build directories and the site-packages once in a while.

The recordserver is working for the current svn, I was doing some
testing with it yesterday. Plus it runs on the living room machine
without any problems.

Checking the config for errors could be a possible problem, doubt that
it is in this case. There are two ways to check, use the reindent.py
from python (Tools/scripts/reindent.py) and the second way is to import
it with the freevo prompt command.

Duncan

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to