[RESOLVED] problems with media monitor on 2.0.0.4 - Airtime Support Discussions on Sourcefabric Forum

Albert FR · Post edited by Albert FR at 2012-02-08 15:03:06

on a fresh install

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)

----
AIRTIME_STATUS_URL             = http://localhost/api/status/format/json/api_key/%%api_key%%
AIRTIME_SERVER_RESPONDING      = OK
KERNEL_VERSION                 = 2.6.38-13-generic-pae
MACHINE_ARCHITECTURE           = i686
TOTAL_MEMORY_MBYTES            = 4042704
TOTAL_SWAP_MBYTES              = 1044220
AIRTIME_VERSION                = 2.0.0
OS                             = Ubuntu 11.04 i686
CPU                            = Intel(R) Core(TM) i3 CPU         540 @ 3.07GHz
WEB_SERVER                     = Apache/2.2.17 (Ubuntu)
PLAYOUT_ENGINE_PROCESS_ID      = 911
PLAYOUT_ENGINE_RUNNING_SECONDS = 645
PLAYOUT_ENGINE_MEM_PERC        = 0.2%
PLAYOUT_ENGINE_CPU_PERC        = 0.0%
LIQUIDSOAP_PROCESS_ID          = 919
LIQUIDSOAP_RUNNING_SECONDS     = 645
LIQUIDSOAP_MEM_PERC            = 0.5%
LIQUIDSOAP_CPU_PERC            = 3.4%
MEDIA_MONITOR_PROCESS_ID       = 2338
MEDIA_MONITOR_RUNNING_SECONDS = 230
MEDIA_MONITOR_MEM_PERC         = 0.2%
MEDIA_MONITOR_CPU_PERC         = 0.0%
SHOW_RECORDER_PROCESS_ID       = 930
SHOW_RECORDER_RUNNING_SECONDS = 645
SHOW_RECORDER_MEM_PERC         = 0.2%
SHOW_RECORDER_CPU_PERC         = 0.0%
RABBITMQ_PROCESS_ID            = 1169
RABBITMQ_RUNNING_SECONDS       = 645
RABBITMQ_MEM_PERC              = 0.4%
RABBITMQ_CPU_PERC              = 0.0%

Albert FR

We have same errors in the past (with 1.8.x) with utf8 characters
a bug return ?

Albert FR

no one have the same problem ?

Albert FR

that's seems to be really a utf8 problem, but i'm trying to put an

# -*- coding: utf8 -*-

at the first line of each program without results ...

any idea ?

Martin Konecny

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.

Albert FR · Post edited by Albert FR at 2012-02-06 04:11:58

Hi,

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)

YounesDesign

Hello Albert!

I've got the axact same error!

I thought this was fixed since the version 1.9!

ascii prob!

Hey the Airtime team! Any idea how to fix this?

Martin Konecny

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?

Albert FR

exept log file from media-monitor all is correct, and no errors...

the log file is attached

thanks for your help

Albert FR

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 ...

Albert FR · Post edited by Albert FR at 2012-02-09 04:58:33

to be more specific media-monitor crash on the character : '

that's could be a problem...

Howdy, Stranger!

Categories

Poll

Top Posters