[jitsi-dev] Failed to allocate channels - no bridge configured


#1

I also found the following sever in the jicofo.log :

Jicofo 2017-03-07 11:42:07.649 SEVERE: [96] org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.checkIfDisposed().148 Not doing expireConference - bridge not initialized
Jicofo 2017-03-07 11:42:07.687 SEVERE: [98] impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().520 Invalid DiscoverInfo for www.baidu.com<http://www.baidu.com/>#z1aBBLuF0kcC4cvtqaI3m4YQdkI=: org.jivesoftware.smackx.packet.DiscoverInfo@e60da346

···

On Mar 6, 2017, at 12:20, Daniel Bareiro <daniel-listas@gmx.net<mailto:daniel-listas@gmx.net>> wrote:

On 06/03/17 05:23, Saúl Ibarra Corretgé wrote:

On Mar 6, 2017, at 04:44, yicheng li <rtjava@hotmail.com<mailto:rtjava@hotmail.com>> wrote:

it seems that , if I restart jicofo with the following command “/etc/init.d/jicofo restart” . the problem
is resolved.

but this is not the final solution.

When you restart the JVB you should see it coming up on the Jicofo logs. Is this not happening for you? Can
you reproduce this consistently?

Hi, Saúl.

It's a good surprise to read you here as well as in Asterisk-es :slight_smile:

:slight_smile:

As I mentioned a few days ago in another message [1], I am also
observing this issue. Restarting Jicofo resolves it but is not a
solution. It does not seem to be something that is linked to the problem
with the open descriptors, as I said in that message.

Ah, sorry I must have missed that part.

Is there anything we can do to avoid this?

First we need to understand why the JVB gets disconnected. Can you see anything meaningful in the JVB of Jicofo logs?

Cheers,

--
Saúl

------------------------------

Message: 3
Date: Mon, 6 Mar 2017 14:00:26 -0300
From: Daniel Bareiro <daniel-listas@gmx.net<mailto:daniel-listas@gmx.net>>
To: dev@jitsi.org<mailto:dev@jitsi.org>
Subject: Re: [jitsi-dev] Failed to allocate channels - no bridge
configured
Message-ID: <236bd898-95ba-384f-7aaf-1a5f191c4bb2@gmx.net<mailto:236bd898-95ba-384f-7aaf-1a5f191c4bb2@gmx.net>>
Content-Type: text/plain; charset="utf-8"

Hi, Saúl.

Thanks for your reply.

On 06/03/17 13:41, Saúl Ibarra Corretgé wrote:

Is there anything we can do to avoid this?

First we need to understand why the JVB gets disconnected. Can you see
anything meaningful in the JVB of Jicofo logs?

In that moment I found this in the Jicofo's log:

-----------------------------------------------------------------------
Jcofo 2017-02-13 13:05:43.071 SEVERE: [92]
org.jitsi.jicofo.ChannelAllocator.log() Failed to allocate channels for
inmobiliariaortega@conference.conf.opcion-libre.com.ar<mailto:inmobiliariaortega@conference.conf.opcion-libre.com.ar>/4ce8717c
net.java.sip.communicator.service.protocol.OperationFailedException:
Failed to allocate channels - no bridge configured
       at
org.jitsi.jicofo.ChannelAllocator.allocateChannels(ChannelAllocator.java:372)
       at
org.jitsi.jicofo.ChannelAllocator.createOffer(ChannelAllocator.java:307)
       at
org.jitsi.jicofo.ChannelAllocator.discoverFeaturesAndInvite(ChannelAllocator.java:166)
       at org.jitsi.jicofo.ChannelAllocator.run(ChannelAllocator.java:135)
       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)
Jicofo 2017-02-13 13:05:43.080 SEVERE: [92]
org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.checkIfDisposed().148
Not doing expireConference - bridge not initialize
-----------------------------------------------------------------------

Now the log has been rotated enough to not have the logs in jvb.log for
that temporary window. Do those records of Jicofo help in anything?

Yicheng Li, can you provide us the Jitsi videobridge or Jicofo logs by
the time you had this issue?

Kind regards,
Daniel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.jitsi.org/pipermail/dev/attachments/20170306/11cd910c/attachment.sig>

------------------------------

Subject: Digest Footer

_______________________________________________
dev mailing list
dev@jitsi.org<mailto:dev@jitsi.org>
http://lists.jitsi.org/mailman/listinfo/dev

------------------------------

End of dev Digest, Vol 48, Issue 28
***********************************


#2

Hi, Yicheng.

I also found the following sever in the jicofo.log :

Jicofo 2017-03-07 11:42:07.649 SEVERE: [96]
org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.checkIfDisposed().148
Not doing expireConference - bridge not initialized
Jicofo 2017-03-07 11:42:07.687 SEVERE: [98]
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().520
Invalid DiscoverInfo for www.baidu.com
<http://www.baidu.com/>#z1aBBLuF0kcC4cvtqaI3m4YQdkI=:
org.jivesoftware.smackx.packet.DiscoverInfo@e60da346

The line with the "Not doing expireConference - bridge not initialized"
is something that I also saw in that moment in my log of Jicofo. And in
jvb.log have you found any errors for that same temporary window where
the issue occurred?

Saul, this and the log that I mentioned in an previous message in this
thread is helpful?

Thanks in advance.

Kind regards,
Daniel

···

On 07/03/17 06:17, yicheng li wrote:


#3

Hi,

So the thing is that jicofo is health checking jvb and at some point
if that fails, jicofo remove jvb from its list of active jvbs.
We need to check the actual jvb error when that happend, it can be few
days before you see "no bridge configured". We have seen a leak in a
idle jvb which is just been health checked and we think we had fixed
it. I was experiencing this problem and after the fix I haven't seen
this.

Regards
damencho

···

On Fri, Mar 10, 2017 at 9:01 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

Hi, Yicheng.

On 07/03/17 06:17, yicheng li wrote:

I also found the following sever in the jicofo.log :

Jicofo 2017-03-07 11:42:07.649 SEVERE: [96]
org.jitsi.impl.protocol.xmpp.colibri.ColibriConferenceImpl.checkIfDisposed().148
Not doing expireConference - bridge not initialized
Jicofo 2017-03-07 11:42:07.687 SEVERE: [98]
impl.protocol.jabber.ScServiceDiscoveryManager.discoverInfo().520
Invalid DiscoverInfo for www.baidu.com
<http://www.baidu.com/>#z1aBBLuF0kcC4cvtqaI3m4YQdkI=:
org.jivesoftware.smackx.packet.DiscoverInfo@e60da346

The line with the "Not doing expireConference - bridge not initialized"
is something that I also saw in that moment in my log of Jicofo. And in
jvb.log have you found any errors for that same temporary window where
the issue occurred?

Saul, this and the log that I mentioned in an previous message in this
thread is helpful?

Thanks in advance.

Kind regards,
Daniel

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


#4

Hi,

Hi, Damian.

So the thing is that jicofo is health checking jvb and at some point
if that fails, jicofo remove jvb from its list of active jvbs.
We need to check the actual jvb error when that happend, it can be few
days before you see "no bridge configured". We have seen a leak in a
idle jvb which is just been health checked and we think we had fixed
it. I was experiencing this problem and after the fix I haven't seen
this.

Thanks for your reply.

Here I am using the stable branch of Jitsi Meet. The fix that you
mention is applied in nightly or also in stable?

Kind regards,
Daniel

···

On 10/03/17 12:29, Damian Minkov wrote:


#5

Hi,

Hi again, Damian.

So the thing is that jicofo is health checking jvb and at some point
if that fails, jicofo remove jvb from its list of active jvbs.
We need to check the actual jvb error when that happend, it can be few
days before you see "no bridge configured". We have seen a leak in a
idle jvb which is just been health checked and we think we had fixed
it. I was experiencing this problem and after the fix I haven't seen
this.

I was thinking of making a Nagios plugin to check if the bridge is
connected. Is there any way to find out this other than through the logs?

Kind regards,
Daniel

···

On 10/03/17 12:29, Damian Minkov wrote:


#6

Hi,

The fix is https://github.com/jitsi/jitsi-videobridge/commit/17634b97d503b7050a68cf6601caeb53249652aa
in the bridge and is coming from this:
https://github.com/jitsi/ice4j/commit/7c63d5202c3ab453028eefa2a6f81cd2f1f70ca3
This went into version 882 in the bridge. And the stable one is 879.
So no :frowning: it is in nightly. We will be updating stable soon I hope.
There is a sctp crash we are trying to catch on the jvb side, which is
slowing down this process at the moment.

Regards
damencho

···

On Fri, Mar 10, 2017 at 10:39 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 10/03/17 12:29, Damian Minkov wrote:

Hi,

Hi, Damian.

So the thing is that jicofo is health checking jvb and at some point
if that fails, jicofo remove jvb from its list of active jvbs.
We need to check the actual jvb error when that happend, it can be few
days before you see "no bridge configured". We have seen a leak in a
idle jvb which is just been health checked and we think we had fixed
it. I was experiencing this problem and after the fix I haven't seen
this.

Thanks for your reply.

Here I am using the stable branch of Jitsi Meet. The fix that you
mention is applied in nightly or also in stable?

Kind regards,
Daniel

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


#7

Hi,

Hi, Damian.

The fix is https://github.com/jitsi/jitsi-videobridge/commit/17634b97d503b7050a68cf6601caeb53249652aa
in the bridge and is coming from this:
https://github.com/jitsi/ice4j/commit/7c63d5202c3ab453028eefa2a6f81cd2f1f70ca3
This went into version 882 in the bridge. And the stable one is 879.
So no :frowning: it is in nightly. We will be updating stable soon I hope.
There is a sctp crash we are trying to catch on the jvb side, which is
slowing down this process at the moment.

I see. Thanks for confirm. Please let us know when there is an update.

I'm not sure if it will be related to the issue we're talking about, but
reviewing in my Jicofo logs I found the following:

···

On 10/03/17 14:37, Damian Minkov wrote:

---------------------------------------------------------------------------
root@conference:/var/log/jitsi# tail -F jicofo.log
Jicofo 2017-03-06 17:34:03.925 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().265 New
component discovered: auth.conf.opcion-libre.com.ar,
Version[Prosody(0.9.12,Linux)@-71270384]
Jicofo 2017-03-06 17:34:03.925 INFO: [16]
org.jitsi.jicofo.JitsiMeetServices.newNodeDiscovered().244 Detected XMPP
server version: Version[Prosody(0.9.12,Linux)@-71270384]
Jicofo 2017-03-06 17:34:03.942 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().265 New
component discovered: focus.conf.opcion-libre.com.ar, null
Jicofo 2017-03-06 17:34:04.454 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().265 New
component discovered: jitsi-videobridge.conf.opcion-libre.com.ar,
Version[JVB(0.1.879,Linux)@-1445256601]
Jicofo 2017-03-06 17:34:04.455 INFO: [16]
org.jitsi.jicofo.BridgeSelector.addJvbAddress().147 Added videobridge:
jitsi-videobridge.conf.opcion-libre.com.ar v:
Version[JVB(0.1.879,Linux)@-1445256601]
Jicofo 2017-03-06 17:34:04.455 WARNING: [16]
org.jitsi.jicofo.BridgeSelector.addJvbAddress().159 No pub-sub node
mapped for jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-06 17:34:04.473 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.scheduleRediscovery().188 Services
re-discovery interval: 30000
Jicofo 2017-03-06 17:34:04.484 INFO: [16]
org.jitsi.jicofo.FocusManager.log() XMPP provider reg state:
RegistrationState=Registered
Jicofo 2017-03-06 17:34:04.485 INFO: [16]
org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() XMPP provider
Jabber:focus@auth.conf.opcion-libre.com.ar/focus186517940618@localhost
connected (JID: focus@auth.conf.opcion-libre.com.ar/focus186517940618)
Jicofo 2017-03-06 17:34:04.488 INFO: [45]
org.jitsi.jicofo.JvbDoctor.log() Scheduled health-check task for:
jitsi-videobridge.conf.opcion-libre.com.ar
tail: jicofo.log: file truncated
Jicofo 2017-03-08 09:03:54.641 WARNING: [71]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 119ms to process: <iq
id="ARuO2-71105" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
tail: jicofo.log: file truncated
Jicofo 2017-03-09 14:15:29.603 WARNING: [42]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 674ms to process: <iq
id="ARuO2-123650" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
Jicofo 2017-03-09 14:15:39.589 WARNING: [49]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 504ms to process: <iq
id="ARuO2-123654" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
Jicofo 2017-03-09 14:16:29.624 WARNING: [80]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 113ms to process: <iq
id="ARuO2-123681" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
Jicofo 2017-03-09 17:03:38.145 INFO: [46]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().297 Component
went offline: jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-09 17:03:38.291 INFO: [46]
org.jitsi.jicofo.BridgeSelector.removeJvbAddress().192 Removing JVB:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-09 17:03:38.507 INFO: [45]
org.jitsi.jicofo.JvbDoctor.log() Stopping health-check task for:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-09 17:03:38.539 INFO: [81]
org.jitsi.jicofo.JvbDoctor.log() Health check task cancelled for:
jitsi-videobridge.conf.opcion-libre.com.ar
---------------------------------------------------------------------------

It seems that for some reason, the Health check have been suspended.

Checking the jvb.log I also found the following for the same time window:

---------------------------------------------------------------------------
JVB 2017-03-09 17:03:24.554 INFO: [24]
org.jitsi.videobridge.xmpp.ComponentImpl.log() SENT: <iq
id=“ARuO2-128689” to=“focus@auth.conf.opcion-libre.com.ar/focus186517940
618” from=“jitsi-videobridge.conf.opcion-libre.com.ar” type=“result”/>
JVB 2017-03-09 17:03:34.068 INFO: [141]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq
id=“fqD5i-25735” type=“result” to=“jitsi-videobridge.conf.opcion-libre.
com.ar” from=“conf.opcion-libre.com.ar”/>
JVB 2017-03-09 17:03:34.483 INFO: [232]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq type=“get”
to=“jitsi-videobridge.conf.opcion-libre.com.ar” from=“focus@
auth.conf.opcion-libre.com.ar/focus186517940618”
id=“ARuO2-128692”><healthcheck
xmlns=“http://jitsi.org/protocol/healthcheck”/></iq>
JVB 2017-03-09 17:03:34.484 INFO: [232]
org.jitsi.videobridge.Videobridge.log() CAT=stat
create_conf,conf_id=9fb5c7e070ec87d1
conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff540085517, pid=433, tid=140690701465344
#
# JRE version: OpenJDK Runtime Environment (7.0_121) (build 1.7.0_121-b00)
# Java VM: OpenJDK 64-Bit Server VM (24.121-b00 mixed mode linux-amd64
compressed oops)
# Derivative: IcedTea 2.6.8
# Distribution: Debian GNU/Linux 8.7 (jessie), package 7u121-2.6.8-2~deb8u1
# Problematic frame:
# C 0x00007ff540085517
#
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try “ulimit -c unlimited” before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid433.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
---------------------------------------------------------------------------

This seems to suggest rather that the checks were canceled due to some
problem with OpenJDK. If I can provide more information, please let me
know (Maybe the /tmp/hs_err_pid433.log file).

Kind regards,
Daniel


#8

Hi,

You can just health check jicofo curl
http://localhost:8888/about/health?list_jvb=true. It will report 200
if jicofo thinks it is healthy and has at least one healthy jvb
connected to it.

Cheers
damencho

···

On Mon, Mar 20, 2017 at 9:15 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 10/03/17 12:29, Damian Minkov wrote:

Hi,

Hi again, Damian.

So the thing is that jicofo is health checking jvb and at some point
if that fails, jicofo remove jvb from its list of active jvbs.
We need to check the actual jvb error when that happend, it can be few
days before you see "no bridge configured". We have seen a leak in a
idle jvb which is just been health checked and we think we had fixed
it. I was experiencing this problem and after the fix I haven't seen
this.

I was thinking of making a Nagios plugin to check if the bridge is
connected. Is there any way to find out this other than through the logs?

Kind regards,
Daniel

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


#9

Hi,

Hi, Damian.

You can just health check jicofo curl
http://localhost:8888/about/health?list_jvb=true. It will report 200
if jicofo thinks it is healthy and has at least one healthy jvb
connected to it.

Great! Thank you!

I have noticed that in the morning of today, when running some
cron.daily standard tasks, it seems the check had a timeout and then the
bridge was removed. Maybe because the I/O wait on those tasks.

Here is what I found in the Jicofo log:

···

On 20/03/17 11:40, Damian Minkov wrote:

-----------------------------------------------------------------------
Jicofo 2017-03-21 06:25:46.495 WARNING: [16]
org.jitsi.jicofo.JvbDoctor.log()
jitsi-videobridge.conf.opcion-libre.com.ar health-check timed out, but
will give it anothe
r try after: 5000
Jicofo 2017-03-21 06:25:52.939 SEVERE: [35]
org.jitsi.xmpp.component.ComponentBase.run().629 Ping timeout for ID:
3li7c-76572
Jicofo 2017-03-21 06:26:07.903 WARNING: [16]
org.jitsi.jicofo.JvbDoctor.log() Health check failed on:
jitsi-videobridge.conf.opcion-libre.com.ar error: timeout
Jicofo 2017-03-21 06:26:07.908 INFO: [43]
org.jitsi.jicofo.BridgeSelector.removeJvbAddress().192 Removing JVB:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-21 06:26:07.908 INFO: [43]
org.jitsi.jicofo.JvbDoctor.log() Stopping health-check task for:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-21 06:26:07.911 INFO: [16]
org.jitsi.jicofo.JvbDoctor.log() Health check task cancelled for:
jitsi-videobridge.conf.opcion-libre.com.ar
-----------------------------------------------------------------------

Is it possible?

On the other hand, do you know if these messages displayed in the Jicofo
log may be related to the Nagios checks?

-----------------------------------------------------------------------
Jicofo 2017-03-21 13:59:40.406 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:09:40.517 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:29:40.741 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:39:39.865 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:14:38.227 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:19:38.243 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:24:38.260 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:29:38.273 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:34:38.286 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
-----------------------------------------------------------------------

Thanks for your time.

Kind regards,
Daniel


#10

When you see that in jicofo, can you check the same timestamps in
jvb.log. It should complain about not able to create file or something
like that.

···

On Fri, Mar 10, 2017 at 12:06 PM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 10/03/17 14:37, Damian Minkov wrote:

Hi,

Hi, Damian.

The fix is https://github.com/jitsi/jitsi-videobridge/commit/17634b97d503b7050a68cf6601caeb53249652aa
in the bridge and is coming from this:
https://github.com/jitsi/ice4j/commit/7c63d5202c3ab453028eefa2a6f81cd2f1f70ca3
This went into version 882 in the bridge. And the stable one is 879.
So no :frowning: it is in nightly. We will be updating stable soon I hope.
There is a sctp crash we are trying to catch on the jvb side, which is
slowing down this process at the moment.

I see. Thanks for confirm. Please let us know when there is an update.

I'm not sure if it will be related to the issue we're talking about, but
reviewing in my Jicofo logs I found the following:

---------------------------------------------------------------------------
root@conference:/var/log/jitsi# tail -F jicofo.log
Jicofo 2017-03-06 17:34:03.925 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().265 New
component discovered: auth.conf.opcion-libre.com.ar,
Version[Prosody(0.9.12,Linux)@-71270384]
Jicofo 2017-03-06 17:34:03.925 INFO: [16]
org.jitsi.jicofo.JitsiMeetServices.newNodeDiscovered().244 Detected XMPP
server version: Version[Prosody(0.9.12,Linux)@-71270384]
Jicofo 2017-03-06 17:34:03.942 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().265 New
component discovered: focus.conf.opcion-libre.com.ar, null
Jicofo 2017-03-06 17:34:04.454 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().265 New
component discovered: jitsi-videobridge.conf.opcion-libre.com.ar,
Version[JVB(0.1.879,Linux)@-1445256601]
Jicofo 2017-03-06 17:34:04.455 INFO: [16]
org.jitsi.jicofo.BridgeSelector.addJvbAddress().147 Added videobridge:
jitsi-videobridge.conf.opcion-libre.com.ar v:
Version[JVB(0.1.879,Linux)@-1445256601]
Jicofo 2017-03-06 17:34:04.455 WARNING: [16]
org.jitsi.jicofo.BridgeSelector.addJvbAddress().159 No pub-sub node
mapped for jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-06 17:34:04.473 INFO: [16]
org.jitsi.jicofo.ComponentsDiscovery.scheduleRediscovery().188 Services
re-discovery interval: 30000
Jicofo 2017-03-06 17:34:04.484 INFO: [16]
org.jitsi.jicofo.FocusManager.log() XMPP provider reg state:
RegistrationState=Registered
Jicofo 2017-03-06 17:34:04.485 INFO: [16]
org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() XMPP provider
Jabber:focus@auth.conf.opcion-libre.com.ar/focus186517940618@localhost
connected (JID: focus@auth.conf.opcion-libre.com.ar/focus186517940618)
Jicofo 2017-03-06 17:34:04.488 INFO: [45]
org.jitsi.jicofo.JvbDoctor.log() Scheduled health-check task for:
jitsi-videobridge.conf.opcion-libre.com.ar
tail: jicofo.log: file truncated
Jicofo 2017-03-08 09:03:54.641 WARNING: [71]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 119ms to process: <iq
id="ARuO2-71105" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
tail: jicofo.log: file truncated
Jicofo 2017-03-09 14:15:29.603 WARNING: [42]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 674ms to process: <iq
id="ARuO2-123650" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
Jicofo 2017-03-09 14:15:39.589 WARNING: [49]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 504ms to process: <iq
id="ARuO2-123654" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
Jicofo 2017-03-09 14:16:29.624 WARNING: [80]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 113ms to process: <iq
id="ARuO2-123681" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
Jicofo 2017-03-09 17:03:38.145 INFO: [46]
org.jitsi.jicofo.ComponentsDiscovery.discoverServices().297 Component
went offline: jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-09 17:03:38.291 INFO: [46]
org.jitsi.jicofo.BridgeSelector.removeJvbAddress().192 Removing JVB:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-09 17:03:38.507 INFO: [45]
org.jitsi.jicofo.JvbDoctor.log() Stopping health-check task for:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-09 17:03:38.539 INFO: [81]
org.jitsi.jicofo.JvbDoctor.log() Health check task cancelled for:
jitsi-videobridge.conf.opcion-libre.com.ar
---------------------------------------------------------------------------

It seems that for some reason, the Health check have been suspended.

Checking the jvb.log I also found the following for the same time window:

---------------------------------------------------------------------------
JVB 2017-03-09 17:03:24.554 INFO: [24]
org.jitsi.videobridge.xmpp.ComponentImpl.log() SENT: <iq
id=“ARuO2-128689” to=“focus@auth.conf.opcion-libre.com.ar/focus186517940
618” from=“jitsi-videobridge.conf.opcion-libre.com.ar” type=“result”/>
JVB 2017-03-09 17:03:34.068 INFO: [141]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq
id=“fqD5i-25735” type=“result” to=“jitsi-videobridge.conf.opcion-libre.
com.ar” from=“conf.opcion-libre.com.ar”/>
JVB 2017-03-09 17:03:34.483 INFO: [232]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq type=“get”
to=“jitsi-videobridge.conf.opcion-libre.com.ar” from=“focus@
auth.conf.opcion-libre.com.ar/focus186517940618”
id=“ARuO2-128692”><healthcheck
xmlns=“http://jitsi.org/protocol/healthcheck”/></iq>
JVB 2017-03-09 17:03:34.484 INFO: [232]
org.jitsi.videobridge.Videobridge.log() CAT=stat
create_conf,conf_id=9fb5c7e070ec87d1
conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff540085517, pid=433, tid=140690701465344
#
# JRE version: OpenJDK Runtime Environment (7.0_121) (build 1.7.0_121-b00)
# Java VM: OpenJDK 64-Bit Server VM (24.121-b00 mixed mode linux-amd64
compressed oops)
# Derivative: IcedTea 2.6.8
# Distribution: Debian GNU/Linux 8.7 (jessie), package 7u121-2.6.8-2~deb8u1
# Problematic frame:
# C 0x00007ff540085517
#
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try “ulimit -c unlimited” before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid433.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
---------------------------------------------------------------------------

This seems to suggest rather that the checks were canceled due to some
problem with OpenJDK. If I can provide more information, please let me
know (Maybe the /tmp/hs_err_pid433.log file).

Kind regards,
Daniel

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


#11

Hi, Damian.

···

On 10/03/17 15:11, Damian Minkov wrote:

When you see that in jicofo, can you check the same timestamps in
jvb.log. It should complain about not able to create file or something
like that.

Yes, I found what I mentioned in an previous email of this thread:

---------------------------------------------------------------------------
JVB 2017-03-09 17:03:24.554 INFO: [24]
org.jitsi.videobridge.xmpp.ComponentImpl.log() SENT: <iq
id=“ARuO2-128689” to=“focus@auth.conf.opcion-libre.com.ar/focus186517940
618” from=“jitsi-videobridge.conf.opcion-libre.com.ar” type=“result”/>
JVB 2017-03-09 17:03:34.068 INFO: [141]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq
id=“fqD5i-25735” type=“result” to=“jitsi-videobridge.conf.opcion-libre.
com.ar” from=“conf.opcion-libre.com.ar”/>
JVB 2017-03-09 17:03:34.483 INFO: [232]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq type=“get”
to=“jitsi-videobridge.conf.opcion-libre.com.ar” from=“focus@
auth.conf.opcion-libre.com.ar/focus186517940618”
id=“ARuO2-128692”><healthcheck
xmlns=“http://jitsi.org/protocol/healthcheck”/></iq>
JVB 2017-03-09 17:03:34.484 INFO: [232]
org.jitsi.videobridge.Videobridge.log() CAT=stat
create_conf,conf_id=9fb5c7e070ec87d1
conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff540085517, pid=433, tid=140690701465344
#
# JRE version: OpenJDK Runtime Environment (7.0_121) (build 1.7.0_121-b00)
# Java VM: OpenJDK 64-Bit Server VM (24.121-b00 mixed mode linux-amd64
compressed oops)
# Derivative: IcedTea 2.6.8
# Distribution: Debian GNU/Linux 8.7 (jessie), package 7u121-2.6.8-2~deb8u1
# Problematic frame:
# C 0x00007ff540085517
#
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try “ulimit -c unlimited” before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid433.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
---------------------------------------------------------------------------

It seems that there was some problem with the JRE, although I'm not sure
what happened. If it helps, I can send you the file
/tmp/hs_err_pid433.log that was generated.

Thanks for your reply.

Kind regards,
Daniel


#12

Hi,

Hi,

Hi, Damian.

You can just health check jicofo curl
http://localhost:8888/about/health?list_jvb=true. It will report 200
if jicofo thinks it is healthy and has at least one healthy jvb
connected to it.

Great! Thank you!

I have noticed that in the morning of today, when running some
cron.daily standard tasks, it seems the check had a timeout and then the
bridge was removed. Maybe because the I/O wait on those tasks.

Here is what I found in the Jicofo log:

-----------------------------------------------------------------------
Jicofo 2017-03-21 06:25:46.495 WARNING: [16]
org.jitsi.jicofo.JvbDoctor.log()
jitsi-videobridge.conf.opcion-libre.com.ar health-check timed out, but
will give it anothe
r try after: 5000
Jicofo 2017-03-21 06:25:52.939 SEVERE: [35]
org.jitsi.xmpp.component.ComponentBase.run().629 Ping timeout for ID:
3li7c-76572
Jicofo 2017-03-21 06:26:07.903 WARNING: [16]
org.jitsi.jicofo.JvbDoctor.log() Health check failed on:
jitsi-videobridge.conf.opcion-libre.com.ar error: timeout
Jicofo 2017-03-21 06:26:07.908 INFO: [43]
org.jitsi.jicofo.BridgeSelector.removeJvbAddress().192 Removing JVB:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-21 06:26:07.908 INFO: [43]
org.jitsi.jicofo.JvbDoctor.log() Stopping health-check task for:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-21 06:26:07.911 INFO: [16]
org.jitsi.jicofo.JvbDoctor.log() Health check task cancelled for:
jitsi-videobridge.conf.opcion-libre.com.ar
-----------------------------------------------------------------------

Is it possible?

Yep, this is possible, did you check jvb, does it have any problems at
the same time?

On the other hand, do you know if these messages displayed in the Jicofo
log may be related to the Nagios checks?

-----------------------------------------------------------------------
Jicofo 2017-03-21 13:59:40.406 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:09:40.517 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:29:40.741 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:39:39.865 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:14:38.227 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:19:38.243 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:24:38.260 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:29:38.273 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:34:38.286 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
-----------------------------------------------------------------------

Not sure about these.

Regards
damencho

···

On Tue, Mar 21, 2017 at 1:38 PM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 20/03/17 11:40, Damian Minkov wrote:

Thanks for your time.

Kind regards,
Daniel

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


#13

Hi,

Hi, Damian.

I have noticed that in the morning of today, when running some
cron.daily standard tasks, it seems the check had a timeout and then the
bridge was removed. Maybe because the I/O wait on those tasks.

Here is what I found in the Jicofo log:

-----------------------------------------------------------------------
Jicofo 2017-03-21 06:25:46.495 WARNING: [16]
org.jitsi.jicofo.JvbDoctor.log()
jitsi-videobridge.conf.opcion-libre.com.ar health-check timed out, but
will give it anothe
r try after: 5000
Jicofo 2017-03-21 06:25:52.939 SEVERE: [35]
org.jitsi.xmpp.component.ComponentBase.run().629 Ping timeout for ID:
3li7c-76572
Jicofo 2017-03-21 06:26:07.903 WARNING: [16]
org.jitsi.jicofo.JvbDoctor.log() Health check failed on:
jitsi-videobridge.conf.opcion-libre.com.ar error: timeout
Jicofo 2017-03-21 06:26:07.908 INFO: [43]
org.jitsi.jicofo.BridgeSelector.removeJvbAddress().192 Removing JVB:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-21 06:26:07.908 INFO: [43]
org.jitsi.jicofo.JvbDoctor.log() Stopping health-check task for:
jitsi-videobridge.conf.opcion-libre.com.ar
Jicofo 2017-03-21 06:26:07.911 INFO: [16]
org.jitsi.jicofo.JvbDoctor.log() Health check task cancelled for:
jitsi-videobridge.conf.opcion-libre.com.ar
-----------------------------------------------------------------------

Is it possible?

Yep, this is possible, did you check jvb, does it have any problems at
the same time?

Today I didn't have this problem in the same time that the standard
operating system cron jobs were executed. I will continue to monitor it.

On the other hand, do you know if these messages displayed in the Jicofo
log may be related to the Nagios checks?

-----------------------------------------------------------------------
Jicofo 2017-03-21 13:59:40.406 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:09:40.517 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:29:40.741 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 14:39:39.865 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:14:38.227 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:19:38.243 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:24:38.260 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:29:38.273 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-21 15:34:38.286 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
-----------------------------------------------------------------------

Not sure about these.

I have the feeling that it has to do with Nagios checks pointing to the
URL that you mentioned to me because these log entries appears at five
minute intervals (or multiples of five minutes) and casually the Nagios
checks are every five minutes.

···

On 21/03/17 15:53, Damian Minkov wrote:

---------------------------------------------------------------------------
Jicofo 2017-03-22 00:09:38.465 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 00:34:38.427 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 00:39:38.408 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 00:44:38.399 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 00:59:38.419 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 01:04:38.469 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 01:24:38.675 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 01:34:38.777 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 02:19:38.251 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 02:29:38.231 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 02:44:38.208 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 02:49:38.206 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 02:59:38.257 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 03:04:38.309 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 03:14:38.410 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 03:24:38.521 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 03:39:38.681 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 03:44:38.751 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 04:04:36.985 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 04:19:37.152 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 04:24:37.206 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 04:39:37.358 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 04:44:37.407 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 04:49:37.459 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 04:59:37.565 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 05:14:37.720 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 05:24:38.134 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 05:34:38.144 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 05:44:38.169 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 05:59:38.177 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 06:04:38.202 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 06:14:38.195 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
tail: jicofo.log: file truncated
Jicofo 2017-03-22 06:25:44.974 WARNING: [47]
org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().538
PROCESSING TIME LIMIT EXCEEDED - it took 304ms to process: <iq
id="3li7c-119713" type="result" to="focus.conf.opcion-libre.com.ar"
from="conf.opcion-libre.com.ar"/>
Jicofo 2017-03-22 06:29:38.265 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 06:34:38.248 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 06:39:38.255 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 06:44:38.266 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 06:54:38.289 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:04:38.392 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:09:38.432 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:14:38.460 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:24:38.498 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:34:38.535 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:39:38.560 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:54:38.602 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 07:59:38.628 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 08:09:38.660 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 08:24:38.711 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 08:59:36.915 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 09:04:36.971 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 09:09:37.074 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 09:39:37.299 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 09:54:37.258 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 10:09:37.297 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 10:14:37.350 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 10:19:37.446 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 10:29:37.549 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 10:34:37.607 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 10:44:37.719 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
Jicofo 2017-03-22 10:49:37.780 WARNING: [40]
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Focus role unknown
(...)
---------------------------------------------------------------------------

Thanks for your reply.

Kind regards,
Daniel


#14

Hi,

Can you send it to me, thanks.

Regards
damencho

···

On Tue, Mar 14, 2017 at 10:23 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

Hi, Damian.

On 10/03/17 15:11, Damian Minkov wrote:

When you see that in jicofo, can you check the same timestamps in
jvb.log. It should complain about not able to create file or something
like that.

Yes, I found what I mentioned in an previous email of this thread:

---------------------------------------------------------------------------
JVB 2017-03-09 17:03:24.554 INFO: [24]
org.jitsi.videobridge.xmpp.ComponentImpl.log() SENT: <iq
id=“ARuO2-128689” to=“focus@auth.conf.opcion-libre.com.ar/focus186517940
618” from=“jitsi-videobridge.conf.opcion-libre.com.ar” type=“result”/>
JVB 2017-03-09 17:03:34.068 INFO: [141]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq
id=“fqD5i-25735” type=“result” to=“jitsi-videobridge.conf.opcion-libre.
com.ar” from=“conf.opcion-libre.com.ar”/>
JVB 2017-03-09 17:03:34.483 INFO: [232]
org.jitsi.videobridge.xmpp.ComponentImpl.log() RECV: <iq type=“get”
to=“jitsi-videobridge.conf.opcion-libre.com.ar” from=“focus@
auth.conf.opcion-libre.com.ar/focus186517940618”
id=“ARuO2-128692”><healthcheck
xmlns=“http://jitsi.org/protocol/healthcheck”/></iq>
JVB 2017-03-09 17:03:34.484 INFO: [232]
org.jitsi.videobridge.Videobridge.log() CAT=stat
create_conf,conf_id=9fb5c7e070ec87d1
conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff540085517, pid=433, tid=140690701465344
#
# JRE version: OpenJDK Runtime Environment (7.0_121) (build 1.7.0_121-b00)
# Java VM: OpenJDK 64-Bit Server VM (24.121-b00 mixed mode linux-amd64
compressed oops)
# Derivative: IcedTea 2.6.8
# Distribution: Debian GNU/Linux 8.7 (jessie), package 7u121-2.6.8-2~deb8u1
# Problematic frame:
# C 0x00007ff540085517
#
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try “ulimit -c unlimited” before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid433.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
---------------------------------------------------------------------------

It seems that there was some problem with the JRE, although I'm not sure
what happened. If it helps, I can send you the file
/tmp/hs_err_pid433.log that was generated.

Thanks for your reply.

Kind regards,
Daniel

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


#15

Hi,

Hi, Damian.

Can you send it to me, thanks.

I attach the file.

Thanks for your time.

Kind regards,
Daniel

hs_err_pid433.log (88.3 KB)

···

On 14/03/17 12:47, Damian Minkov wrote:


#16

Hi again,

Thanks for the report. Do you observe this frequently, the same crash?
We haven't seen this, it basically crashes in the native part of the
java sockets:
....
j java.net.PlainDatagramSocketImpl.receive0(Ljava/net/DatagramPacket;)V+0

As you are using java7 and if you see it regularly I would suggest
updating to java8 and monitor how it behaves.

Regards
damencho

···

On Tue, Mar 14, 2017 at 11:14 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 14/03/17 12:47, Damian Minkov wrote:

Hi,

Hi, Damian.

Can you send it to me, thanks.

I attach the file.

Thanks for your time.

Kind regards,
Daniel

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


#17

Hi again,

Hi, Damian.

Thanks for the report. Do you observe this frequently, the same crash?
We haven't seen this, it basically crashes in the native part of the
java sockets:
....
j java.net.PlainDatagramSocketImpl.receive0(Ljava/net/DatagramPacket;)V+0

As you are using java7 and if you see it regularly I would suggest
updating to java8 and monitor how it behaves.

Thank you for your time reviewing this.

I'm now using openjdk-7-jre which is the version that is available in
Debian Jessie standard repositories. It seems that openjdk-8-jre is
available in Backports but I have not tried it.

From the moment I had this crash I did not restart Jitsi VideoBridge
because before doing so I wanted to know what opinion you had about this
crash. I will restart JVB and I will be monitoring if it happens again
in which case I will mention it in this thread.

Thanks again.

Kind regards,
Daniel

···

On 14/03/17 14:07, Damian Minkov wrote: