[SR-Users] /var/log/syslog in mediaproxy
Greger Viken Teigre
gregert at teigre.com
Wed Sep 9 07:00:38 CEST 2009
There's already something listening on port 25061, most likely another
instance of proxydispatcher.
g-)
Rakhmadhany Primananda wrote:
> hi everybody,,
>
> I'm using mediaproxy 1.7.2 and ser-0.9.6,,
>
> this is my output from syslog after I installed mediaproxy and running
> the process :
>
> root at serbuntu:/# cat /var/log/syslog | grep proxy
>
> Sep 3 13:38:12 serbuntu mediaproxy[2214]: Listening for commands on
> local socket `/var/run/mediaproxy.sock'
> Sep 3 13:38:12 serbuntu mediaproxy[2214]: Listening for remote
> commands on `10.100.0.45:25060 <http://10.100.0.45:25060/>'
> Sep 3 13:38:12 serbuntu mediaproxy[2214]: Remote commands are allowed
> from: 10.100.0.45, 127.0.0.1
> Sep 3 13:38:12 serbuntu mediaproxy[2214]: Using IP address
> `10.100.0.45' for the RTP/RTCP proxy
> Sep 3 13:38:12 serbuntu proxydispatcher[2217]: Listening for commands
> on local socket `/var/run/proxydispatcher.
> sock'
> Sep 3 13:38:12 serbuntu proxydispatcher[2217]: Listening for
> mediaproxy media timeout requests on 0.0.0.0:25061 <http://0.0.0.0:25061/>
> Sep 3 13:38:12 serbuntu proxydispatcher[2217]: Default mediaproxy
> server is on `/var/run/mediaproxy.sock'
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: Traceback (most recent
> call last):
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: File
> "/usr/local/mediaproxy/proxydispatcher.py", line 87, in <module>
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]:
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: dispatcher.start()
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: File
> "/usr/local/mediaproxy/modules/dispatcher.py", line 114, in start
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]:
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: mp =
> MediaproxyCommandHandler()
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: File
> "/usr/local/mediaproxy/modules/dispatcher.py", line 232, in __init__
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]:
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: raise RuntimeError,
> "couldn't create server (%s)" % why[1]
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: RuntimeError
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: :
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: couldn't create server
> (Address already in use)
> Sep 3 13:38:13 serbuntu proxydispatcher[2217]: exiting.
> Sep 3 14:08:01 serbuntu mediaproxy[2214]: received signal 15
> Sep 3 14:09:09 serbuntu mediaproxy[4987]: Listening for commands on
> local socket `/var/run/mediaproxy.sock'
> Sep 3 14:09:09 serbuntu mediaproxy[4987]: Listening for remote
> commands on `10.100.0.45:25060 <http://10.100.0.45:25060/>'
> Sep 3 14:09:09 serbuntu mediaproxy[4987]: Remote commands are allowed
> from: 10.100.0.45, 127.0.0.1
> Sep 3 14:09:09 serbuntu mediaproxy[4987]: Using IP address
> `10.100.0.45' for the RTP/RTCP proxy
> Sep 3 14:09:10 serbuntu proxydispatcher[4990]: Listening for commands
> on local socket `/var/run/proxydispatcher.sock'
> Sep 3 14:09:10 serbuntu proxydispatcher[4990]: Listening for
> mediaproxy media timeout requests on 0.0.0.0:25061 <http://0.0.0.0:25061/>
> Sep 3 14:09:10 serbuntu proxydispatcher[4990]: Default mediaproxy
> server is on `/var/run/mediaproxy.sock'
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: Listening for commands
> on local socket `/var/run/proxydispatcher.sock'
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: Listening for
> mediaproxy media timeout requests on 0.0.0.0:25061 <http://0.0.0.0:25061/>
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: Default mediaproxy
> server is on `/var/run/mediaproxy.sock'
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: Traceback (most recent
> call last):
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: File
> "/usr/local/mediaproxy/proxydispatcher.py", line 87, in <module>
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]:
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: dispatcher.start()
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: File
> "/usr/local/mediaproxy/modules/dispatcher.py", line 114, in start
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]:
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: mp =
> MediaproxyCommandHandler()
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: File
> "/usr/local/mediaproxy/modules/dispatcher.py", line 232, in __init__
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]:
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: raise RuntimeError,
> "couldn't create server (%s)" % why[1]
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: RuntimeError
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: :
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: couldn't create server
> (Address already in use)
> Sep 3 21:01:19 serbuntu proxydispatcher[7498]: exiting.
>
> my question:
> what's the meaning of serbuntu proxydispatcher[7498]: raise
> RuntimeError, "couldn't create server (%s)" % why[1] and serbuntu
> proxydispatcher[7498]: couldn't create server (Address already in use)
> ? is it a bug or error?
>
> and this is my mediaproxy.ini configuration (mediaproxy and SER
> running in one machine) :
>
> root at serbuntu:/# cat /usr/local/mediaproxy/mediaproxy.ini
>
> ;
> ; Configuration file for MediaProxy
> ;
>
> [Dispatcher]
>
> start = yes
>
> socket = /var/run/proxydispatcher.sock
> group = ser
> defaultProxy = /var/run/mediaproxy.sock
>
> [MediaProxy]
>
> start = yes
>
> socket = /var/run/mediaproxy.sock
> group = ser
> listen = 10.100.0.45
> allow = 10.100.0.45
> proxyIP = 10.100.0.45
> portRange = 60000:65000
> ;TOS = 0xb8
> ;idleTimeout = 60
> ;holdTimeout = 3600
> ;forceClose = 0
>
> [Accounting]
> dbaccounting = off
>
> [Database]
> user = dbuser
> password = dbpass
> host = dbhost
> database = radius
> table = radacct
>
> thankq,,
> regards,,
>
> dhany
> ------------------------------------------------------------------------
>
> _______________________________________________
> sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20090909/f1b30a55/attachment.htm>
More information about the sr-users
mailing list