EMS 2.0 instancesCount
We have been testing Evostream 2.0 in house for several weeks now and have discovered an unusual problem. When instancesCount=-1 (default) we are unable to get outbound RTMP streams to work. If we set instancesCount=0 then outbound RTMP streams work as expected. We have been running Evostream v1.7.1 for years now and every time we bring up a new server we always leave the instances count set to -1. Server is Ubuntu 16.04 LTS with 2 cores. I can provide logs if needed, but this does not appear to be a problem with configuration.
Hi bbischan, This issue has been reported and resolved. There is a bug with RTMP playback when using multiple core that’s why it worked with instancesCount=0. Sorry for this issue and rest assured we will include the fix on the next release. 🙂 Thank you!
What impact does this have on performance/capacity? When do you anticipate the next release?
I’m also seeing this issue on Centos & Redhat servers with multiple cores. Streams work with a single daemon or in console mode. I’m using
EvoStream Media Server (www.evostream.com) version 2.0.1 build 5649 with hash: 97f4c69bcb092d7569c941407422688ed93d7e70 on branch: release/2.0/main – QBert – (built for CentOS-7-x86_64 on 2018-04-20T10:05:09.000)Any idea when this will be fixed?