[jitsi-users] Jitsi meet hangs after server up was for several hours


#1

Hi,

I am new to Jitsi meet and I have done some testing with it.

My test setup is an ubuntu server 16.04.2 LTS with
jitsi-meet Version 1.0.1622-1
jitsi-videobridge Version 879-1
jigasi 1.0-130

Installation was done with the quick install guide.

The server is running in an internal test-setup, self signed certificat,
not accessible from internet.
My browser is Firefox 53.

The biggest problem is that after the server is up for several hours (I
assume for more the 12 hours) Jitsi Meet stops working as soon a second
computer connects to a Jitsi Meet session (error text displayed on both
clients: Unfortunately something went wrong ...). This continues as a never
ending loop, so there is no conversation possible. As soon as I restart the
server the system works fine again, several clients can connect and have a
video conversation without problems.

Same problem occurs with Jigasi. A fresh restarted server works fine for
making sip calls with jigasi, the next day the sip call ends in the well
know text "Unfortunately something went wrong ...).

How can I track down the problem? Where to start looking? I have read a lot
in the archive but I could not find a clue.

Chris

PS: Jitsi Meet is really cool stuff. Congratulation to the developers.


#2

Hi,

There is a known issue with leaking file descriptors in jvb, which is
fixed in latest nightlies. After some time running healthchecks jvb
reports an error to jicofo and is removed from the list of currently
available bridges and as this is the last one, there is a problem.
Restarting jvb and jicofo will fix the problem.
You can also update to latest nightly where we believe the problem is
fixed, we will soon push a new version to stable.

Regards
damencho

···

On Fri, May 5, 2017 at 1:53 PM, Me <gtn8vmgddg@gmail.com> wrote:

Hi,

I am new to Jitsi meet and I have done some testing with it.

My test setup is an ubuntu server 16.04.2 LTS with
jitsi-meet Version 1.0.1622-1
jitsi-videobridge Version 879-1
jigasi 1.0-130

Installation was done with the quick install guide.

The server is running in an internal test-setup, self signed certificat, not
accessible from internet.
My browser is Firefox 53.

The biggest problem is that after the server is up for several hours (I
assume for more the 12 hours) Jitsi Meet stops working as soon a second
computer connects to a Jitsi Meet session (error text displayed on both
clients: Unfortunately something went wrong ...). This continues as a never
ending loop, so there is no conversation possible. As soon as I restart the
server the system works fine again, several clients can connect and have a
video conversation without problems.

Same problem occurs with Jigasi. A fresh restarted server works fine for
making sip calls with jigasi, the next day the sip call ends in the well
know text "Unfortunately something went wrong ...).

How can I track down the problem? Where to start looking? I have read a lot
in the archive but I could not find a clue.

Chris

PS: Jitsi Meet is really cool stuff. Congratulation to the developers.

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


#3

Hi,

I have the same problem, I also tryed the nightly build by changing the repository from stable to unstable and update it.
After one week I reinstalled with the old and stable version because all the conference users told me that is much worse than before(with nightly build), lots of reconection issues, video turned off and so on.
So know I'm back with the stable one!

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: Friday, May 5, 2017 10:36 PM
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

Hi,

There is a known issue with leaking file descriptors in jvb, which is fixed in latest nightlies. After some time running healthchecks jvb reports an error to jicofo and is removed from the list of currently available bridges and as this is the last one, there is a problem.
Restarting jvb and jicofo will fix the problem.
You can also update to latest nightly where we believe the problem is fixed, we will soon push a new version to stable.

Regards
damencho

On Fri, May 5, 2017 at 1:53 PM, Me <gtn8vmgddg@gmail.com> wrote:

Hi,

I am new to Jitsi meet and I have done some testing with it.

My test setup is an ubuntu server 16.04.2 LTS with jitsi-meet Version
1.0.1622-1 jitsi-videobridge Version 879-1 jigasi 1.0-130

Installation was done with the quick install guide.

The server is running in an internal test-setup, self signed
certificat, not accessible from internet.
My browser is Firefox 53.

The biggest problem is that after the server is up for several hours
(I assume for more the 12 hours) Jitsi Meet stops working as soon a
second computer connects to a Jitsi Meet session (error text displayed
on both
clients: Unfortunately something went wrong ...). This continues as a
never ending loop, so there is no conversation possible. As soon as I
restart the server the system works fine again, several clients can
connect and have a video conversation without problems.

Same problem occurs with Jigasi. A fresh restarted server works fine
for making sip calls with jigasi, the next day the sip call ends in
the well know text "Unfortunately something went wrong ...).

How can I track down the problem? Where to start looking? I have read
a lot in the archive but I could not find a clue.

Chris

PS: Jitsi Meet is really cool stuff. Congratulation to the developers.

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

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


#4

I tested again with the stable version, all the participants had to close video and rejoined multple times.
Is there any incompatibility between java, chrome version regarding WebRtc implementation?

Chrome 58.0.3029.96
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)

jitsi/stable 2.10.5550-1 amd64
jicofo/stable,now 1.0-320-1 amd64 [installed,automatic]

In logs:

JVB 2017-05-09 12:09:25.416 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965366, rtpTimestamp=996509913, frequencyHz=-1192327, streamHashCode=579999975
JVB 2017-05-09 12:09:25.416 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped because they were late: 0
JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped because they were late by more than MAX_SIZE: 0
JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped in reset(): 1
JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Max size reached: 4
JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Adaptive jitter buffer mode was enabled
JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() Stopping RTPSourceStream.
JVB 2017-05-09 12:09:25.611 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=3758342508, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965606, rtpTimestamp=577679218, frequencyHz=-425512, streamHashCode=579999975
JVB 2017-05-09 12:09:25.629 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965581, rtpTimestamp=2280781405, frequencyHz=-35749, streamHashCode=1019967362
JVB 2017-05-09 12:09:25.629 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965581, rtpTimestamp=297192744, frequencyHz=-1821756, streamHashCode=1422780299

In callstats:

Conference is ongoing.
Some connections failed.

48736345
Failed connection to jitsi, reason: undefined.
f6e4b2df
Failed to access media devices (MediaConfigError).
015c007c
Failed connection to jitsi, reason: undefined.
af827c99
Failed connection to jitsi, reason: undefined.
04cc5949
Failed connection to jitsi, reason: undefined.
acc4c230
Failed connection to jitsi, reason: undefined.
3a90e725
Failed connection to jitsi, reason: undefined.
efea21b3
Failed connection to jitsi, reason: undefined.
aceb4692
Failed connection to jitsi, reason: undefined.
f60c45f1
Failed connection to jitsi, reason: undefined.
084b81f6
Failed connection to jitsi, reason: NegotiationFailure.
2de7b067
Failed connection to jitsi, reason: undefined.
fc37cce5
Failed connection to jitsi, reason: undefined.
7acdcd7c
Failed connection to jitsi, reason: undefined.
87fc4334
Failed connection to jitsi, reason: undefined.
2d4ae61e
Failed connection to jitsi, reason: undefined.
ce732886
Failed connection to jitsi, reason: undefined.
a3764087
Failed connection to jitsi, reason: NegotiationFailure.
3d36b769
Failed connection to jitsi, reason: undefined.
40aeef0b
Failed connection to jitsi, reason: undefined.
ce80f2e8
Failed connection to jitsi, reason: undefined.
cff99cc2
Failed connection to jitsi, reason: undefined.
eef4ea92
Failed connection to jitsi, reason: undefined.

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Stefan Szabo
Sent: Tuesday, May 9, 2017 10:33 AM
To: 'Jitsi Users' <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

Hi,

I have the same problem, I also tryed the nightly build by changing the repository from stable to unstable and update it.
After one week I reinstalled with the old and stable version because all the conference users told me that is much worse than before(with nightly build), lots of reconection issues, video turned off and so on.
So know I'm back with the stable one!

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: Friday, May 5, 2017 10:36 PM
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

Hi,

There is a known issue with leaking file descriptors in jvb, which is fixed in latest nightlies. After some time running healthchecks jvb reports an error to jicofo and is removed from the list of currently available bridges and as this is the last one, there is a problem.
Restarting jvb and jicofo will fix the problem.
You can also update to latest nightly where we believe the problem is fixed, we will soon push a new version to stable.

Regards
damencho

On Fri, May 5, 2017 at 1:53 PM, Me <gtn8vmgddg@gmail.com> wrote:

Hi,

I am new to Jitsi meet and I have done some testing with it.

My test setup is an ubuntu server 16.04.2 LTS with jitsi-meet Version
1.0.1622-1 jitsi-videobridge Version 879-1 jigasi 1.0-130

Installation was done with the quick install guide.

The server is running in an internal test-setup, self signed
certificat, not accessible from internet.
My browser is Firefox 53.

The biggest problem is that after the server is up for several hours
(I assume for more the 12 hours) Jitsi Meet stops working as soon a
second computer connects to a Jitsi Meet session (error text displayed
on both
clients: Unfortunately something went wrong ...). This continues as a
never ending loop, so there is no conversation possible. As soon as I
restart the server the system works fine again, several clients can
connect and have a video conversation without problems.

Same problem occurs with Jigasi. A fresh restarted server works fine
for making sip calls with jigasi, the next day the sip call ends in
the well know text "Unfortunately something went wrong ...).

How can I track down the problem? Where to start looking? I have read
a lot in the archive but I could not find a clue.

Chris

PS: Jitsi Meet is really cool stuff. Congratulation to the developers.

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

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

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


#5

I dont want to be a stress but it seems that even on meet.jit.si is the same problem?
Am I the only one experience bad videoconference, is almost impossibile to keep a conference!

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Stefan Szabo
Sent: Tuesday, May 9, 2017 12:26 PM
To: 'Jitsi Users' <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

I tested again with the stable version, all the participants had to close video and rejoined multple times.
Is there any incompatibility between java, chrome version regarding WebRtc implementation?

Chrome 58.0.3029.96
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)

jitsi/stable 2.10.5550-1 amd64
jicofo/stable,now 1.0-320-1 amd64 [installed,automatic]

In logs:

JVB 2017-05-09 12:09:25.416 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965366, rtpTimestamp=996509913, frequencyHz=-1192327, streamHashCode=579999975 JVB 2017-05-09 12:09:25.416 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped because they were late: 0 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped because they were late by more than MAX_SIZE: 0 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped in reset(): 1 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Max size reached: 4 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Adaptive jitter buffer mode was enabled JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() Stopping RTPSourceStream.
JVB 2017-05-09 12:09:25.611 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=3758342508, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965606, rtpTimestamp=577679218, frequencyHz=-425512, streamHashCode=579999975 JVB 2017-05-09 12:09:25.629 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965581, rtpTimestamp=2280781405, frequencyHz=-35749, streamHashCode=1019967362 JVB 2017-05-09 12:09:25.629 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965581, rtpTimestamp=297192744, frequencyHz=-1821756, streamHashCode=1422780299

In callstats:

Conference is ongoing.
Some connections failed.

48736345
Failed connection to jitsi, reason: undefined.
f6e4b2df
Failed to access media devices (MediaConfigError).
015c007c
Failed connection to jitsi, reason: undefined.
af827c99
Failed connection to jitsi, reason: undefined.
04cc5949
Failed connection to jitsi, reason: undefined.
acc4c230
Failed connection to jitsi, reason: undefined.
3a90e725
Failed connection to jitsi, reason: undefined.
efea21b3
Failed connection to jitsi, reason: undefined.
aceb4692
Failed connection to jitsi, reason: undefined.
f60c45f1
Failed connection to jitsi, reason: undefined.
084b81f6
Failed connection to jitsi, reason: NegotiationFailure.
2de7b067
Failed connection to jitsi, reason: undefined.
fc37cce5
Failed connection to jitsi, reason: undefined.
7acdcd7c
Failed connection to jitsi, reason: undefined.
87fc4334
Failed connection to jitsi, reason: undefined.
2d4ae61e
Failed connection to jitsi, reason: undefined.
ce732886
Failed connection to jitsi, reason: undefined.
a3764087
Failed connection to jitsi, reason: NegotiationFailure.
3d36b769
Failed connection to jitsi, reason: undefined.
40aeef0b
Failed connection to jitsi, reason: undefined.
ce80f2e8
Failed connection to jitsi, reason: undefined.
cff99cc2
Failed connection to jitsi, reason: undefined.
eef4ea92
Failed connection to jitsi, reason: undefined.

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Stefan Szabo
Sent: Tuesday, May 9, 2017 10:33 AM
To: 'Jitsi Users' <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

Hi,

I have the same problem, I also tryed the nightly build by changing the repository from stable to unstable and update it.
After one week I reinstalled with the old and stable version because all the conference users told me that is much worse than before(with nightly build), lots of reconection issues, video turned off and so on.
So know I'm back with the stable one!

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: Friday, May 5, 2017 10:36 PM
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

Hi,

There is a known issue with leaking file descriptors in jvb, which is fixed in latest nightlies. After some time running healthchecks jvb reports an error to jicofo and is removed from the list of currently available bridges and as this is the last one, there is a problem.
Restarting jvb and jicofo will fix the problem.
You can also update to latest nightly where we believe the problem is fixed, we will soon push a new version to stable.

Regards
damencho

On Fri, May 5, 2017 at 1:53 PM, Me <gtn8vmgddg@gmail.com> wrote:

Hi,

I am new to Jitsi meet and I have done some testing with it.

My test setup is an ubuntu server 16.04.2 LTS with jitsi-meet Version
1.0.1622-1 jitsi-videobridge Version 879-1 jigasi 1.0-130

Installation was done with the quick install guide.

The server is running in an internal test-setup, self signed
certificat, not accessible from internet.
My browser is Firefox 53.

The biggest problem is that after the server is up for several hours
(I assume for more the 12 hours) Jitsi Meet stops working as soon a
second computer connects to a Jitsi Meet session (error text displayed
on both
clients: Unfortunately something went wrong ...). This continues as a
never ending loop, so there is no conversation possible. As soon as I
restart the server the system works fine again, several clients can
connect and have a video conversation without problems.

Same problem occurs with Jigasi. A fresh restarted server works fine
for making sip calls with jigasi, the next day the sip call ends in
the well know text "Unfortunately something went wrong ...).

How can I track down the problem? Where to start looking? I have read
a lot in the archive but I could not find a clue.

Chris

PS: Jitsi Meet is really cool stuff. Congratulation to the developers.

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

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

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

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


#6

Hi,

Can anyone tell me why I have this in logs?

JVB 2017-05-09 11:13:23.022 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=1213668848, systemTime=Tue May 09 11:13:23 EEST 2017, systemTimeMs=1494317603209, rtpTimestamp=3272654229, frequencyHz=0, streamHashCode=1666671387

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Stefan Szabo
Sent: Tuesday, May 9, 2017 5:57 PM
To: 'Jitsi Users' <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

I dont want to be a stress but it seems that even on meet.jit.si is the same problem?
Am I the only one experience bad videoconference, is almost impossibile to keep a conference!

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Stefan Szabo
Sent: Tuesday, May 9, 2017 12:26 PM
To: 'Jitsi Users' <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

I tested again with the stable version, all the participants had to close video and rejoined multple times.
Is there any incompatibility between java, chrome version regarding WebRtc implementation?

Chrome 58.0.3029.96
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)

jitsi/stable 2.10.5550-1 amd64
jicofo/stable,now 1.0-320-1 amd64 [installed,automatic]

In logs:

JVB 2017-05-09 12:09:25.416 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965366, rtpTimestamp=996509913, frequencyHz=-1192327, streamHashCode=579999975 JVB 2017-05-09 12:09:25.416 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped because they were late: 0 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped because they were late by more than MAX_SIZE: 0 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Packets dropped in reset(): 1 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Max size reached: 4 JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() net.sf.fmj.media.rtp.RTPSourceStream Adaptive jitter buffer mode was enabled JVB 2017-05-09 12:09:25.417 INFO: [275189] net.sf.fmj.media.Log.info() Stopping RTPSourceStream.
JVB 2017-05-09 12:09:25.611 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=3758342508, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965606, rtpTimestamp=577679218, frequencyHz=-425512, streamHashCode=579999975 JVB 2017-05-09 12:09:25.629 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965581, rtpTimestamp=2280781405, frequencyHz=-35749, streamHashCode=1019967362 JVB 2017-05-09 12:09:25.629 WARNING: [275201] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=660562721, systemTime=Tue May 09 12:09:25 EEST 2017, systemTimeMs=1494320965581, rtpTimestamp=297192744, frequencyHz=-1821756, streamHashCode=1422780299

In callstats:

Conference is ongoing.
Some connections failed.

48736345
Failed connection to jitsi, reason: undefined.
f6e4b2df
Failed to access media devices (MediaConfigError).
015c007c
Failed connection to jitsi, reason: undefined.
af827c99
Failed connection to jitsi, reason: undefined.
04cc5949
Failed connection to jitsi, reason: undefined.
acc4c230
Failed connection to jitsi, reason: undefined.
3a90e725
Failed connection to jitsi, reason: undefined.
efea21b3
Failed connection to jitsi, reason: undefined.
aceb4692
Failed connection to jitsi, reason: undefined.
f60c45f1
Failed connection to jitsi, reason: undefined.
084b81f6
Failed connection to jitsi, reason: NegotiationFailure.
2de7b067
Failed connection to jitsi, reason: undefined.
fc37cce5
Failed connection to jitsi, reason: undefined.
7acdcd7c
Failed connection to jitsi, reason: undefined.
87fc4334
Failed connection to jitsi, reason: undefined.
2d4ae61e
Failed connection to jitsi, reason: undefined.
ce732886
Failed connection to jitsi, reason: undefined.
a3764087
Failed connection to jitsi, reason: NegotiationFailure.
3d36b769
Failed connection to jitsi, reason: undefined.
40aeef0b
Failed connection to jitsi, reason: undefined.
ce80f2e8
Failed connection to jitsi, reason: undefined.
cff99cc2
Failed connection to jitsi, reason: undefined.
eef4ea92
Failed connection to jitsi, reason: undefined.

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Stefan Szabo
Sent: Tuesday, May 9, 2017 10:33 AM
To: 'Jitsi Users' <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

Hi,

I have the same problem, I also tryed the nightly build by changing the repository from stable to unstable and update it.
After one week I reinstalled with the old and stable version because all the conference users told me that is much worse than before(with nightly build), lots of reconection issues, video turned off and so on.
So know I'm back with the stable one!

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: Friday, May 5, 2017 10:36 PM
To: Jitsi Users <users@jitsi.org>
Subject: Re: [jitsi-users] Jitsi meet hangs after server up was for several hours

Hi,

There is a known issue with leaking file descriptors in jvb, which is fixed in latest nightlies. After some time running healthchecks jvb reports an error to jicofo and is removed from the list of currently available bridges and as this is the last one, there is a problem.
Restarting jvb and jicofo will fix the problem.
You can also update to latest nightly where we believe the problem is fixed, we will soon push a new version to stable.

Regards
damencho

On Fri, May 5, 2017 at 1:53 PM, Me <gtn8vmgddg@gmail.com> wrote:

Hi,

I am new to Jitsi meet and I have done some testing with it.

My test setup is an ubuntu server 16.04.2 LTS with jitsi-meet Version
1.0.1622-1 jitsi-videobridge Version 879-1 jigasi 1.0-130

Installation was done with the quick install guide.

The server is running in an internal test-setup, self signed
certificat, not accessible from internet.
My browser is Firefox 53.

The biggest problem is that after the server is up for several hours
(I assume for more the 12 hours) Jitsi Meet stops working as soon a
second computer connects to a Jitsi Meet session (error text displayed
on both
clients: Unfortunately something went wrong ...). This continues as a
never ending loop, so there is no conversation possible. As soon as I
restart the server the system works fine again, several clients can
connect and have a video conversation without problems.

Same problem occurs with Jigasi. A fresh restarted server works fine
for making sip calls with jigasi, the next day the sip call ends in
the well know text "Unfortunately something went wrong ...).

How can I track down the problem? Where to start looking? I have read
a lot in the archive but I could not find a clue.

Chris

PS: Jitsi Meet is really cool stuff. Congratulation to the developers.

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

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

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

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

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