Ugh! Bind failed, try again

Wowza Streaming Engine
1

OK - I’ve been around long enough to have checked the obvious - but can’t for the life of me understand why the dang server won’t start.

I’m a monthly subscriber with a CENTOS instance on AWS that I’m currently developing with. Wowza 3 had been working fine a month back, but now I’m ready to get going on it again and I’m getting:

2012-02-10	15:13:37	EST	comment	vhost	WARN	200	_defaultVHost_	Bind failed, try again ([any]:1935): java.net.BindException: Address already in use	-	-	-	43.79

Netstat -a |fgrep 1935 produces

tcp        0      0 localhost:19350             *:*                         LISTEN      
tcp        0      0 localhost:37118             localhost:19350             ESTABLISHED 
tcp        0      0 localhost:19350             localhost:37118             ESTABLISHED 
udp        0      0 ip-10-111-31-17.e:19350     *:*                                     
udp        0      0 localhost:19350             *:*                                     
udp        0      0 ip-10-111-31-17.e:19351     *:*                                     
udp        0      0 localhost:19351             *:*

I’ve rebooted - with no success

I"ve got ports open through my Security Group

I’ve grabbed the latest WowzaMediaServer-3.0.x-3.0.4

No Joy!

Any Ideas? Anyone?

2

In Linux, it’s “netstat -p” to see the program associated with the port. You’ll have to figure out what that program is and stop it, change its port, or change Wowza’s port.

Check that you don’t have the Wowza service already loaded. Do “ps aux |grep java”. Look in the Wowza User Guide for info on how to start/stop the Wowza service.

3

In Linux, it’s “netstat -p” to see the program associated with the port. You’ll have to figure out what that program is and stop it, change its port, or change Wowza’s port.

Check that you don’t have the Wowza service already loaded. Do “ps aux |grep java”. Look in the Wowza User Guide for info on how to start/stop the Wowza service.

Well

  • netstat -p hasn’t identified any process

  • no java processes running

  • I’ve removed the server by deleting the installation from /usr/local

  • I’ve re-installed

    I still get the bind error :frowning:

    The startup session follows:

    [root@ip-10-111-31-17 bin]# ./startup.sh
/usr/local/WowzaMediaServer/lib/
Configure logging: file:///usr/local/WowzaMediaServer/conf/log4j.properties
INFO server server-start Wowza Media Server 3 Monthly Edition 3.0.4 build1127 -
INFO server comment - Server License Key: SVRM3-XXXXX-XXXXX-XXXXX-XXXXX-bvpZk
INFO server comment - Maximum Connections: Unlimited
INFO server comment - Transcoder Streams Available: Unlimited
INFO server comment - Transcoder Watermark: No
INFO server comment - nDVR Available: Yes
INFO server comment - DRM Available: Yes
INFO server comment - Hardware Available Processors: 1
INFO server comment - Hardware Physical Memory: 91MB/622MB
INFO server comment - Max File Descriptor Count: 20000
INFO server comment - Open File Descriptor Count: 43
INFO server comment - OS Name: Linux
INFO server comment - OS Version: 2.6.21.7-2.fc8xen
INFO server comment - OS Architecture: amd64
INFO server comment - Java Name: Java HotSpot(TM) 64-Bit Server VM
INFO server comment - Java Vendor: Sun Microsystems Inc.
INFO server comment - Java Version: 1.6.0_14
INFO server comment - Java VM Version: 14.0-b16
INFO server comment - Java Spec Version: 1.6
INFO server comment - Java Home: /usr/java/jdk1.6.0_14/jre
INFO server comment - Java Max Heap Size: 1160MB
INFO server comment - Java Architecture: 64
INFO server comment - Java Locale[user.language]: en
INFO server comment - Java Locale[user.country]: US
INFO server comment - Java Locale[file.encoding]: ANSI_X3.4-1968
INFO server comment - Java Args[0]: -Xmx1200M
INFO server comment - Java Args[1]: -Djava.net.preferIPv4Stack=true
INFO server comment - Java Args[2]: -Dcom.sun.management.jmxremote=true
INFO server comment - Java Args[3]: -Dcom.wowza.wms.runmode=standalone
INFO server comment - Java Args[4]: -Dcom.wowza.wms.native.base=linux
INFO server comment - Java Args[5]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaMediaServer
INFO server comment - Java Args[6]: -Dcom.wowza.wms.ConfigURL=
INFO server comment - Java Args[7]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer
INFO server comment - Server runmode: standalone
INFO server comment - Server native.platform: linux
INFO server comment - Server threads[h/t]: 10/10
INFO server comment - CMDInterface now listening: [any]:8083
INFO vhost vhost-start _defaultVHost_ -
INFO server comment - _defaultVHost_ threads[h/t]:120/80 home:/usr/local/WowzaMediaServer
INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
WARN vhost comment _defaultVHost_ Bind failed, try again ([any]:1935): java.net.BindException: Address already in use
etc.
etc.
etc.

    Next I’m going to try installing on a new EC2 instance

4

Well - I did imply it was a dev server - looks like someone had tinkered with the Adobe FMS settings and it was running though not “obviously” using the port. You don’t see it in Netstat, but I think something funny happens with Wowza tries to compete at startup for ports etc.

Problem solved - another 2 hours of my life I won’t get back HA!