/
Troubleshooting
- You can see the role of a node on the Tags tab in the EC2 console
- VERY IMPORTANT: If you have more than one autoscaling environment running, it is essential that the
instancecontroller.instanceNamePrefix=
property is set to a completely unique value for each environment, or the first stream manager may terminate the nodes belonging to the second group. For example, if you have one environment withinstancecontroller.instanceNamePrefix=node
and another one withinstancecontroller.instanceNamePrefix=node123
, thenode123
instances will be terminated by the first stream manager. This occurs because it identifies them as starting withnode
and therefore as instances it should be managing, and which are not present it its database. Find theinstancecontroller.instanceNamePrefix=
in the{red5pro}/webapps/streammanager/WEB-INF/red5-web.properties
, and edit it accordingly. - If you have created a new nodegroup, but adding an Origin server doesn't automatically spin up an accompanying Edge server, check the following on your node image:
-
Verify that red5pro/conf/autoscale.xml in your Red5Pro server image points to the IP address of your stream manager
replace 0.0.0.0 in <property name="cloudWatchHost" value="http://0.0.0.0:5080/streammanager/cloudwatch"/>
make sure that you the change active value from default “false” to “true” (
<property name="active" value="true"/>
) - Check
{red5pro}/conf/cluster.xml
- make sure that the password set for<!-- edge/origin link cluster password -->
matches thecluster.password=
in the stream managerred5-web.properties
file. - Make sure that your have your
LICENSE.KEY
file in the {red5pro} root directory; clustering (and in turn, autoscaling) will not work without a valid license key. - If all of these check out, then start up red5pro service on your ami instance, and tail the Stream Manager
{red5pro}/log/red5.log
file - you should see messages about an instance pinging the Stream Manager. If you don't, then check for inbound port access to your stream manager (or outbound port access from your node security group). - If you are using an existing AWS VPC that hasn't been created per our instructions, then it is essential that when you create (or modify) the subnets they use a different route table than the VPC AND that their route table includes an internet gateway.