File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/pyinotify.py", line 1887, in add_watch for rpath in self.__walk_rec(apath, rec): File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/pyinotify.py", line 2075, in __walk_rec for root, dirs, files in os.walk(top): File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/os.py", line 284, in walk if isdir(join(top, name)): File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/posixpath.py", line 68, in join path += b UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 9: ordinal not in range(128)
Is that the whole stack trace? If yes, then this is a bug with Python or pyinotify. Please check again if there is more information.
Also, you probably have a queue of files in /srv/airtime/stor/organize waiting to be imported. One of those files is causing Media Monitor to fail. Try removing all of them and adding them one at a time to see which one is the culprit.
that's the only trace, nothing else in the logs... no files in "organize" an I've now a new bug, but similar on another machine (who is in ubuntu 10.04) :
File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/pyinotify.py", line 1887, in add_watch for rpath in self.__walk_rec(apath, rec): File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/pyinotify.py", line 2075, in __walk_rec for root, dirs, files in os.walk(top): File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/os.py", line 284, in walk if isdir(join(top, name)): File "/usr/lib/airtime/airtime_virtualenv/lib/python2.6/posixpath.py", line 68, in join path += b UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 15: ordinal not in range(128)
root@sd-27666:/var/log/airtime/media-monitor# tail media-monitor.log path += b UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 15: ordinal not in range(128)
It really hard to say what the problem is because none of those files mentioned in the stack trace were written by the Airtime team. What are the lines in the log file before that? Could give us some kind of idea what media monitor was doing before the problem happened?
I've found the errors And that was not a sinecure ... In fact I have some bad files in my directories and media-monitor crash on it ! perhaps a good thing in the future will be to create a different log for bad files and render media-monitor more error compliant ...