[Users] mediaproxy errors

Helge Waastad helge at smartnet.no
Thu May 3 12:59:20 CEST 2007


Hi,
yes I actually have this installer on my system.

I realized now that I have more serious problem with one of my servers
which might also be a source of problems

It takes ~1 hour to start OpenSER...only with 50 users. Everything's
soooooo slow....

Well thanks a lot, anyway

have a nice day :-)

br hw


tor, 03.05.2007 kl. 12.40 +0200, skrev Klaus Darilion:
> Hi!
> 
> We have this all the time. But it does not cause any problems.
> 
> Tried this?
> http://www.mail-archive.com/users@openser.org/msg09017.html
> 
> regards
> klaus
> 
> Helge Waastad wrote:
> > Hi,
> > I'm running mediaproxy 1.8.2 and have started to se:
> > 
> > error: uncaptured python exception, closing channel
> > <rtphandler.CommandHandler connected <ip-address>:42224 at 0x2a99dff518>
> > (socket.error:(9, 'Bad file descriptor')
> > [/usr/lib64/python2.3/asyncore.py|readwrite|88]
> > [/usr/lib64/python2.3/asyncore.py|handle_write_event|397]
> > [/etc/mediaproxy/modules/rtphandler.py|handle_write|453]
> > [/usr/lib64/python2.3/asyncore.py|send|337])
> > 
> > does anyone knw what this means?
> > 
> > br hw
> > 
> > 
> > 
> > 
-- 
Helge Waastad
Senior developer
Smartnet / Datametrix
Et selskap i Ignis gruppen

Martin Lingesvei 25
1367 Snarøya
Postboks 494
1327 Lysaker
Telefon: +47 67830017
Mobil: +47 48095461
Support: +47 67830045 -
support at smartnet.no
www.smartnet.no




More information about the sr-users mailing list