outstreamcmd, ezstream, and error: manager.c: Unable to bind socket: Address already in use

App_rpt-users
1

After setting up the outstreamcmd parameter in rpt.conf with ezstream on my DIAL AllStar node I noticed that when I stopped and restarted the asterisk service, I was getting the following error in the log:

[Oct 29 23:15:37] WARNING[19838] manager.c: Unable to bind socket: Address already in use

I found that after a service asterisk stop, port 5038 was still in use.

my manager.conf file has port = 5038

prior to a service asterisk stop - I get the following:

root@Server1:~# ps -ef | grep 7497

root 7497 1 24 13:45 ? 00:09:24 /usr/sbin/asterisk

root 7528 7497 0 13:45 ? 00:00:00 /bin/sh -c /usr/bin/lame --preset cbr 16 -r -m m -s 8 --bitwidth 16 - - | /usr/bin/ezstream -qvc /etc/asterisk/ezstream.xml

after a service asterisk stop I can still see port 5038 in use:

root@Server1:~# netstat -nlp|grep 5038

tcp 0 0 127.0.0.1:5038 0.0.0.0:* LISTEN 7528/sh

Now, when I issue asterisk service start I get the following error:

manager.c: Unable to bind socket: Address already in use

and Asterisk fails to load

If I kill pid 7528 then my service asterisk start works fine.

I assume outstreamcmd is using manager, shells out to ezstream which is a child of asterisk, and when asterisk shuts down, the process running ezstream is left running.

Should I put something in my asterisk startip script to look for processes using 5038 and kill them?

Thanks

-Larry

2

Make sure asterisk is stopping.

kill it if necessary

killall -9 /usr/sbin/asterisk
···

On 11/01/2015 08:34 AM, Larry da Ponte
wrote:

      After setting up the outstreamcmd parameter in rpt.conf

with ezstream on my DIAL AllStar node I noticed that when I
stopped and restarted the asterisk service, I was getting the
following error in the log:

      [Oct 29 23:15:37] WARNING[19838] manager.c: Unable to bind

socket: Address already in use

      I found that after a service asterisk stop, port 5038 was

still in use.

my manager.conf file has port = 5038

prior to a service asterisk stop - I get the following:

root@Server1:~# ps -ef | grep 7497

        root � � �7497 � � 1 24 13:45 ? � � � �00:09:24

/usr/sbin/asterisk

        root � � �7528 �7497 �0 13:45 ? � � � �00:00:00 /bin/sh

-c /usr/bin/lame --preset cbr 16 -r -m m -s 8 --bitwidth 16

    • | /usr/bin/ezstream -qvc /etc/asterisk/ezstream.xml
      after a service asterisk stop I can still see port 5038 in

use:

root@Server1:~# netstat -nlp|grep 5038

tcp � � � �0 � � �0 127.0.0.1:5038 � � � �
�0.0.0.0:* � � � � � � � LISTEN � � �7528/sh

      Now, when I issue asterisk service start I get the

following error:

manager.c: Unable to bind socket: Address already in use

and Asterisk fails to load

      If I kill pid 7528 then my service asterisk start works

fine.

      I assume outstreamcmd is using manager, shells out to

ezstream which is a child of asterisk, and when asterisk shuts
down, the process running ezstream is left running.

      Should I put something in my asterisk startip script to

look for processes using 5038 and kill them?

Thanks

-Larry




_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

-- "Anything is possible if you don't know what you are talking about."
1st Law of Logic

App_rpt-users@ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-usershttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users