[jitsi-users] conferences error mesg in jitsi-videobridge


#1

Hi All

We are getting a error after 25 conferences with 5 Users along AV.
The error mesg is here below: we have increased no of User per Conference in

root@jitsivb:~# cat /etc/jitsi/videobridge/sip-communicator.properties
org.jitsi.impl.neomedia.transform.CachingTransformer.CACHE_SIZE_STREAMS=200
root@jitsivb:~#

Error Mesg:

SEVERE: Jitsi-Hammer_4 : Error during the generation of the IceMediaStream
java.io.IOException: Failed to bind even a single host candidate for component:Component id=1 parent stream=audio
no local candidates.
no remote candidates. preferredPort=6000 minPort=6000 maxPort=6050
        at org.ice4j.ice.harvest.HostCandidateHarvester.harvest(HostCandidateHarvester.java:381)
        at org.ice4j.ice.Agent.gatherCandidates(Agent.java:462)
        at org.ice4j.ice.Agent.createComponent(Agent.java:404)
        at org.jitsi.hammer.utils.IceMediaStreamGenerator.generateIceMediaStream(IceMediaStreamGenerator.java:158)
        at org.jitsi.hammer.FakeUser.acceptJingleSession(FakeUser.java:627)
        at org.jitsi.hammer.FakeUser.processPacket(FakeUser.java:841)
        at org.jivesoftware.smack.XMPPConnection$ListenerWrapper.notifyListener(XMPPConnection.java:1233)
        at org.jivesoftware.smack.XMPPConnection$ListenerNotification.run(XMPPConnection.java:1143)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

Aug 11, 2016 6:06:55 PM org.jitsi.util.Logger fatal
SEVERE: ICE failed for user Jitsi-Hammer_0. Agent state: Running
Aug 11, 2016 6:06:55 PM org.jitsi.util.Logger fatal
SEVERE: ICE failed for user Jitsi-Hammer_2. Agent state: Running
Aug 11, 2016 6:06:57 PM org.jitsi.util.Logger fatal
SEVERE: ICE failed for user Jitsi-Hammer_3. Agent state: Running
Aug 11, 2016 6:06:57 PM org.jitsi.util.Logger fatal
SEVERE: ICE failed for user Jitsi-Hammer_1. Agent state: Running

Cheers
Shyam Yeduru


#2

Hi,

Hi All

We are getting a error after 25 conferences with 5 Users along AV.
The error mesg is here below: we have increased no of User per
Conference in

root@jitsivb:~# cat /etc/jitsi/videobridge/sip-communicator.properties
org.jitsi.impl.neomedia.transform.CachingTransformer.CACHE_SIZE_STREAMS=200
root@jitsivb:~#

*Error Mesg:

*SEVERE: Jitsi-Hammer_4 : Error during the generation of the IceMediaStream
java.io.IOException: Failed to bind even a single host candidate for
component:Component id=1 parent stream=audio
no local candidates.
no remote candidates. preferredPort=6000 minPort=6000 maxPort=6050

The strategy that jitsi-hammer uses to select ports to bind on doesn't work well with many (>12) hammer instances on one machine.

Each instance will first try to use the 6000-6050 port range and bind 4 ports there. After 12 instances there will be only two ports left, and the next one will fail.

I think the easiest way to work around this (short of using more machines) is to extend the code here to make the values configurable:
https://github.com/jitsi/jitsi-hammer/blob/master/src/org/jitsi/hammer/utils/IceMediaStreamGenerator.java

They you can run with e.g. 12 hammers using MIN=6000, MAX=7000, the next 12 using MIN=7000, MAX=8000, etc.

Regards,
Boris

···

On 11/08/16 07:40, shyam yeduru wrote: