Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #232453 > unrolled thread

Jitsi keeps failing when I want to use it

Back to article view | Back to linux.debian.user

Contents

  Jitsi keeps failing when I want to use it Gary Dale <gary@extremeground.com> - 2021-03-06 19:40 +0100
    Re: Jitsi keeps failing when I want to use it Dan Ritter <dsr@randomstring.org> - 2021-03-06 21:20 +0100
      Re: Jitsi keeps failing when I want to use it Gary Dale <gary@extremeground.com> - 2021-03-06 21:50 +0100
        Re: Jitsi keeps failing when I want to use it Gary Dale <gary@extremeground.com> - 2021-03-06 22:00 +0100
          Re: Jitsi keeps failing when I want to use it [RESOLVED} Gary Dale <gary@extremeground.com> - 2021-03-06 23:00 +0100
    Re: Jitsi keeps failing when I want to use it Henning Follmann <hfollmann@itcfollmann.com> - 2021-03-06 21:40 +0100
      Re: Jitsi keeps failing when I want to use it Gary Dale <gary@extremeground.com> - 2021-03-06 21:50 +0100
      Re: Jitsi keeps failing when I want to use it Gary Dale <gary@extremeground.com> - 2021-03-06 21:50 +0100

#232453 — Jitsi keeps failing when I want to use it

I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It 
usually works fine. However every time I want to actually host a 
meeting, it decides to act up.

Yesterday evening I tested Jitsi with a meeting between my desktop 
system and my Android phone. Everything worked properly. I could see the 
video feed from both devices on both devices. Since it was working, I 
notified people of the meeting address.

Today, I tried it again pre-meeting only to find the usual issue cropped 
up. While both devices can connect to the meeting, I can only see the 
video feed from the local device (I can see my desktop feed on the 
desktop browser and the Android feed on the phone).

I tried creating a new meeting but I get the same problem. I've tried 
reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), which 
worked in the past, but still no luck. Nor does rebooting the server help.

Any ideas anyone?

[toc] | [next] | [standalone]

#232457

Gary Dale wrote: 
> I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It usually
> works fine. However every time I want to actually host a meeting, it decides
> to act up.
> 
> Yesterday evening I tested Jitsi with a meeting between my desktop system
> and my Android phone. Everything worked properly. I could see the video feed
> from both devices on both devices. Since it was working, I notified people
> of the meeting address.
> 
> Today, I tried it again pre-meeting only to find the usual issue cropped up.
> While both devices can connect to the meeting, I can only see the video feed
> from the local device (I can see my desktop feed on the desktop browser and
> the Android feed on the phone).
> 
> I tried creating a new meeting but I get the same problem. I've tried
> reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), which
> worked in the past, but still no luck. Nor does rebooting the server help.

Is your phone connected via wifi to your LAN or to a mobile data
service? Try it both ways.

I suspect a STUN/TURN NAT issue.

-dsr-

[toc] | [prev] | [next] | [standalone]

#232460

My phone lost its wifi so it only connects via the mobile data. In any 
event, the connection is through a public IP address.

I've noticed one thing that puzzles me a little (after I tried removing 
and reinstalling Jitsi) and that is that the Debian/Buster package 
installs jitsi-videobridge while the jitsi install guide for 
Debian/Ubuntu talks about jitsi-videobridge2.


On 2021-03-06 15:16, Dan Ritter wrote:
> Gary Dale wrote:
>> I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It 
>> usually
>> works fine. However every time I want to actually host a meeting, it 
>> decides
>> to act up.
>>
>> Yesterday evening I tested Jitsi with a meeting between my desktop system
>> and my Android phone. Everything worked properly. I could see the 
>> video feed
>> from both devices on both devices. Since it was working, I notified 
>> people
>> of the meeting address.
>>
>> Today, I tried it again pre-meeting only to find the usual issue 
>> cropped up.
>> While both devices can connect to the meeting, I can only see the 
>> video feed
>> from the local device (I can see my desktop feed on the desktop 
>> browser and
>> the Android feed on the phone).
>>
>> I tried creating a new meeting but I get the same problem. I've tried
>> reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), which
>> worked in the past, but still no luck. Nor does rebooting the server 
>> help.
> Is your phone connected via wifi to your LAN or to a mobile data
> service? Try it both ways.
>
> I suspect a STUN/TURN NAT issue.
>
> -dsr-

[toc] | [prev] | [next] | [standalone]

#232462

On 2021-03-06 15:44, Gary Dale wrote:
> My phone lost its wifi so it only connects via the mobile data. In any 
> event, the connection is through a public IP address.
>
> I've noticed one thing that puzzles me a little (after I tried 
> removing and reinstalling Jitsi) and that is that the Debian/Buster 
> package installs jitsi-videobridge while the jitsi install guide for 
> Debian/Ubuntu talks about jitsi-videobridge2.
>
>
> On 2021-03-06 15:16, Dan Ritter wrote:
>> Gary Dale wrote:
>>> I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It 
>>> usually
>>> works fine. However every time I want to actually host a meeting, it 
>>> decides
>>> to act up.
>>>
>>> Yesterday evening I tested Jitsi with a meeting between my desktop 
>>> system
>>> and my Android phone. Everything worked properly. I could see the 
>>> video feed
>>> from both devices on both devices. Since it was working, I notified 
>>> people
>>> of the meeting address.
>>>
>>> Today, I tried it again pre-meeting only to find the usual issue 
>>> cropped up.
>>> While both devices can connect to the meeting, I can only see the 
>>> video feed
>>> from the local device (I can see my desktop feed on the desktop 
>>> browser and
>>> the Android feed on the phone).
>>>
>>> I tried creating a new meeting but I get the same problem. I've tried
>>> reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), which
>>> worked in the past, but still no luck. Nor does rebooting the server 
>>> help.
>> Is your phone connected via wifi to your LAN or to a mobile data
>> service? Try it both ways.
>>
>> I suspect a STUN/TURN NAT issue.
>>
>> -dsr-
>
BTW: I didn't change anything on the jitsi server between it working and 
it not working. I did ssh to it in the morning to check for apt updates 
but there weren't any.

[toc] | [prev] | [next] | [standalone]

#232463 — Re: Jitsi keeps failing when I want to use it [RESOLVED}

On 2021-03-06 15:54, Gary Dale wrote:
> On 2021-03-06 15:44, Gary Dale wrote:
>> My phone lost its wifi so it only connects via the mobile data. In 
>> any event, the connection is through a public IP address.
>>
>> I've noticed one thing that puzzles me a little (after I tried 
>> removing and reinstalling Jitsi) and that is that the Debian/Buster 
>> package installs jitsi-videobridge while the jitsi install guide for 
>> Debian/Ubuntu talks about jitsi-videobridge2.
>>
>>
>> On 2021-03-06 15:16, Dan Ritter wrote:
>>> Gary Dale wrote:
>>>> I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It 
>>>> usually
>>>> works fine. However every time I want to actually host a meeting, 
>>>> it decides
>>>> to act up.
>>>>
>>>> Yesterday evening I tested Jitsi with a meeting between my desktop 
>>>> system
>>>> and my Android phone. Everything worked properly. I could see the 
>>>> video feed
>>>> from both devices on both devices. Since it was working, I notified 
>>>> people
>>>> of the meeting address.
>>>>
>>>> Today, I tried it again pre-meeting only to find the usual issue 
>>>> cropped up.
>>>> While both devices can connect to the meeting, I can only see the 
>>>> video feed
>>>> from the local device (I can see my desktop feed on the desktop 
>>>> browser and
>>>> the Android feed on the phone).
>>>>
>>>> I tried creating a new meeting but I get the same problem. I've tried
>>>> reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), 
>>>> which
>>>> worked in the past, but still no luck. Nor does rebooting the 
>>>> server help.
>>> Is your phone connected via wifi to your LAN or to a mobile data
>>> service? Try it both ways.
>>>
>>> I suspect a STUN/TURN NAT issue.
>>>
>>> -dsr-
>>
> BTW: I didn't change anything on the jitsi server between it working 
> and it not working. I did ssh to it in the morning to check for apt 
> updates but there weren't any.
>
OK, it turns out the problem was with my phone. I have no idea why it 
worked yesterday but not today but when I tried it with another device, 
things worked.

[toc] | [prev] | [next] | [standalone]

#232458

On Sat, Mar 06, 2021 at 01:38:07PM -0500, Gary Dale wrote:
> I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It usually
> works fine. However every time I want to actually host a meeting, it decides
> to act up.
> 
> Yesterday evening I tested Jitsi with a meeting between my desktop system
> and my Android phone. Everything worked properly. I could see the video feed
> from both devices on both devices. Since it was working, I notified people
> of the meeting address.
> 
> Today, I tried it again pre-meeting only to find the usual issue cropped up.
> While both devices can connect to the meeting, I can only see the video feed
> from the local device (I can see my desktop feed on the desktop browser and
> the Android feed on the phone).
> 
> I tried creating a new meeting but I get the same problem. I've tried
> reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), which
> worked in the past, but still no luck. Nor does rebooting the server help.
> 
> Any ideas anyone?
>


As usual, no logs => it didn't happen!

Without any information one could only guess.

-H

-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [prev] | [next] | [standalone]

#232459

On 2021-03-06 15:36, Henning Follmann wrote:
> On Sat, Mar 06, 2021 at 01:38:07PM -0500, Gary Dale wrote:
>> I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It usually
>> works fine. However every time I want to actually host a meeting, it decides
>> to act up.
>>
>> Yesterday evening I tested Jitsi with a meeting between my desktop system
>> and my Android phone. Everything worked properly. I could see the video feed
>> from both devices on both devices. Since it was working, I notified people
>> of the meeting address.
>>
>> Today, I tried it again pre-meeting only to find the usual issue cropped up.
>> While both devices can connect to the meeting, I can only see the video feed
>> from the local device (I can see my desktop feed on the desktop browser and
>> the Android feed on the phone).
>>
>> I tried creating a new meeting but I get the same problem. I've tried
>> reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), which
>> worked in the past, but still no luck. Nor does rebooting the server help.
>>
>> Any ideas anyone?
>>
>
> As usual, no logs => it didn't happen!
>
> Without any information one could only guess.
>
> -H
# tail -n 32 jicofo.log
Jicofo 2021-03-06 15:38:06.901 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Added participant jid= 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521, 
bridge=jvbbrewery@internal.auth.meet.rahim-dale.org/3b2b133c-6e81-4d54-9563-48bc57c16876
Jicofo 2021-03-06 15:38:06.902 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Region info, 
conference=22383: [[null, null]]
Jicofo 2021-03-06 15:38:06.906 INFO: [136] 
org.jitsi.jicofo.discovery.DiscoveryUtil.log() Doing feature discovery 
for shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521
Jicofo 2021-03-06 15:38:06.906 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Added participant jid= 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557, 
bridge=jvbbrewery@internal.auth.meet.rahim-dale.org/3b2b133c-6e81-4d54-9563-48bc57c16876
Jicofo 2021-03-06 15:38:06.907 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Region info, 
conference=22383: [[null, null, null]]
Jicofo 2021-03-06 15:38:06.908 INFO: [137] 
org.jitsi.jicofo.discovery.DiscoveryUtil.log() Doing feature discovery 
for shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557
Jicofo 2021-03-06 15:38:07.192 INFO: [136] 
org.jitsi.jicofo.discovery.DiscoveryUtil.log() Successfully discovered 
features for 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521 in 285
Jicofo 2021-03-06 15:38:07.215 INFO: [136] 
org.jitsi.jicofo.AbstractChannelAllocator.log() Using 
jvbbrewery@internal.auth.meet.rahim-dale.org/3b2b133c-6e81-4d54-9563-48bc57c16876 
to allocate channels for: 
Participant[shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521]@423117319
Jicofo 2021-03-06 15:38:08.151 INFO: [137] 
org.jitsi.jicofo.discovery.DiscoveryUtil.log() Successfully discovered 
features for 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557 in 1243
Jicofo 2021-03-06 15:38:08.155 INFO: [137] 
org.jitsi.jicofo.AbstractChannelAllocator.log() Using 
jvbbrewery@internal.auth.meet.rahim-dale.org/3b2b133c-6e81-4d54-9563-48bc57c16876 
to allocate channels for: 
Participant[shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557]@2134948675
Jicofo 2021-03-06 15:38:08.344 INFO: [136] 
org.jitsi.jicofo.ParticipantChannelAllocator.log() Sending 
session-initiate to: 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521
Jicofo 2021-03-06 15:38:08.366 INFO: [137] 
org.jitsi.jicofo.ParticipantChannelAllocator.log() Sending 
session-initiate to: 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557
Jicofo 2021-03-06 15:38:08.600 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Got session-accept from: 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521
Jicofo 2021-03-06 15:38:08.614 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Received session-accept 
from shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521 with 
accepted sources:Sources{ video: [ssrc=2796851205 ssrc=3366031894 
ssrc=2837324841 ] audio: [ssrc=682686965 ] }@887521678
Jicofo 2021-03-06 15:38:08.619 WARNING: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() No jingle session yet for 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557
Jicofo 2021-03-06 15:38:09.449 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Got session-accept from: 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557
Jicofo 2021-03-06 15:38:09.458 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Received session-accept 
from shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557 with 
accepted sources:Sources{ video: [ssrc=682624931 ssrc=616139617 
ssrc=4223476417 ssrc=2608752843 ssrc=22331310 ssrc=4245847487 ] audio: 
[ssrc=4124579793 ] }@703862439
Jicofo 2021-03-06 15:38:41.565 INFO: [32] 
org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event 
ChatRoomMemberPresenceChangeEvent[type=MemberLeft 
sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@68733ba7 
member=ChatMember[shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557, 
jid: lbgaft_f60qtjhxs@guest.meet.rahim-dale.org/xrhm6YjQ]@1646921893]
Jicofo 2021-03-06 15:38:41.565 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557 is leaving
Jicofo 2021-03-06 15:38:41.567 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Terminating 
Participant[shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557]@2134948675, 
reason: gone, send st: false
Jicofo 2021-03-06 15:38:41.568 INFO: [32] 
org.jitsi.protocol.xmpp.AbstractOperationSetJingle.log() Terminate 
session: shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557, 
reason: gone, send terminate: false
Jicofo 2021-03-06 15:38:41.574 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Removing 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557 sources 
Sources{ video: [ssrc=682624931 ssrc=616139617 ssrc=4223476417 
ssrc=2608752843 ssrc=22331310 ssrc=4245847487 ] audio: [ssrc=4124579793 
] }@1962660370
Jicofo 2021-03-06 15:38:41.576 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Removed participant: 
true, shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557
Jicofo 2021-03-06 15:38:41.576 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Region info, 
conference=22383: [[null, null]]
Jicofo 2021-03-06 15:38:41.579 INFO: [32] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Expiring channels for: 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/911a4557 on: 
Bridge[jid=jvbbrewery@internal.auth.meet.rahim-dale.org/3b2b133c-6e81-4d54-9563-48bc57c16876, 
relayId=null, region=null, stress=0.01]
Jicofo 2021-03-06 15:39:01.583 INFO: [112] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Timing out single 
participant: shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521
Jicofo 2021-03-06 15:39:01.584 INFO: [112] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Terminating 
Participant[shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521]@423117319, 
reason: expired, send st: true
Jicofo 2021-03-06 15:39:01.584 INFO: [112] 
org.jitsi.protocol.xmpp.AbstractOperationSetJingle.log() Terminate 
session: shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521, 
reason: expired, send terminate: true
Jicofo 2021-03-06 15:39:01.590 INFO: [112] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Removing 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521 sources 
Sources{ video: [ssrc=2796851205 ssrc=3366031894 ssrc=2837324841 ] 
audio: [ssrc=682686965 ] }@1758236393
Jicofo 2021-03-06 15:39:01.590 INFO: [112] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Removed participant: 
true, shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521
Jicofo 2021-03-06 15:39:01.591 INFO: [112] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Region info, 
conference=22383: [[null]]
Jicofo 2021-03-06 15:39:01.592 INFO: [112] 
org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Expiring channels for: 
shafeenasbirthdayparty@conference.meet.rahim-dale.org/c397d521 on: 
Bridge[jid=jvbbrewery@internal.auth.meet.rahim-dale.org/3b2b133c-6e81-4d54-9563-48bc57c16876, 
relayId=null, region=null, stress=0.01]

[toc] | [prev] | [next] | [standalone]

#232461

On 2021-03-06 15:36, Henning Follmann wrote:
> On Sat, Mar 06, 2021 at 01:38:07PM -0500, Gary Dale wrote:
>> I'm running a Jitis-meet server on a Debian/Buster AMD64 system. It usually
>> works fine. However every time I want to actually host a meeting, it decides
>> to act up.
>>
>> Yesterday evening I tested Jitsi with a meeting between my desktop system
>> and my Android phone. Everything worked properly. I could see the video feed
>> from both devices on both devices. Since it was working, I notified people
>> of the meeting address.
>>
>> Today, I tried it again pre-meeting only to find the usual issue cropped up.
>> While both devices can connect to the meeting, I can only see the video feed
>> from the local device (I can see my desktop feed on the desktop browser and
>> the Android feed on the phone).
>>
>> I tried creating a new meeting but I get the same problem. I've tried
>> reinstalling Jitsi-meet (and also Jicofo and Jitsi-videobridge2), which
>> worked in the past, but still no luck. Nor does rebooting the server help.
>>
>> Any ideas anyone?
>>
>
> As usual, no logs => it didn't happen!
>
> Without any information one could only guess.
>
> -H
>
# tail -n 32 jvb.log
2021-03-06 15:40:29.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:40:39.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:40:49.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:40:59.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:41:09.285 INFO: [23] VideobridgeExpireThread.expire#140: 
Running expire()
2021-03-06 15:41:09.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:41:19.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:41:29.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:41:39.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:41:49.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:41:59.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:42:09.285 INFO: [23] VideobridgeExpireThread.expire#140: 
Running expire()
2021-03-06 15:42:09.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:42:19.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:42:29.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:42:39.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:42:49.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:42:59.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:43:09.285 INFO: [23] VideobridgeExpireThread.expire#140: 
Running expire()
2021-03-06 15:43:09.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:43:19.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:43:29.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:43:39.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:43:49.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:43:59.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:44:09.285 INFO: [23] VideobridgeExpireThread.expire#140: 
Running expire()
2021-03-06 15:44:09.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:44:19.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.00001S. Sticky failure: false
2021-03-06 15:44:29.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:44:39.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:44:49.306 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
2021-03-06 15:44:59.305 INFO: [24] HealthChecker.run#170: Performed a 
successful health check in PT0.000011S. Sticky failure: false
root@TheLibrarian:/var/log/jitsi#

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web