Well, I have encountered this today ;-) The issue is not having the mysqldb package for python. Download it from: http://downloads.sourceforge.net/mysql-python/MySQL-python-1.2.1_p2.tar.gz?… You might need to install also the python-devel package: yum install yum install python-devel HIH Michael Original message: [Users] mediaproxy exceptions on session delete Klaus Darilion Thu, 15 Feb 2007 02:37:35 -0800 Hi! I have a problem with mediaproxy 1.8. Whenever a session is deleted there is an exception: Feb 14 14:18:27 foobar mediaproxy[27053]: delete OGI3Nzk1N2ExODY4NTIzYzIxMjc1NmYxN2MwMDBiZjU. info= Feb 14 14:18:27 foobar mediaproxy[27053]: session OGI3Nzk1N2ExODY4NTIzYzIxMjc1NmYxN2MwMDBiZjU.: 10558/10557/21113 packets, 778927/774750/1553531 bytes (caller/called/relayed) Feb 14 14:18:27 foobar mediaproxy[27053]: session OGI3Nzk1N2ExODY4NTIzYzIxMjc1NmYxN2MwMDBiZjU.: ended. Feb 14 14:18:27 foobar mediaproxy[27053]: error: uncaptured python exception, closing channel <rtphandler.CommandHandler connected 5.6.7.8:38879 at 0xb7d255ec> (exceptions.NameError:global name 'StopRecordSerializer' is not defined [/usr/lib/python2.3/asyncore.py|readwrite|86] [/usr/lib/python2.3/asyncore.py|handle_read_event|390] [/opt/mediaproxy/modules/rtphandler.py|handle_read|441] [/opt/mediaproxy/modules/rtphandler.py|process|568]) Feb 14 14:19:53 foobar mediaproxy[27053]: status Feb 14 14:19:53 foobar mediaproxy[27053]: execution time: 0.11 ms I could not find the problem - accounting.py with StopRecordSerializer is there, and it is imported in rtphandler. Do others also have problems and maybe a workaround? regards klaus -- Klaus Darilion nic.at