[jitsi-dev] Fwd: [jitsi-meet] Self-hosted : video crash after startup (#308)


#1

Forwarding a message from our issue tracker as a reminder.

A link to this thread will be added to github as a follow up, so please respond and comment here.

Thanks,
Yana

p.s. We’re trying to keep all questions and discussions on the mailing list and only create issues for identified problems.

···

Begin forwarded message:

From: Kidav <notifications@github.com>
Subject: Re: [jitsi-meet] Self-hosted : video crash after startup (#308)
Date: 18 June 2015 12:50:32 pm GMT-5
To: jitsi/jitsi-meet <jitsi-meet@noreply.github.com>
Reply-To: jitsi/jitsi-meet <reply+0031d0a469ee94a18b095befaca3f21f1cc0ec5a19cc675b92cf00000001119ac6e892a169ce053e219d@reply.github.com>

I am also spent some time for this issue and found this errors in log of jvb

Sctp send error: : Resource temporarily unavailable
SEVERE: [29] org.jitsi.videobridge.Conference.error() Failed to send message on data channel.
java.io.IOException: Failed to send the data
jicofo.log

SEVERE: [52] org.jitsi.protocol.xmpp.AbstractOperationSetJingle.initiateSession().135 Timeout waiting for session-accept from 1122334@conference.meet.jit.si/7217db9a
INFO: [52] org.jitsi.jicofo.JitsiMeetConference.discoverFeaturesAndInvite().588 Expiring 1122334@conference.meet.jit.si/7217db9a channels - participant has left
SEVERE: [55] org.jitsi.protocol.xmpp.AbstractOperationSetJingle.initiateSession().135 Timeout waiting for session-accept from 1122334@conference.meet.jit.si/0936319a
INFO: [55] org.jitsi.jicofo.JitsiMeetConference.discoverFeaturesAndInvite().588 Expiring 1122334@conference.meet.jit.si/0936319a channels - participant has left
so I suppose for quick workaround you can downgrade jicofo to 1.0-68-1 (that helped me)


Reply to this email directly or view it on GitHub <https://github.com/jitsi/jitsi-meet/issues/308#issuecomment-113235058>.


#2

I'm having a similar problem on my setup (also built following the quick install guide).

I notice that after a certain peer joins all other peers that join afterwards won't get the streams or get their sent over as if the bridge was in a bad state (all other new sessions follow the same symptom).

I normally have to restart the services to be able to get it back in working state. I'm not sure if it has anything to do with the peers not being able to communicate with the bridge (over the udp ports or tcp fallback) and that leaving the bridge in a weird state. I had originally only opened a few udp ports in my servers firewall (10000-10010) to test out and noticed this happening quite frequently. I then opened up the whole default range 10000-20000 and it seems to be better now but I haven't confirmed that is what was causing the weird state that had me restart the bridge so often.

···

Sent from my iPhone

On Jul 21, 2015, at 4:09 PM, Yana Stamcheva <yana@jitsi.org> wrote:

Forwarding a message from our issue tracker as a reminder.

A link to this thread will be added to github as a follow up, so please respond and comment here.

Thanks,
Yana

p.s. We’re trying to keep all questions and discussions on the mailing list and only create issues for identified problems.

Begin forwarded message:

From: Kidav <notifications@github.com>
Subject: Re: [jitsi-meet] Self-hosted : video crash after startup (#308)
Date: 18 June 2015 12:50:32 pm GMT-5
To: jitsi/jitsi-meet <jitsi-meet@noreply.github.com>
Reply-To: jitsi/jitsi-meet <reply+0031d0a469ee94a18b095befaca3f21f1cc0ec5a19cc675b92cf00000001119ac6e892a169ce053e219d@reply.github.com>

I am also spent some time for this issue and found this errors in log of jvb

Sctp send error: : Resource temporarily unavailable
SEVERE: [29] org.jitsi.videobridge.Conference.error() Failed to send message on data channel.
java.io.IOException: Failed to send the data
jicofo.log

SEVERE: [52] org.jitsi.protocol.xmpp.AbstractOperationSetJingle.initiateSession().135 Timeout waiting for session-accept from 1122334@conference.meet.jit.si/7217db9a
INFO: [52] org.jitsi.jicofo.JitsiMeetConference.discoverFeaturesAndInvite().588 Expiring 1122334@conference.meet.jit.si/7217db9a channels - participant has left
SEVERE: [55] org.jitsi.protocol.xmpp.AbstractOperationSetJingle.initiateSession().135 Timeout waiting for session-accept from 1122334@conference.meet.jit.si/0936319a
INFO: [55] org.jitsi.jicofo.JitsiMeetConference.discoverFeaturesAndInvite().588 Expiring 1122334@conference.meet.jit.si/0936319a channels - participant has left
so I suppose for quick workaround you can downgrade jicofo to 1.0-68-1 (that helped me)


Reply to this email directly or view it on GitHub.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev