[arm-allstar] Asterisk restart (astres.sh) unable to bind socket (UPDATE)
wa3dsp at gmail.com
Sat Jan 13 18:51:03 EST 2018
Yes you should ALWAYS kill the ezstream process before restarting. Here
is how I do it in a script rather than running astres.sh -
killall -9 lame
killall -9 ezstream
On Sat, Jan 13, 2018 at 6:00 PM, "Lawrence Roney via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> I did 'netstat -atunp | grep 5038'
> It looks like the EZStream (Broadcastify feed) was holding the port open.
> When I killed the EZstream process, it released port 5038 and now astres.sh
> works OK again.
> -----Original Message-----
> From: Lawrence Roney [mailto:roney at chiarappa.com]
> Sent: Saturday, January 13, 2018 2:05 PM
> To: 'arm-allstar at hamvoip.org' <arm-allstar at hamvoip.org>
> Subject: Asterisk restart (astres.sh) unable to bind socket
> I've noticed recently when I use 'astres.sh' to restart Asterisk, it will
> fail. It appears that Asterisk is not unbinding the port (socket) that is
> defined in manager.conf
> Here's what I get:
> # astres.sh
> Restarting Asterisk...
> Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)
> If I execute # asterisk -cvvvv I get:
> == Manager registered action ListCommands
> == Manager registered action UserEvent
> == Manager registered action WaitEvent [Jan 13 13:26:21] WARNING:
> manager.c:3159 init_manager: Unable to bind socket: Address already in use
> If I fully reboot or if I change port = 5038 to something else in
> manager.conf then Asterisk will restart.
> Any ideas?
> Lawrence N6YFN
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the arm-allstar