[jitsi-users] New Debian install - only local audio/video


#1

Hi.

I've just set up Jitsi Meet on a Debian 7 (wheezy) Virtual Machine running
under KVM. I've followed the first part of the instructions at
https://jitsi.org/qi (ie: down as far as, and including "Open a conference").

From a (real hardware) client, I use Chrome to connect to the Jitsi server IP
address, and I get offered a conference URL. I accept this, and I then get
joined to a new conference and I can see my own video stream.

So far, so good - that was nice and easy to get going :slight_smile:

If I then connect to the same URL from another machine (also real hardware,
and just to be clear, all three machines are on the same 192.168.36.0/24
network with no NAT involved), I also see my local video stream on that
machine, and I can see on both machines that there's a second person now in
the conference.

The problem is that I get no audio or video between the two clients - the
"other participant" window on one machine is blank, and on the other it just
has one of those default Jitsi avatars in it, but there's no display of the
other machine's video stream on either. I also get no audio on machine A from
machine B or vice versa.

I do know that there's no problem with the clients themselves, because if I
point them at https://meet.jit.si/Something they can conference completely as
expected (and that is also going through NAT, of course).

1. Is this a known problem; should I have done something different from the
(surprisingly easy) instructions at https://jitsi.org/qi ?

2. Where should I look for log messages indicating what might be wrong? I've
found /var/log/jitsi with jvb.log and jicofo.log in it, but I'm not sure how
to make sense of what I find in those files.

I there's any other info I can provide to help work out what's wrong, please
tell me what to post.

Thanks,

Antony.

···

--
"The future is already here. It's just not evenly distributed yet."

- William Gibson

                                                   Please reply to the list;
                                                         please *don't* CC me.


#2

The reason is that there are some issues with the conference
creation and/or the access of the clients to it.

You can look at /var/log/jitsi/jvb.log and search at the end of it, to
see what happens when you try to create/access a conference. Pay
attention to the messages with errors.

Also look at the /var/log/prosody/prosody.{log|err} to see whether the
jitsi-videobrdge and focus get registered as xmpp components.

It could also be a network/firewall issue, but the first thing to
check are the logs, as very often the problem is in xmpp components
unavailability.

···

On Thu, 17 Sep 2015 12:34:52 +0200 Antony Stone wrote:

1. Is this a known problem; should I have done something different
from the (surprisingly easy) instructions at https://jitsi.org/qi ?

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#3

>1. Is this a known problem; should I have done something different
>from the (surprisingly easy) instructions at https://jitsi.org/qi ?

The reason is that there are some issues with the conference
creation and/or the access of the clients to it.

You can look at /var/log/jitsi/jvb.log and search at the end of it, to
see what happens when you try to create/access a conference. Pay
attention to the messages with errors.

With no clients connected, I see only messages such as the following, every
ten seconds:

2015-08-17 13:42:40.649 INFO: [17]
org.jitsi.videobridge.xmpp.ComponentImpl.info() RECV: <iq id="TsbLD-796"
type="result" to="jitsi-videobridge.192.168.36.80" from="192.168.36.80"/>

When the first client connects, nothing new appears (and the above messages
continue occurring).

When the second client connects, around 100 lines appear in that log file,
including the following:

2015-08-17 13:42:41.943 SEVERE: [79]
util.UtilActivator.uncaughtException().108 An uncaught exception occurred in
thread=Thread[org.jitsi.videobridge.SctpConnection-pool-5-thread-9,5,main] and
message was: Could not initialize class org.jitsi.sctp4j.Sctp
        at org.jitsi.videobridge.SctpConnection$1.run(SctpConnection.java:454)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:701)

2015-08-17 13:42:43.016 SEVERE: [84]
util.UtilActivator.uncaughtException().108 An uncaught exception occurred in
thread=Thread[org.jitsi.videobridge.SctpConnection-pool-5-thread-10,5,main]
and message was: Could not initialize class org.jitsi.sctp4j.Sctp
        at org.jitsi.videobridge.SctpConnection$1.run(SctpConnection.java:454)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:701)

Does this give a clue as to what's wrong?

Also look at the /var/log/prosody/prosody.{log|err} to see whether the
jitsi-videobrdge and focus get registered as xmpp components.

The first looks okay:

Sep 17 11:29:50 jitsi-videobridge.192.168.36.80:component info
Component successfully authenticated: jitsi-videobridge.192.168.36.80

However I'm not so sure about the second one - I'm getting the following every
30 seconds, whether there's a conference in progress or not:

Sep 17 13:52:50 callcontrol.192.168.36.80:component warn Stanza being
handled by default component; bouncing error for: <iq id='Ipm4a-3847'
type='get' to='callcontrol.192.168.36.80'
from='focus@auth.192.168.36.80/focus11168755666'>

It could also be a network/firewall issue, but the first thing to
check are the logs, as very often the problem is in xmpp components
unavailability.

I think I can rule that out because the server, and both clients, are on a flat
192.168.36.0/24 network with no router, firewall or NAT in between them.

Thanks,

Antony.

···

On Thursday 17 September 2015 at 13:14:48, Yasen Pramatarov wrote:

On Thu, 17 Sep 2015 12:34:52 +0200 Antony Stone wrote:

--
I want to build a machine that will be proud of me.

- Danny Hillis, creator of The Connection Machine

                                                   Please reply to the list;
                                                         please *don't* CC me.


#4

1. Is this a known problem; should I have done something different

>from the (surprisingly easy) instructions at https://jitsi.org/qi ?

  The reason is that there are some issues with the conference
  creation and/or the access of the clients to it.

  You can look at /var/log/jitsi/jvb.log and search at the end of it, to
  see what happens when you try to create/access a conference. Pay
  attention to the messages with errors.

With no clients connected, I see only messages such as the following, every
ten seconds:

2015-08-17 13:42:40.649 INFO: [17]
org.jitsi.videobridge.xmpp.ComponentImpl.info() RECV: <iq id="TsbLD-796"
type="result" to="jitsi-videobridge.192.168.36.80" from="192.168.36.80"/>

When the first client connects, nothing new appears (and the above messages
continue occurring).

When the second client connects, around 100 lines appear in that log file,
including the following:

2015-08-17 13:42:41.943 SEVERE: [79]
util.UtilActivator.uncaughtException().108 An uncaught exception occurred in
thread=Thread[org.jitsi.videobridge.SctpConnection-pool-5-thread-9,5,main] and
message was: Could not initialize class org.jitsi.sctp4j.Sctp
         at org.jitsi.videobridge.SctpConnection$1.run(SctpConnection.java:454)
         at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
         at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
         at java.lang.Thread.run(Thread.java:701)

2015-08-17 13:42:43.016 SEVERE: [84]
util.UtilActivator.uncaughtException().108 An uncaught exception occurred in
thread=Thread[org.jitsi.videobridge.SctpConnection-pool-5-thread-10,5,main]
and message was: Could not initialize class org.jitsi.sctp4j.Sctp
         at org.jitsi.videobridge.SctpConnection$1.run(SctpConnection.java:454)
         at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
         at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
         at java.lang.Thread.run(Thread.java:701)

Does this give a clue as to what's wrong?

Are you running jitsi-videobridge version 517 (you can check with `apt-cache policy jitsi-videobridge`)? If so, update to 518 or the latest (`sudo apt-get update && sudo apt-get install --only-upgrade jitsi-videobridge`) and try again.

Regards,
Boris

···

On 17/09/15 08:04, Antony Stone wrote:

On Thursday 17 September 2015 at 13:14:48, Yasen Pramatarov wrote:

On Thu, 17 Sep 2015 12:34:52 +0200 Antony Stone wrote:

  Also look at the /var/log/prosody/prosody.{log|err} to see whether the
  jitsi-videobrdge and focus get registered as xmpp components.

The first looks okay:

Sep 17 11:29:50 jitsi-videobridge.192.168.36.80:component info
Component successfully authenticated: jitsi-videobridge.192.168.36.80

However I'm not so sure about the second one - I'm getting the following every
30 seconds, whether there's a conference in progress or not:

Sep 17 13:52:50 callcontrol.192.168.36.80:component warn Stanza being
handled by default component; bouncing error for: <iq id='Ipm4a-3847'
type='get' to='callcontrol.192.168.36.80'
from='focus@auth.192.168.36.80/focus11168755666'>

  It could also be a network/firewall issue, but the first thing to
  check are the logs, as very often the problem is in xmpp components
  unavailability.

I think I can rule that out because the server, and both clients, are on a flat
192.168.36.0/24 network with no router, firewall or NAT in between them.

Thanks,

Antony.


#5

>
> 2015-08-17 13:42:41.943 SEVERE: [79]
> util.UtilActivator.uncaughtException().108 An uncaught exception occurred
> in
> thread=Thread[org.jitsi.videobridge.SctpConnection-pool-5-thread-9,5,mai
> n] and message was: Could not initialize class org.jitsi.sctp4j.Sctp at
> org.jitsi.videobridge.SctpConnection$1.run(SctpConnection.java:
> 454) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java
> :1146) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav
> a:615) at java.lang.Thread.run(Thread.java:701)
>
> 2015-08-17 13:42:43.016 SEVERE: [84]
> util.UtilActivator.uncaughtException().108 An uncaught exception occurred
> in
> thread=Thread[org.jitsi.videobridge.SctpConnection-pool-5-thread-10,5,ma
> in] and message was: Could not initialize class org.jitsi.sctp4j.Sctp at
> org.jitsi.videobridge.SctpConnection$1.run(SctpConnection.java:
> 454) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java
> :1146) at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav
> a:615) at java.lang.Thread.run(Thread.java:701)
>
> Does this give a clue as to what's wrong?

Are you running jitsi-videobridge version 517 (you can check with
`apt-cache policy jitsi-videobridge`)?

Unfortunately that's not the problem:

root@Jitsi:~# apt-cache policy jitsi-videobridge
jitsi-videobridge:
  Installed: 518-1
  Candidate: 518-1
  Version table:
*** 518-1 0
        500 http://download.jitsi.org/nightly/deb/ unstable/ Packages

[...plus further details of older packages, back to 509...]

It was only installed this morning, from the repo
http://download.jitsi.org/nightly/deb unstable/ as listed at
https://jitsi.org/qi

If so, update to 518 or the latest (`sudo apt-get update && sudo apt-get
install --only-upgrade jitsi-videobridge`) and try again.

Well, just in case:

root@Jitsi:~# apt-get update
...standard repo output skipped...
Hit http://download.jitsi.org unstable/ Packages
Ign http://download.jitsi.org unstable/ Translation-en_GB
Ign http://download.jitsi.org unstable/ Translation-en
Reading package lists... Done
root@Jitsi:~# apt-get install --only-upgrade jitsi-videobridge
Reading package lists... Done
Building dependency tree
Reading state information... Done
jitsi-videobridge is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

It was a new install of Debian, immediately followed by a new install of
Jitsi. I did exactly what was described at https://jitsi.org/qi and used the
machine's IP address throughout the configuration (because I haven't put it
into local DNS with a hostname).

Any further ideas, please?

Antony.

···

On Thursday 17 September 2015 at 16:28:27, Boris Grozev wrote:

On 17/09/15 08:04, Antony Stone wrote:

--
The words "e pluribus unum" on the Great Seal of the United States are from a
poem by Virgil entitled "Moretum", which is about cheese and garlic salad
dressing.

                                                   Please reply to the list;
                                                         please *don't* CC me.