AWS EC2 fails when using more than 20 workers

mediasoup libraries
1

Hi,

We are trying to open 36 workers and getting the following error.
We have a machine with 36 vCPU, hopping each worker will consume a different CPU.
Is that the correct usage?

Error: port bind failed too many times [udp:127.0.0.1, attempt:21]
at Channel._processMessage (/home/ec2-user/streaming-server/node_modules/mediasoup/lib/Channel.js:220:37)
at Socket.Channel._consumerSocket.on (/home/ec2-user/streaming-server/node_modules/mediasoup/lib/Channel.js:80:34)
at Socket.emit (events.js:193:13)
at addChunk (_stream_readable.js:295:12)
at readableAddChunk (_stream_readable.js:276:11)
at Socket.Readable.push (_stream_readable.js:231:10)
at Pipe.onStreamRead (internal/stream_base_commons.js:154:17)
e ? Error: MID already exists in RTP listener [mid:0]
at Channel._processMessage (/home/ec2-user/streaming-server/node_modules/mediasoup/lib/Channel.js:220:37)
at Socket.Channel._consumerSocket.on (/home/ec2-user/streaming-server/node_modules/mediasoup/lib/Channel.js:80:34)
at Socket.emit (events.js:193:13)
at addChunk (_stream_readable.js:295:12)
at readableAddChunk (_stream_readable.js:276:11)
at Socket.Readable.push (_stream_readable.js:231:10)
at Pipe.onStreamRead (internal/stream_base_commons.js:154:17)

2

Well, which min-max port range you pass to each mediasoup Worker? Do you understand what those ports are for?

3

rtcMinPort: 40000,
rtcMaxPort: 49999,

4

I was about to explain why that happens and how to avoid it. But, instead of that, I’m gonna release a new version of mediasoup that makes this easier. Will be ready today.

5

Wow! Thanks,
It will be grate if you will point as to the problem .

6

ok, please upgrade to mediasoup 3.4.7. The commit should be self-explanatory.