1 - If you have created a new nodegroup, but adding an Origin server doesn't automatically initiate an accompanying Edge server, check the following on your server instance:

  • Verify that red5pro/conf/autoscale.xml in your Red5Pro server image points to the IP address of your stream manager (replace in <property name="cloudWatchHost" value=""/>); 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 the cluster.password= in the stream manager red5-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). 2 - If you have any issues with, or are updating anything in your live environment, you should restart Red5 Pro service on your instances in the following order:
  • 1 - Restart on the ORIGIN server(s) first
  • 2 - Then, restart on the EDGE server(s)
  • 3 - Finally, restart the STREAM MANAGER Red5 Pro service last.

3 - NOTE if you reboot a node that is part of a nodegroup, the stream manager will most likely replace it before it restarts, which may cause nodegroup instability. If a node is unresponsive the best course of action is to stop/terminate the instance from the hosting platform dashboard.