[jitsi-dev] problems with Jigasi and Jitsi-Meet


#1

Hi all,

I updated to latest unstable Debian packages and I'm getting the following
error when trying to dial out via Jigasi

2017-04-03 16:32:51.757 INFO: [65]
impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.registrationStateChanged().118
Jingle : ON
2017-04-03 16:32:51.758 INFO: [65]
org.jitsi.jigasi.JvbConference.registrationStateChanged().546 XMPP
(15b34a97146@callcontrol.meet.my.domain): RegistrationStateChangeEvent[
oldState=Unregistered; ne$
2017-04-03 16:32:51.769 SEVERE: [70]
org.jivesoftware.smack.Connection.notifyListener() null
java.lang.NullPointerException
        at
java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
        at
java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
        at
net.java.sip.communicator.impl.protocol.jabber.extensions.caps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
        at
net.java.sip.communicator.impl.protocol.jabber.extensions.caps.EntityCapsManager$CapsPacketListener.processPacket(EntityCapsManager.java:980)
        at
org.jivesoftware.smack.Connection$ListenerWrapper.notifyListener(Connection.java:877)
        at
org.jivesoftware.smack.PacketReader$ListenerNotification.run(PacketReader.java:403)
        at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Anyone else experiencing this? Where should I start to look to debug this?

Cheers,
Peter


#2

Anyone else seeing this NPE in smack or is it just me?
Any hint where I should start looking?

Cheers,
Peter

···

On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Hi all,

I updated to latest unstable Debian packages and I'm getting the following
error when trying to dial out via Jigasi

2017-04-03 16:32:51.757 INFO: [65] impl.protocol.jabber.
OperationSetBasicTelephonyJabberImpl.registrationStateChanged().118
Jingle : ON
2017-04-03 16:32:51.758 INFO: [65] org.jitsi.jigasi.JvbConference.registrationStateChanged().546
XMPP (15b34a97146@callcontrol.meet.my.domain):
RegistrationStateChangeEvent[ oldState=Unregistered; ne$
2017-04-03 16:32:51.769 SEVERE: [70] org.jivesoftware.smack.Connection.notifyListener()
null
java.lang.NullPointerException
        at java.util.concurrent.ConcurrentHashMap.replaceNode(
ConcurrentHashMap.java:1106)
        at java.util.concurrent.ConcurrentHashMap.remove(
ConcurrentHashMap.java:1097)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.caps.
EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.caps.
EntityCapsManager$CapsPacketListener.processPacket(
EntityCapsManager.java:980)
        at org.jivesoftware.smack.Connection$ListenerWrapper.
notifyListener(Connection.java:877)
        at org.jivesoftware.smack.PacketReader$ListenerNotification.run(
PacketReader.java:403)
        at java.util.concurrent.Executors$RunnableAdapter.
call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Anyone else experiencing this? Where should I start to look to debug this?

Cheers,
Peter


#3

I haven't seen this, its some problem with capabilities, not sure what can
be the cause of this.

···

On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> wrote:

Anyone else seeing this NPE in smack or is it just me?
Any hint where I should start looking?

Cheers,
Peter

On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Hi all,

I updated to latest unstable Debian packages and I'm getting the
following error when trying to dial out via Jigasi

2017-04-03 16:32:51.757 INFO: [65] impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118 Jingle : ON
2017-04-03 16:32:51.758 INFO: [65] org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP (15b34a97146@callcontrol.meet.my.domain):
RegistrationStateChangeEvent[ oldState=Unregistered; ne$
2017-04-03 16:32:51.769 SEVERE: [70] org.jivesoftware.smack.Connection.notifyListener()
null
java.lang.NullPointerException
        at java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
        at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager$CapsPacketListener.processPacket(Entity
CapsManager.java:980)
        at org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
        at org.jivesoftware.smack.PacketReader$ListenerNotification.run
(PacketReader.java:403)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Anyone else experiencing this? Where should I start to look to debug this?

Cheers,
Peter

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


#4

Thanks Damian,

I think I'm going to purge the ubuntu server and install everything again
from scratch.
What is the current recommended packages that are known to work well with
latest Chrome and ffox (and jigasi)?

Should I use stable or unstable packages?

Cheers,
Peter

···

On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov <damencho@damencho.com> wrote:

I haven't seen this, its some problem with capabilities, not sure what can
be the cause of this.

On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> wrote:

Anyone else seeing this NPE in smack or is it just me?
Any hint where I should start looking?

Cheers,
Peter

On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

Hi all,

I updated to latest unstable Debian packages and I'm getting the
following error when trying to dial out via Jigasi

2017-04-03 16:32:51.757 INFO: [65] impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118 Jingle : ON
2017-04-03 16:32:51.758 INFO: [65] org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP (15b34a97146@callcontrol.meet.my.domain):
RegistrationStateChangeEvent[ oldState=Unregistered; ne$
2017-04-03 16:32:51.769 SEVERE: [70] org.jivesoftware.smack.Connection.notifyListener()
null
java.lang.NullPointerException
        at java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
        at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager$CapsPacketListener.processPacket(Entity
CapsManager.java:980)
        at org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
        at org.jivesoftware.smack.PacketReader$ListenerNotification.run
(PacketReader.java:403)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Anyone else experiencing this? Where should I start to look to debug
this?

Cheers,
Peter

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

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


#5

I also noticed that the current install (unstable packages from 2 days ago)
is giving me some problems, specially when clients are behind restrictive
firewalls (and yes I have jetty listening on 443 on AWS and advertising
that ICE candidate).

I see a lot of these SCTP error messages and DTLS handshake and socket
removal errors in the logs:

org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49 not
ready yet.
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: 122
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: -62
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: -14
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: 68
org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to remove.

···

On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Thanks Damian,

I think I'm going to purge the ubuntu server and install everything again
from scratch.
What is the current recommended packages that are known to work well with
latest Chrome and ffox (and jigasi)?

Should I use stable or unstable packages?

Cheers,
Peter

On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov <damencho@damencho.com> > wrote:

I haven't seen this, its some problem with capabilities, not sure what
can be the cause of this.

On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> wrote:

Anyone else seeing this NPE in smack or is it just me?
Any hint where I should start looking?

Cheers,
Peter

On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

Hi all,

I updated to latest unstable Debian packages and I'm getting the
following error when trying to dial out via Jigasi

2017-04-03 16:32:51.757 INFO: [65] impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118 Jingle : ON
2017-04-03 16:32:51.758 INFO: [65] org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP (15b34a97146@callcontrol.meet.my.domain):
RegistrationStateChangeEvent[ oldState=Unregistered; ne$
2017-04-03 16:32:51.769 SEVERE: [70] org.jivesoftware.smack.Connection.notifyListener()
null
java.lang.NullPointerException
        at java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
        at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
        at net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager$CapsPacketListener.processPacket(Entity
CapsManager.java:980)
        at org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
        at org.jivesoftware.smack.PacketReader$ListenerNotification.run
(PacketReader.java:403)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Anyone else experiencing this? Where should I start to look to debug
this?

Cheers,
Peter

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

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


#6

Unstable should work, we are trying to fix some stuff in the jvb new features.
Stable I think should be fine, even that jigasi is in the unstable repo.

···

On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

I also noticed that the current install (unstable packages from 2 days ago)
is giving me some problems, specially when clients are behind restrictive
firewalls (and yes I have jetty listening on 443 on AWS and advertising that
ICE candidate).

I see a lot of these SCTP error messages and DTLS handshake and socket
removal errors in the logs:

org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49 not ready
yet.
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: 122
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: -62
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: -14
org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log() Unknown
DTLS handshake message type: 68
org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to remove.

On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Thanks Damian,

I think I'm going to purge the ubuntu server and install everything again
from scratch.
What is the current recommended packages that are known to work well with
latest Chrome and ffox (and jigasi)?

Should I use stable or unstable packages?

Cheers,
Peter

On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov <damencho@damencho.com> >> wrote:

I haven't seen this, its some problem with capabilities, not sure what
can be the cause of this.

On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> wrote:

Anyone else seeing this NPE in smack or is it just me?
Any hint where I should start looking?

Cheers,
Peter

On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:

Hi all,

I updated to latest unstable Debian packages and I'm getting the
following error when trying to dial out via Jigasi

2017-04-03 16:32:51.757 INFO: [65]
impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.registrationStateChanged().118
Jingle : ON
2017-04-03 16:32:51.758 INFO: [65]
org.jitsi.jigasi.JvbConference.registrationStateChanged().546 XMPP
(15b34a97146@callcontrol.meet.my.domain): RegistrationStateChangeEvent[
oldState=Unregistered; ne$
2017-04-03 16:32:51.769 SEVERE: [70]
org.jivesoftware.smack.Connection.notifyListener() null
java.lang.NullPointerException
        at
java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
        at
java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
        at
net.java.sip.communicator.impl.protocol.jabber.extensions.caps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
        at
net.java.sip.communicator.impl.protocol.jabber.extensions.caps.EntityCapsManager$CapsPacketListener.processPacket(EntityCapsManager.java:980)
        at
org.jivesoftware.smack.Connection$ListenerWrapper.notifyListener(Connection.java:877)
        at
org.jivesoftware.smack.PacketReader$ListenerNotification.run(PacketReader.java:403)
        at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Anyone else experiencing this? Where should I start to look to debug
this?

Cheers,
Peter

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

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

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


#7

Thanks, I'll spin up a new debian VPS and install all the packages from
unstable and will report back here any issues.

···

On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> wrote:

Unstable should work, we are trying to fix some stuff in the jvb new
features.
Stable I think should be fine, even that jigasi is in the unstable repo.

On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> I also noticed that the current install (unstable packages from 2 days
ago)
> is giving me some problems, specially when clients are behind restrictive
> firewalls (and yes I have jetty listening on 443 on AWS and advertising
that
> ICE candidate).
>
> I see a lot of these SCTP error messages and DTLS handshake and socket
> removal errors in the logs:
>
> org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49 not
ready
> yet.
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: 122
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: -62
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: -14
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: 68
> org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove.
>
>
> On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve <petervnv1@gmail.com> > > wrote:
>>
>> Thanks Damian,
>>
>> I think I'm going to purge the ubuntu server and install everything
again
>> from scratch.
>> What is the current recommended packages that are known to work well
with
>> latest Chrome and ffox (and jigasi)?
>>
>> Should I use stable or unstable packages?
>>
>> Cheers,
>> Peter
>>
>> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov <damencho@damencho.com> > >> wrote:
>>>
>>> I haven't seen this, its some problem with capabilities, not sure what
>>> can be the cause of this.
>>>
>>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> wrote:
>>>>
>>>> Anyone else seeing this NPE in smack or is it just me?
>>>> Any hint where I should start looking?
>>>>
>>>> Cheers,
>>>> Peter
>>>>
>>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve <petervnv1@gmail.com > > > >>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I updated to latest unstable Debian packages and I'm getting the
>>>>> following error when trying to dial out via Jigasi
>>>>>
>>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.
registrationStateChanged().118
>>>>> Jingle : ON
>>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546 XMPP
>>>>> (15b34a97146@callcontrol.meet.my.domain):
RegistrationStateChangeEvent[
>>>>> oldState=Unregistered; ne$
>>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(
ConcurrentHashMap.java:1106)
>>>>> at
>>>>> java.util.concurrent.ConcurrentHashMap.remove(
ConcurrentHashMap.java:1097)
>>>>> at
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.caps.
EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>>>> at
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.caps.
EntityCapsManager$CapsPacketListener.processPacket(
EntityCapsManager.java:980)
>>>>> at
>>>>> org.jivesoftware.smack.Connection$ListenerWrapper.
notifyListener(Connection.java:877)
>>>>> at
>>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.run(
PacketReader.java:403)
>>>>> at
>>>>> java.util.concurrent.Executors$RunnableAdapter.
call(Executors.java:511)
>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1142)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:617)
>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>
>>>>>
>>>>> Anyone else experiencing this? Where should I start to look to debug
>>>>> this?
>>>>>
>>>>> Cheers,
>>>>> Peter
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#8

A couple of observations so far.

1) Even before trying to run my first conference, I see the same SCTP error
messages described above and the "org.ice4j.socket.MergingDatagramSocket.log()
Cannot find socket to remove." error messages too

2) I noticed that the quick install script also installs nginx and uses it
by default (it would be nice to have the option to disable this behaviour
for people like me that want to just run jetty so as to keep port 443 free
for the videobridge)

3) In my case (fresh Debian Jessie) it also installed JDK 7, which then led
to some errors and I updated to JDK 8, which has led to other errors (more
below). What's the proper version we should be running?

Right now, having installed JDK8 and trying to use Jetty instead of nginx
(which I disabled), I'm getting the following errors when JVB starts:
Any clue what I'm doing wrong?

Cheers,
Peter

JVB 2017-04-05 17:01:15.405 INFO: [14]
org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize() Initialized
mapping harvesters (delay=312ms). stunDiscoveryFailed=false
JVB 2017-04-05 17:01:16.015 INFO: [10]
org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up SecureRandom...
JVB 2017-04-05 17:01:16.019 INFO: [10]
org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up SecureRandom
finished.
JVB 2017-04-05 17:01:16.036 INFO: [10]
org.jitsi.version.AbstractVersionActivator.start().119 JVB Version: JVB
0.1.925
JVB 2017-04-05 17:01:16.129 INFO: [10]
org.eclipse.jetty.util.log.initialized() Logging initialized @3321ms
JVB 2017-04-05 17:01:16.384 INFO: [10]
org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
JVB 2017-04-05 17:01:16.458 INFO: [10]
org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
JVB 2017-04-05 17:01:16.498 INFO: [10]
org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
JVB 2017-04-05 17:01:16.585 WARNING: [10]
org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException: Operation not $
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.588 WARNING: [10]
org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation not permitted
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)

    at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.588 WARNING: [10]
org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation not permitted
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.589 SEVERE: [10]
org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
initialize and/or start a new Jetty HTTP(S) server instance.
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)

  at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.591 SEVERE: [10]
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error changing start level
org.osgi.framework.BundleException: BundleActivator.start
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
Caused by: java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        ... 5 more

···

On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Thanks, I'll spin up a new debian VPS and install all the packages from
unstable and will report back here any issues.

On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> wrote:

Unstable should work, we are trying to fix some stuff in the jvb new
features.
Stable I think should be fine, even that jigasi is in the unstable repo.

On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> I also noticed that the current install (unstable packages from 2 days
ago)
> is giving me some problems, specially when clients are behind
restrictive
> firewalls (and yes I have jetty listening on 443 on AWS and advertising
that
> ICE candidate).
>
> I see a lot of these SCTP error messages and DTLS handshake and socket
> removal errors in the logs:
>
> org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49 not
ready
> yet.
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: 122
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: -62
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: -14
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: 68
> org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove.
>
>
> On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve <petervnv1@gmail.com> >> > wrote:
>>
>> Thanks Damian,
>>
>> I think I'm going to purge the ubuntu server and install everything
again
>> from scratch.
>> What is the current recommended packages that are known to work well
with
>> latest Chrome and ffox (and jigasi)?
>>
>> Should I use stable or unstable packages?
>>
>> Cheers,
>> Peter
>>
>> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov <damencho@damencho.com> >> >> wrote:
>>>
>>> I haven't seen this, its some problem with capabilities, not sure what
>>> can be the cause of this.
>>>
>>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> wrote:
>>>>
>>>> Anyone else seeing this NPE in smack or is it just me?
>>>> Any hint where I should start looking?
>>>>
>>>> Cheers,
>>>> Peter
>>>>
>>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve < >> petervnv1@gmail.com> >> >>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I updated to latest unstable Debian packages and I'm getting the
>>>>> following error when trying to dial out via Jigasi
>>>>>
>>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.re
gistrationStateChanged().118
>>>>> Jingle : ON
>>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546 XMPP
>>>>> (15b34a97146@callcontrol.meet.my.domain):
RegistrationStateChangeEvent[
>>>>> oldState=Unregistered; ne$
>>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
>>>>> at
>>>>> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
>>>>> at
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.
caps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>>>> at
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.
caps.EntityCapsManager$CapsPacketListener.processPacket(Enti
tyCapsManager.java:980)
>>>>> at
>>>>> org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
>>>>> at
>>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.
run(PacketReader.java:403)
>>>>> at
>>>>> java.util.concurrent.Executors$RunnableAdapter.call(
Executors.java:511)
>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>
>>>>>
>>>>> Anyone else experiencing this? Where should I start to look to debug
>>>>> this?
>>>>>
>>>>> Cheers,
>>>>> Peter
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#9

A couple of observations so far.

1) Even before trying to run my first conference, I see the same SCTP error
messages described above and the
"org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to remove."
error messages too

2) I noticed that the quick install script also installs nginx and uses it
by default (it would be nice to have the option to disable this behavior
for people like me that want to just run jetty so as to keep port 443 free
for the videobridge)

If you miss java8 installation defaults on using nginx.

3) In my case (fresh Debian Jessie) it also installed JDK 7, which then led
to some errors and I updated to JDK 8, which has led to other errors (more
below). What's the proper version we should be running?

Right now, having installed JDK8 and trying to use Jetty instead of nginx
(which I disabled), I'm getting the following errors when JVB starts:
Any clue what I'm doing wrong?

If you have java8 installation will default to installing jetty.

Cheers,
Peter

JVB 2017-04-05 17:01:15.405 INFO: [14]
org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize() Initialized
mapping harvesters (delay=312ms). stunDiscoveryFailed=false
JVB 2017-04-05 17:01:16.015 INFO: [10]
org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up SecureRandom...
JVB 2017-04-05 17:01:16.019 INFO: [10]
org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up SecureRandom
finished.
JVB 2017-04-05 17:01:16.036 INFO: [10]
org.jitsi.version.AbstractVersionActivator.start().119 JVB Version: JVB
0.1.925
JVB 2017-04-05 17:01:16.129 INFO: [10]
org.eclipse.jetty.util.log.initialized() Logging initialized @3321ms
JVB 2017-04-05 17:01:16.384 INFO: [10]
org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
JVB 2017-04-05 17:01:16.458 INFO: [10]
org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
JVB 2017-04-05 17:01:16.498 INFO: [10]
org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
JVB 2017-04-05 17:01:16.585 WARNING: [10]
org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
MuxServerConnector@488e6426{SSL-http/1.1}{:::443}: java.net.SocketException:
Operation not $
java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi-meet-web-config.postinst#L140

Regards
damencho

···

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.588 WARNING: [10]
org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException: Operation
not permitted
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)

    at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.588 WARNING: [10]
org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException: Operation
not permitted
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.589 SEVERE: [10]
org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
initialize and/or start a new Jetty HTTP(S) server instance.
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)

  at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.591 SEVERE: [10]
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged() Error
changing start level
org.osgi.framework.BundleException: BundleActivator.start
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
        at
org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:460)
        at
org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:111)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:17)
        at
org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:220)
Caused by: java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at
org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(MuxingServerSocketChannel.java:295)
        at
org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at
org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
        at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at
org.jitsi.rest.AbstractJettyBundleActivator.doStart(AbstractJettyBundleActivator.java:215)
        at
org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJettyBundleActivator.java:537)
        at
org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
        ... 5 more

On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Thanks, I'll spin up a new debian VPS and install all the packages from
unstable and will report back here any issues.

On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> wrote:

Unstable should work, we are trying to fix some stuff in the jvb new
features.
Stable I think should be fine, even that jigasi is in the unstable repo.

On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:
> I also noticed that the current install (unstable packages from 2 days
> ago)
> is giving me some problems, specially when clients are behind
> restrictive
> firewalls (and yes I have jetty listening on 443 on AWS and advertising
> that
> ICE candidate).
>
> I see a lot of these SCTP error messages and DTLS handshake and socket
> removal errors in the logs:
>
> org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49 not
> ready
> yet.
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
> Unknown
> DTLS handshake message type: 122
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
> Unknown
> DTLS handshake message type: -62
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
> Unknown
> DTLS handshake message type: -14
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
> Unknown
> DTLS handshake message type: 68
> org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
> remove.
>
>
> On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve <petervnv1@gmail.com> >>> > wrote:
>>
>> Thanks Damian,
>>
>> I think I'm going to purge the ubuntu server and install everything
>> again
>> from scratch.
>> What is the current recommended packages that are known to work well
>> with
>> latest Chrome and ffox (and jigasi)?
>>
>> Should I use stable or unstable packages?
>>
>> Cheers,
>> Peter
>>
>> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov <damencho@damencho.com> >>> >> wrote:
>>>
>>> I haven't seen this, its some problem with capabilities, not sure
>>> what
>>> can be the cause of this.
>>>
>>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> wrote:
>>>>
>>>> Anyone else seeing this NPE in smack or is it just me?
>>>> Any hint where I should start looking?
>>>>
>>>> Cheers,
>>>> Peter
>>>>
>>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>> >>>> <petervnv1@gmail.com> >>> >>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I updated to latest unstable Debian packages and I'm getting the
>>>>> following error when trying to dial out via Jigasi
>>>>>
>>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>>>>
>>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.registrationStateChanged().118
>>>>> Jingle : ON
>>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546 XMPP
>>>>> (15b34a97146@callcontrol.meet.my.domain):
>>>>> RegistrationStateChangeEvent[
>>>>> oldState=Unregistered; ne$
>>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>>>> java.lang.NullPointerException
>>>>> at
>>>>>
>>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(ConcurrentHashMap.java:1106)
>>>>> at
>>>>>
>>>>> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:1097)
>>>>> at
>>>>>
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.caps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>>>> at
>>>>>
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.caps.EntityCapsManager$CapsPacketListener.processPacket(EntityCapsManager.java:980)
>>>>> at
>>>>>
>>>>> org.jivesoftware.smack.Connection$ListenerWrapper.notifyListener(Connection.java:877)
>>>>> at
>>>>>
>>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.run(PacketReader.java:403)
>>>>> at
>>>>>
>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>>> at
>>>>>
>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>>> at
>>>>>
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>
>>>>>
>>>>> Anyone else experiencing this? Where should I start to look to
>>>>> debug
>>>>> this?
>>>>>
>>>>> Cheers,
>>>>> Peter
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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


#10

I think I'll start a new thread just for this since it's a bit off topic now

···

On Wed, Apr 5, 2017 at 4:04 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

A couple of observations so far.

1) Even before trying to run my first conference, I see the same SCTP
error messages described above and the "org.ice4j.socket.MergingDatagramSocket.log()
Cannot find socket to remove." error messages too

2) I noticed that the quick install script also installs nginx and uses it
by default (it would be nice to have the option to disable this behaviour
for people like me that want to just run jetty so as to keep port 443 free
for the videobridge)

3) In my case (fresh Debian Jessie) it also installed JDK 7, which then
led to some errors and I updated to JDK 8, which has led to other errors
(more below). What's the proper version we should be running?

Right now, having installed JDK8 and trying to use Jetty instead of nginx
(which I disabled), I'm getting the following errors when JVB starts:
Any clue what I'm doing wrong?

Cheers,
Peter

JVB 2017-04-05 17:01:15.405 INFO: [14] org.ice4j.ice.harvest.
MappingCandidateHarvesters.initialize() Initialized mapping harvesters
(delay=312ms). stunDiscoveryFailed=false
JVB 2017-04-05 17:01:16.015 INFO: [10] org.jitsi.impl.neomedia.MediaServiceImpl.log()
Warming up SecureRandom...
JVB 2017-04-05 17:01:16.019 INFO: [10] org.jitsi.impl.neomedia.MediaServiceImpl.log()
Warming up SecureRandom finished.
JVB 2017-04-05 17:01:16.036 INFO: [10] org.jitsi.version.
AbstractVersionActivator.start().119 JVB Version: JVB 0.1.925
JVB 2017-04-05 17:01:16.129 INFO: [10] org.eclipse.jetty.util.log.initialized()
Logging initialized @3321ms
JVB 2017-04-05 17:01:16.384 INFO: [10] org.eclipse.jetty.server.Server.doStart()
jetty-9.2.10.v20150310
JVB 2017-04-05 17:01:16.458 INFO: [10] org.eclipse.jetty.server.
handler.ContextHandler.doStart() Started o.e.j.s.h.ContextHandler@
1d5d4435{/,null,AVAILABLE}
JVB 2017-04-05 17:01:16.498 INFO: [10] org.eclipse.jetty.server.
handler.ContextHandler.doStart() Started o.e.j.s.ServletContextHandler@
2f23fb01{/,null,AVAILABLE}
JVB 2017-04-05 17:01:16.585 WARNING: [10] org.eclipse.jetty.util.
component.AbstractLifeCycle.setFailed() FAILED MuxServerConnector@488e6426
{SSL-http/1.1}{:::443}: java.net.SocketException: Operation not $
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(
ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
        at org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at org.jitsi.rest.MuxServerConnector.open(
MuxServerConnector.java:170)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
        at org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
        at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.
java:293)
        at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.
startLevelChanged(FrameworkImpl.java:460)
        at org.jitsi.impl.osgi.framework.startlevel.
FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
        at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.588 WARNING: [10] org.eclipse.jetty.util.
component.AbstractLifeCycle.setFailed() FAILED org.eclipse.jetty.server.
Server@68fe67c: java.net.SocketException: Operation not permitted
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(
ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
        at org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at org.jitsi.rest.MuxServerConnector.open(
MuxServerConnector.java:170)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)

    at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
        at org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
        at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.
java:293)
        at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.
startLevelChanged(FrameworkImpl.java:460)
        at org.jitsi.impl.osgi.framework.startlevel.
FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
        at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.588 WARNING: [10] org.eclipse.jetty.util.
component.AbstractLifeCycle.setFailed() FAILED org.eclipse.jetty.server.
Server@68fe67c: java.net.SocketException: Operation not permitted
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(
ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
        at org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at org.jitsi.rest.MuxServerConnector.open(
MuxServerConnector.java:170)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
        at org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
        at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.
java:293)
        at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.
startLevelChanged(FrameworkImpl.java:460)
        at org.jitsi.impl.osgi.framework.startlevel.
FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
        at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.589 SEVERE: [10] org.jitsi.rest.
AbstractJettyBundleActivator.doStart().222 Failed to initialize and/or
start a new Jetty HTTP(S) server instance.
java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(
ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
        at org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at org.jitsi.rest.MuxServerConnector.open(
MuxServerConnector.java:170)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)

  at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
        at org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
        at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.
java:293)
        at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.
startLevelChanged(FrameworkImpl.java:460)
        at org.jitsi.impl.osgi.framework.startlevel.
FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
        at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
JVB 2017-04-05 17:01:16.591 SEVERE: [10] org.jitsi.impl.osgi.framework.
launch.FrameworkImpl.startLevelChanged() Error changing start level
org.osgi.framework.BundleException: BundleActivator.start
        at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.
java:313)
        at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.
startLevelChanged(FrameworkImpl.java:460)
        at org.jitsi.impl.osgi.framework.startlevel.
FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:126)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
        at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
        at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
Caused by: java.net.SocketException: Operation not permitted
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(
ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
        at org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
        at org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
        at org.jitsi.rest.MuxServerConnector.open(
MuxServerConnector.java:170)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:366)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
        at org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
        at org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
        at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.
java:293)
        ... 5 more

On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Thanks, I'll spin up a new debian VPS and install all the packages from
unstable and will report back here any issues.

On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> wrote:

Unstable should work, we are trying to fix some stuff in the jvb new
features.
Stable I think should be fine, even that jigasi is in the unstable repo.

On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:
> I also noticed that the current install (unstable packages from 2 days
ago)
> is giving me some problems, specially when clients are behind
restrictive
> firewalls (and yes I have jetty listening on 443 on AWS and
advertising that
> ICE candidate).
>
> I see a lot of these SCTP error messages and DTLS handshake and socket
> removal errors in the logs:
>
> org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49
not ready
> yet.
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: 122
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: -62
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: -14
> org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
Unknown
> DTLS handshake message type: 68
> org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove.
>
>
> On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve <petervnv1@gmail.com> >>> > wrote:
>>
>> Thanks Damian,
>>
>> I think I'm going to purge the ubuntu server and install everything
again
>> from scratch.
>> What is the current recommended packages that are known to work well
with
>> latest Chrome and ffox (and jigasi)?
>>
>> Should I use stable or unstable packages?
>>
>> Cheers,
>> Peter
>>
>> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov <damencho@damencho.com> >>> >> wrote:
>>>
>>> I haven't seen this, its some problem with capabilities, not sure
what
>>> can be the cause of this.
>>>
>>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> >>> wrote:
>>>>
>>>> Anyone else seeing this NPE in smack or is it just me?
>>>> Any hint where I should start looking?
>>>>
>>>> Cheers,
>>>> Peter
>>>>
>>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve < >>> petervnv1@gmail.com> >>> >>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I updated to latest unstable Debian packages and I'm getting the
>>>>> following error when trying to dial out via Jigasi
>>>>>
>>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.re
gistrationStateChanged().118
>>>>> Jingle : ON
>>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546 XMPP
>>>>> (15b34a97146@callcontrol.meet.my.domain):
RegistrationStateChangeEvent[
>>>>> oldState=Unregistered; ne$
>>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
>>>>> at
>>>>> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
>>>>> at
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>>>> at
>>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager$CapsPacketListener.processPacket(Entity
CapsManager.java:980)
>>>>> at
>>>>> org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
>>>>> at
>>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.run
(PacketReader.java:403)
>>>>> at
>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
>>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
>>>>> at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>
>>>>>
>>>>> Anyone else experiencing this? Where should I start to look to
debug
>>>>> this?
>>>>>
>>>>> Cheers,
>>>>> Peter
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#11

Thanks for the info. You might want to add that bit about java8 in the
wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time making
sure I have java 8 as default.

I'll keep you posted.

cheers

···

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same SCTP
error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx and uses
it
> by default (it would be nice to have the option to disable this behavior
> for people like me that want to just run jetty so as to keep port 443
free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7, which then
led
> to some errors and I updated to JDK 8, which has led to other errors
(more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead of nginx
> (which I disabled), I'm getting the following errors when JVB starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB Version: JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized @3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/
jitsi-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
223)
> at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(
FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$
Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
223)
> at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(
FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$
Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
223)
> at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(
FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$
Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
223)
> at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(
FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$
Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(
FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$
Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(
AsyncExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(
AsyncExecutor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(
AsyncExecutor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
223)
> at sun.nio.ch.ServerSocketAdaptor.bind(
ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindServerSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(
MuxServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.
openAndBindMuxServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
AbstractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(
ServerConnector.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
start(AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(
AbstractJettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(
AbstractJettyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve <petervnv1@gmail.com> > > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the packages from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> > wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the jvb new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the unstable
repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve <petervnv1@gmail.com > > > >>> wrote:
>>> > I also noticed that the current install (unstable packages from 2
days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake and
socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49
not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < > petervnv1@gmail.com> > >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to work well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < > damencho@damencho.com> > >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities, not sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> > wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve > >>> >>>> <petervnv1@gmail.com> > >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm getting the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.
registrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546
XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(
ConcurrentHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.remove(
ConcurrentHashMap.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.caps.
EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.caps.
EntityCapsManager$CapsPacketListener.processPacket(
EntityCapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connection$ListenerWrapper.
notifyListener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.run(
PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors$RunnableAdapter.
call(Executors.java:511)
>>> >>>>> at java.util.concurrent.FutureTask.run(FutureTask.
java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#12

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will still
install JDK7 and nginx on your server.

I've also noticed that with latest Firefox (52.0.2) the Set Your display
name area is completely messed up (see screenshot).
I've also noticed that setting enableWelcomePage: false, in the config does
nothing (ie welcome page is still shown).

I'll keep testing. By the way, is p2p ready to test yet? If so, do I just
need to uncomment those options in config?

Cheers,
Peter

···

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Thanks for the info. You might want to add that bit about java8 in the
wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time making
sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same SCTP
error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx and uses
it
> by default (it would be nice to have the option to disable this behavior
> for people like me that want to just run jetty so as to keep port 443
free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7, which then
led
> to some errors and I updated to JDK 8, which has led to other errors
(more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead of
nginx
> (which I disabled), I'm getting the following errors when JVB starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB Version: JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized @3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.
java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.
java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.
java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.
java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.
java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(
AbstractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve <petervnv1@gmail.com> >> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the packages from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> >> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the jvb new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the unstable
repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >> petervnv1@gmail.com> >> >>> wrote:
>>> > I also noticed that the current install (unstable packages from 2
days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake and
socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with a9ec1f49
not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >> petervnv1@gmail.com> >> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to work
well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >> damencho@damencho.com> >> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities, not sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> >> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >> >>> >>>> <petervnv1@gmail.com> >> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm getting the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.re
gistrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546
XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.
caps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.
caps.EntityCapsManager$CapsPacketListener.processPacket(Enti
tyCapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.
run(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors$RunnableAdapter.call(
Executors.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#13

Hi,

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will still
install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your display
name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the config
does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I suppose if
there was a problem with that, it is now fixed. We are currently working
hard on reactifying the whole UI, so we can share as much as possible
between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do I just
need to uncomment those options in config?

There are still features that are not supported like callstats and it is
not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

···

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Thanks for the info. You might want to add that bit about java8 in the
wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time
making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same SCTP
error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx and
uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep port 443
free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7, which
then led
> to some errors and I updated to JDK 8, which has led to other errors
(more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead of
nginx
> (which I disabled), I'm getting the following errors when JVB starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB Version:
JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized @3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve <petervnv1@gmail.com> >>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the packages
from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> >>> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the jvb new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the unstable
repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>> petervnv1@gmail.com> >>> >>> wrote:
>>> > I also noticed that the current install (unstable packages from 2
days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake and
socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>> petervnv1@gmail.com> >>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to work
well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>> damencho@damencho.com> >>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities, not sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> >>> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>> >>> >>>> <petervnv1@gmail.com> >>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm getting
the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.re
gistrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546
XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager$CapsPacketListener.processPacket(Entity
CapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.run
(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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


#14

Hi Damian,

I was using unstable packages, not nightlies.
I will update with latest nightly package and will report back.

Cheers,
Peter

···

On Wed, Apr 5, 2017 at 8:18 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will still
install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your display
name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the config
does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I suppose
if there was a problem with that, it is now fixed. We are currently working
hard on reactifying the whole UI, so we can share as much as possible
between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do I just
need to uncomment those options in config?

There are still features that are not supported like callstats and it is
not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

Thanks for the info. You might want to add that bit about java8 in the
wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time
making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> >>> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same SCTP
error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx and
uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep port 443
free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7, which
then led
> to some errors and I updated to JDK 8, which has led to other errors
(more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead of
nginx
> (which I disabled), I'm getting the following errors when JVB starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB Version:
JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized @3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed() FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve <petervnv1@gmail.com >>>> > >>>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the packages
from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> >>>> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the jvb new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the unstable
repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>>> petervnv1@gmail.com> >>>> >>> wrote:
>>> > I also noticed that the current install (unstable packages from 2
days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake and
socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket
to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>>> petervnv1@gmail.com> >>>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to work
well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>>> damencho@damencho.com> >>>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities, not
sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> >>>> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>>> >>> >>>> <petervnv1@gmail.com> >>>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm getting
the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.re
gistrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546
XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager$CapsPacketListener.processPacket(Entity
CapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.run
(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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

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


#15

unstable == nightlies :slight_smile:
The nightlies go into unstable repo.

···

On Thu, Apr 6, 2017 at 12:23 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Hi Damian,

I was using unstable packages, not nightlies.
I will update with latest nightly package and will report back.

Cheers,
Peter

On Wed, Apr 5, 2017 at 8:18 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will still
install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your display
name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the config
does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I suppose
if there was a problem with that, it is now fixed. We are currently working
hard on reactifying the whole UI, so we can share as much as possible
between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do I
just need to uncomment those options in config?

There are still features that are not supported like callstats and it is
not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

Thanks for the info. You might want to add that bit about java8 in the
wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time
making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> >>>> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve <petervnv1@gmail.com> >>>>> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same
SCTP error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket to
remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx and
uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep port
443 free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7, which
then led
> to some errors and I updated to JDK 8, which has led to other errors
(more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead of
nginx
> (which I disabled), I'm getting the following errors when JVB starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB Version:
JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized @3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve < >>>>> petervnv1@gmail.com> >>>>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the packages
from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> >>>>> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the jvb
new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the unstable
repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>>>> petervnv1@gmail.com> >>>>> >>> wrote:
>>> > I also noticed that the current install (unstable packages from
2 days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake and
socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket
to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>>>> petervnv1@gmail.com> >>>>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to work
well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>>>> damencho@damencho.com> >>>>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities, not
sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> >>>>> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>>>> >>> >>>> <petervnv1@gmail.com> >>>>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm getting
the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.re
gistrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference.registrationStateChanged().546
XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.replaceNode(Concurren
tHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHash
Map.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager.removeUserCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.protocol.jabber.extensions.ca
ps.EntityCapsManager$CapsPacketListener.processPacket(Entity
CapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connection$ListenerWrapper.notifyList
ener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketReader$ListenerNotification.run
(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to look
to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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

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

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


#16

OK, then I'm using nightlies. :slight_smile:
I'll update again today and see if anything changed.

Cheers

···

On Thu, Apr 6, 2017 at 6:36 PM, Damian Minkov <damencho@jitsi.org> wrote:

unstable == nightlies :slight_smile:
The nightlies go into unstable repo.

On Thu, Apr 6, 2017 at 12:23 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Hi Damian,

I was using unstable packages, not nightlies.
I will update with latest nightly package and will report back.

Cheers,
Peter

On Wed, Apr 5, 2017 at 8:18 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will still
install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your
display name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the config
does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I
suppose if there was a problem with that, it is now fixed. We are currently
working hard on reactifying the whole UI, so we can share as much as
possible between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do I
just need to uncomment those options in config?

There are still features that are not supported like callstats and it is
not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:

Thanks for the info. You might want to add that bit about java8 in the
wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time
making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> >>>>> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve < >>>>>> petervnv1@gmail.com> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same
SCTP error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket
to remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx and
uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep port
443 free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7, which
then led
> to some errors and I updated to JDK 8, which has led to other
errors (more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead of
nginx
> (which I disabled), I'm getting the following errors when JVB
starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB
Version: JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized
@3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c: java.net.SocketException:
Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.java:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve < >>>>>> petervnv1@gmail.com> >>>>>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the packages
from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> >>>>>> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the jvb
new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the
unstable repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>>>>> petervnv1@gmail.com> >>>>>> >>> wrote:
>>> > I also noticed that the current install (unstable packages from
2 days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake and
socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find
socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>>>>> petervnv1@gmail.com> >>>>>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to
work well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>>>>> damencho@damencho.com> >>>>>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities, not
sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" <petervnv1@gmail.com> >>>>>> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>>>>> >>> >>>> <petervnv1@gmail.com> >>>>>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm
getting the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.replaceNode(ConcurrentHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.remove(ConcurrentHashMap.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager.removeUse
rCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager$CapsPacke
tListener.processPacket(EntityCapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connect
ion$ListenerWrapper.notifyListener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketR
eader$ListenerNotification.run(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors
$RunnableAdapter.call(Executors.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to look
to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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

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

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

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


#17

Just updated to latest nightly packages, and the problems with Firefox
(52.0.2 64 bit on Mint) remain.
Besides the messed up display mentioned before, there's also no Audio
output menu anymore (only mic and camera) so we can't hear anything.
By the way, noticed the lock room with password feature is gone. Is that
intentional? It was pretty useful feature.

I also just tested on beta.meet.jit.si with Ffox and you have the same
problems on your setup., so it's not me doing something silly on my end.

Let me know what else you'd like me to test.

Cheers,
Peter

···

On Thu, Apr 6, 2017 at 7:54 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

OK, then I'm using nightlies. :slight_smile:
I'll update again today and see if anything changed.

Cheers

On Thu, Apr 6, 2017 at 6:36 PM, Damian Minkov <damencho@jitsi.org> wrote:

unstable == nightlies :slight_smile:
The nightlies go into unstable repo.

On Thu, Apr 6, 2017 at 12:23 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

Hi Damian,

I was using unstable packages, not nightlies.
I will update with latest nightly package and will report back.

Cheers,
Peter

On Wed, Apr 5, 2017 at 8:18 PM, Damian Minkov <damencho@jitsi.org> >>> wrote:

Hi,

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will still
install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your
display name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the config
does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I
suppose if there was a problem with that, it is now fixed. We are currently
working hard on reactifying the whole UI, so we can share as much as
possible between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do I
just need to uncomment those options in config?

There are still features that are not supported like callstats and it
is not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve <petervnv1@gmail.com> >>>>> wrote:

Thanks for the info. You might want to add that bit about java8 in
the wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time
making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> >>>>>> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve < >>>>>>> petervnv1@gmail.com> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same
SCTP error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket
to remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx and
uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep port
443 free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7, which
then led
> to some errors and I updated to JDK 8, which has led to other
errors (more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead
of nginx
> (which I disabled), I'm getting the following errors when JVB
starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB
Version: JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized
@3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed
to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve < >>>>>>> petervnv1@gmail.com> >>>>>>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the
packages from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov <damencho@jitsi.org> >>>>>>> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the jvb
new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the
unstable repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>>>>>> petervnv1@gmail.com> >>>>>>> >>> wrote:
>>> > I also noticed that the current install (unstable packages
from 2 days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake
and socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find
socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>>>>>> petervnv1@gmail.com> >>>>>>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to
work well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>>>>>> damencho@damencho.com> >>>>>>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities, not
sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" < >>>>>>> petervnv1@gmail.com> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>>>>>> >>> >>>> <petervnv1@gmail.com> >>>>>>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm
getting the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.replaceNode(ConcurrentHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.remove(ConcurrentHashMap.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager.removeUse
rCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager$CapsPacke
tListener.processPacket(EntityCapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connect
ion$ListenerWrapper.notifyListener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketR
eader$ListenerNotification.run(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors
$RunnableAdapter.call(Executors.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to
look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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

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

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

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


#18

Ooo about the display name, now I realized we had fixed something else ...
will fix and that one.
Room lock is still there but somehow hidden in the invite dialog.

···

On Thu, Apr 6, 2017 at 2:16 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Just updated to latest nightly packages, and the problems with Firefox
(52.0.2 64 bit on Mint) remain.
Besides the messed up display mentioned before, there's also no Audio
output menu anymore (only mic and camera) so we can't hear anything.
By the way, noticed the lock room with password feature is gone. Is that
intentional? It was pretty useful feature.

I also just tested on beta.meet.jit.si with Ffox and you have the same
problems on your setup., so it's not me doing something silly on my end.

Let me know what else you'd like me to test.

Cheers,
Peter

On Thu, Apr 6, 2017 at 7:54 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

OK, then I'm using nightlies. :slight_smile:
I'll update again today and see if anything changed.

Cheers

On Thu, Apr 6, 2017 at 6:36 PM, Damian Minkov <damencho@jitsi.org> wrote:

unstable == nightlies :slight_smile:
The nightlies go into unstable repo.

On Thu, Apr 6, 2017 at 12:23 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

Hi Damian,

I was using unstable packages, not nightlies.
I will update with latest nightly package and will report back.

Cheers,
Peter

On Wed, Apr 5, 2017 at 8:18 PM, Damian Minkov <damencho@jitsi.org> >>>> wrote:

Hi,

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com> >>>>> wrote:

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will still
install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your
display name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the
config does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I
suppose if there was a problem with that, it is now fixed. We are currently
working hard on reactifying the whole UI, so we can share as much as
possible between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do I
just need to uncomment those options in config?

There are still features that are not supported like callstats and it
is not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve <petervnv1@gmail.com >>>>>> > wrote:

Thanks for the info. You might want to add that bit about java8 in
the wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time
making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> >>>>>>> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve < >>>>>>>> petervnv1@gmail.com> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same
SCTP error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find socket
to remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx
and uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep port
443 free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7,
which then led
> to some errors and I updated to JDK 8, which has led to other
errors (more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead
of nginx
> (which I disabled), I'm getting the following errors when JVB
starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB
Version: JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized
@3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart() Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222 Failed
to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve < >>>>>>>> petervnv1@gmail.com> >>>>>>>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the
packages from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov < >>>>>>>> damencho@jitsi.org> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the
jvb new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the
unstable repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>>>>>>> petervnv1@gmail.com> >>>>>>>> >>> wrote:
>>> > I also noticed that the current install (unstable packages
from 2 days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake
and socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find
socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>>>>>>> petervnv1@gmail.com> >>>>>>>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to
work well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>>>>>>> damencho@damencho.com> >>>>>>>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities,
not sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" < >>>>>>>> petervnv1@gmail.com> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>>>>>>> >>> >>>> <petervnv1@gmail.com> >>>>>>>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm
getting the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.replaceNode(ConcurrentHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.remove(ConcurrentHashMap.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager.removeUse
rCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager$CapsPacke
tListener.processPacket(EntityCapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connect
ion$ListenerWrapper.notifyListener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketR
eader$ListenerNotification.run(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors
$RunnableAdapter.call(Executors.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to
look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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

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

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

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

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


#19

Hi,

You can check beta it is fixed now in latest builds (the profile side bar)

Cheers
damencho

···

On Thu, Apr 6, 2017 at 3:07 PM, Damian Minkov <damencho@jitsi.org> wrote:

Ooo about the display name, now I realized we had fixed something else ...
will fix and that one.
Room lock is still there but somehow hidden in the invite dialog.

On Thu, Apr 6, 2017 at 2:16 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Just updated to latest nightly packages, and the problems with Firefox
(52.0.2 64 bit on Mint) remain.
Besides the messed up display mentioned before, there's also no Audio
output menu anymore (only mic and camera) so we can't hear anything.
By the way, noticed the lock room with password feature is gone. Is that
intentional? It was pretty useful feature.

I also just tested on beta.meet.jit.si with Ffox and you have the same
problems on your setup., so it's not me doing something silly on my end.

Let me know what else you'd like me to test.

Cheers,
Peter

On Thu, Apr 6, 2017 at 7:54 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

OK, then I'm using nightlies. :slight_smile:
I'll update again today and see if anything changed.

Cheers

On Thu, Apr 6, 2017 at 6:36 PM, Damian Minkov <damencho@jitsi.org> >>> wrote:

unstable == nightlies :slight_smile:
The nightlies go into unstable repo.

On Thu, Apr 6, 2017 at 12:23 PM, Peter Villeneuve <petervnv1@gmail.com> >>>> wrote:

Hi Damian,

I was using unstable packages, not nightlies.
I will update with latest nightly package and will report back.

Cheers,
Peter

On Wed, Apr 5, 2017 at 8:18 PM, Damian Minkov <damencho@jitsi.org> >>>>> wrote:

Hi,

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve <petervnv1@gmail.com >>>>>> > wrote:

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will
still install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your
display name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the
config does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I
suppose if there was a problem with that, it is now fixed. We are currently
working hard on reactifying the whole UI, so we can share as much as
possible between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do I
just need to uncomment those options in config?

There are still features that are not supported like callstats and it
is not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve < >>>>>>> petervnv1@gmail.com> wrote:

Thanks for the info. You might want to add that bit about java8 in
the wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this time
making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> >>>>>>>> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve < >>>>>>>>> petervnv1@gmail.com> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the same
SCTP error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find
socket to remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx
and uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep
port 443 free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7,
which then led
> to some errors and I updated to JDK 8, which has led to other
errors (more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty instead
of nginx
> (which I disabled), I'm getting the following errors when JVB
starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB
Version: JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized
@3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart() jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart()
Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart()
Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222
Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve < >>>>>>>>> petervnv1@gmail.com> >>>>>>>>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the
packages from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov < >>>>>>>>> damencho@jitsi.org> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the
jvb new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the
unstable repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>>>>>>>> petervnv1@gmail.com> >>>>>>>>> >>> wrote:
>>> > I also noticed that the current install (unstable packages
from 2 days
>>> > ago)
>>> > is giving me some problems, specially when clients are behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake
and socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transform.dtls.DatagramTransportImpl
.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find
socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>>>>>>>> petervnv1@gmail.com> >>>>>>>>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to
work well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>>>>>>>> damencho@damencho.com> >>>>>>>>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities,
not sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" < >>>>>>>>> petervnv1@gmail.com> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>>>>>>>> >>> >>>> <petervnv1@gmail.com> >>>>>>>>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm
getting the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.replaceNode(ConcurrentHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.remove(ConcurrentHashMap.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager.removeUse
rCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager$CapsPacke
tListener.processPacket(EntityCapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connect
ion$ListenerWrapper.notifyListener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketR
eader$ListenerNotification.run(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors
$RunnableAdapter.call(Executors.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to
look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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

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

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

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

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


#20

Hi,

Just updated all packages and indeed the FFox display issue is fixed!
A couple of issues remain:

1) There is still no Audio Output setting showing up for Ffox (see attached
screenshot) so we cannot hear anything. Audio output works fine in Chrome.
Perhaps these messages regarding deprecated calls on the console could help?

navigator.mozGetUserMedia has been replaced by
navigator.mediaDevices.getUserMedia
WebRTC interfaces with the “moz” prefix (mozRTCPeerConnection,
mozRTCSessionDescription, mozRTCIceCandidate) have been deprecated.
onaddstream is deprecated! Use peerConnection.ontrack instead

2) Also, the welcome screen still shows up even though I have
enableWelcomePage: false, in my config. Not sure what the problem is.

3) Finally, the update also seems to have broken jigasi (which was also
updated). Yesterday I could place outgoing SIP calls (I realize now that
there's no SIP ICE in Jitsi) fine, but today I get this ICE harvester
related error in the jigasi logs and calls never go through. By the way,
even when it was working yesterday I noticed that the usual "alerting
user/ringing/or whatever" message was never shown even when the call went
through OK. In fact there's no visual or audio indication anymore of the
call's status.

2017-04-07 15:24:13.403 SEVERE: [82]
util.UtilActivator.uncaughtException().119 An uncaught exception occurred
in thread=Thread[Thread-51,5,main] and message was:
org/ice4j/ice/harvest/AbstractCandidateHarvester
java.lang.NoClassDefFoundError:
org/ice4j/ice/harvest/AbstractCandidateHarvester
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
        at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.setTransportManager(CallPeerMediaHandlerJabberImpl.java:2112)
        at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1751)
        at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
        at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
        at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1027)
Caused by: java.lang.ClassNotFoundException:
org.ice4j.ice.harvest.AbstractCandidateHarvester
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

Let me know how else I can help debug this.

Cheers,
Peter

···

On Thu, Apr 6, 2017 at 10:40 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

You can check beta it is fixed now in latest builds (the profile side bar)

Cheers
damencho

On Thu, Apr 6, 2017 at 3:07 PM, Damian Minkov <damencho@jitsi.org> wrote:

Ooo about the display name, now I realized we had fixed something else
... will fix and that one.
Room lock is still there but somehow hidden in the invite dialog.

On Thu, Apr 6, 2017 at 2:16 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

Just updated to latest nightly packages, and the problems with Firefox
(52.0.2 64 bit on Mint) remain.
Besides the messed up display mentioned before, there's also no Audio
output menu anymore (only mic and camera) so we can't hear anything.
By the way, noticed the lock room with password feature is gone. Is that
intentional? It was pretty useful feature.

I also just tested on beta.meet.jit.si with Ffox and you have the same
problems on your setup., so it's not me doing something silly on my end.

Let me know what else you'd like me to test.

Cheers,
Peter

On Thu, Apr 6, 2017 at 7:54 PM, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:

OK, then I'm using nightlies. :slight_smile:
I'll update again today and see if anything changed.

Cheers

On Thu, Apr 6, 2017 at 6:36 PM, Damian Minkov <damencho@jitsi.org> >>>> wrote:

unstable == nightlies :slight_smile:
The nightlies go into unstable repo.

On Thu, Apr 6, 2017 at 12:23 PM, Peter Villeneuve <petervnv1@gmail.com >>>>> > wrote:

Hi Damian,

I was using unstable packages, not nightlies.
I will update with latest nightly package and will report back.

Cheers,
Peter

On Wed, Apr 5, 2017 at 8:18 PM, Damian Minkov <damencho@jitsi.org> >>>>>> wrote:

Hi,

On Wed, Apr 5, 2017 at 2:04 PM, Peter Villeneuve < >>>>>>> petervnv1@gmail.com> wrote:

A few things I've noticed already.
Even if you have JDK8 already installed, the quick install will
still install JDK7 and nginx on your server.

Do you have this package installed openjdk-8-jre-headless ?

I've also noticed that with latest Firefox (52.0.2) the Set Your
display name area is completely messed up (see screenshot).

This was recently fixed in nightlies.

I've also noticed that setting enableWelcomePage: false, in the
config does nothing (ie welcome page is still shown).

This is working for me on meet.jit.si and beta.meet.jit.si, so I
suppose if there was a problem with that, it is now fixed. We are currently
working hard on reactifying the whole UI, so we can share as much as
possible between web and mobile.

I'll keep testing. By the way, is p2p ready to test yet? If so, do
I just need to uncomment those options in config?

There are still features that are not supported like callstats and
it is not enabled on mobile, so generally it is working.

Hum, if you see the p2p thing you should be using nightlies, is this
correct? Then it is strange about the problems with translation (empty
strings ) and welcompage, are you uptodate with latest versions?

Regards
damencho

Cheers,
Peter

On Wed, Apr 5, 2017 at 5:08 PM, Peter Villeneuve < >>>>>>>> petervnv1@gmail.com> wrote:

Thanks for the info. You might want to add that bit about java8 in
the wiki. If I had known that I would have updated java before installing
jisti-meet, instead of after.
I think I'll just purge the installation and start again, this
time making sure I have java 8 as default.

I'll keep you posted.

cheers

On Wed, Apr 5, 2017 at 4:56 PM, Damian Minkov <damencho@jitsi.org> >>>>>>>>> wrote:

On Wed, Apr 5, 2017 at 10:04 AM, Peter Villeneuve < >>>>>>>>>> petervnv1@gmail.com> wrote:
> A couple of observations so far.
>
> 1) Even before trying to run my first conference, I see the
same SCTP error
> messages described above and the
> "org.ice4j.socket.MergingDatagramSocket.log() Cannot find
socket to remove."
> error messages too
>
> 2) I noticed that the quick install script also installs nginx
and uses it
> by default (it would be nice to have the option to disable this
behavior
> for people like me that want to just run jetty so as to keep
port 443 free
> for the videobridge)
If you miss java8 installation defaults on using nginx.

>
> 3) In my case (fresh Debian Jessie) it also installed JDK 7,
which then led
> to some errors and I updated to JDK 8, which has led to other
errors (more
> below). What's the proper version we should be running?
>
>
> Right now, having installed JDK8 and trying to use Jetty
instead of nginx
> (which I disabled), I'm getting the following errors when JVB
starts:
> Any clue what I'm doing wrong?
If you have java8 installation will default to installing jetty.

>
> Cheers,
> Peter
>
>
> JVB 2017-04-05 17:01:15.405 INFO: [14]
> org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize()
Initialized
> mapping harvesters (delay=312ms). stunDiscoveryFailed=false
> JVB 2017-04-05 17:01:16.015 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom...
> JVB 2017-04-05 17:01:16.019 INFO: [10]
> org.jitsi.impl.neomedia.MediaServiceImpl.log() Warming up
SecureRandom
> finished.
> JVB 2017-04-05 17:01:16.036 INFO: [10]
> org.jitsi.version.AbstractVersionActivator.start().119 JVB
Version: JVB
> 0.1.925
> JVB 2017-04-05 17:01:16.129 INFO: [10]
> org.eclipse.jetty.util.log.initialized() Logging initialized
@3321ms
> JVB 2017-04-05 17:01:16.384 INFO: [10]
> org.eclipse.jetty.server.Server.doStart()
jetty-9.2.10.v20150310
> JVB 2017-04-05 17:01:16.458 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart()
Started
> o.e.j.s.h.ContextHandler@1d5d4435{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.498 INFO: [10]
> org.eclipse.jetty.server.handler.ContextHandler.doStart()
Started
> o.e.j.s.ServletContextHandler@2f23fb01{/,null,AVAILABLE}
> JVB 2017-04-05 17:01:16.585 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> MuxServerConnector@488e6426{SSL-http/1.1}{:::443}:
java.net.SocketException:
> Operation not $
> java.net.SocketException: Operation not permitted

Normal OS users are not allowed to bind to port < 1024, and its
the
same by default for jvb user. You need to configure authbind:
Check out how Debian package is doing it:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst#L140

Regards
damencho

> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.588 WARNING: [10]
> org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed()
FAILED
> org.eclipse.jetty.server.Server@68fe67c:
java.net.SocketException: Operation
> not permitted
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.589 SEVERE: [10]
> org.jitsi.rest.AbstractJettyBundleActivator.doStart().222
Failed to
> initialize and/or start a new Jetty HTTP(S) server instance.
> java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
>
>
>
>
>
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> JVB 2017-04-05 17:01:16.591 SEVERE: [10]
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged()
Error
> changing start level
> org.osgi.framework.BundleException: BundleActivator.start
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:313)
> at
> org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLeve
lChanged(FrameworkImpl.java:460)
> at
> org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevel
Impl$Command.run(FrameworkStartLevelImpl.java:126)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(Asyn
cExecutor.java:111)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(Async
Executor.java:17)
> at
> org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecu
tor.java:220)
> Caused by: java.net.SocketException: Operation not permitted
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelI
mpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor
.bind(ServerSocketAdaptor.java:74)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindSe
rverSocketChannel(MuxServerSocketChannelFactory.java:261)
> at
> org.ice4j.socket.jdk8.MuxingServerSocketChannel.openAndBind(
MuxingServerSocketChannel.java:295)
> at
> org.ice4j.socket.jdk8.MuxServerSocketChannel.openAndBind(Mux
ServerSocketChannel.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
ssorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.ice4j.socket.MuxServerSocketChannelFactory.openAndBindMu
xServerSocketChannel(MuxServerSocketChannelFactory.java:181)
> at
> org.jitsi.rest.MuxServerConnector.open(MuxServerConnector.ja
va:170)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(Ab
stractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConne
ctor.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at org.eclipse.jetty.server.Serve
r.doStart(Server.java:366)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(Abs
tractLifeCycle.java:68)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.doStart(Abstract
JettyBundleActivator.java:215)
> at
> org.jitsi.rest.AbstractJettyBundleActivator.start(AbstractJe
ttyBundleActivator.java:537)
> at
> org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.ja
va:293)
> ... 5 more
>
>
>
>
>
> On Tue, Apr 4, 2017 at 4:51 PM, Peter Villeneuve < >>>>>>>>>> petervnv1@gmail.com> >>>>>>>>>> > wrote:
>>
>> Thanks, I'll spin up a new debian VPS and install all the
packages from
>> unstable and will report back here any issues.
>>
>>
>> On Tue, Apr 4, 2017 at 4:36 PM, Damian Minkov < >>>>>>>>>> damencho@jitsi.org> wrote:
>>>
>>> Unstable should work, we are trying to fix some stuff in the
jvb new
>>> features.
>>> Stable I think should be fine, even that jigasi is in the
unstable repo.
>>>
>>>
>>> On Tue, Apr 4, 2017 at 10:31 AM, Peter Villeneuve < >>>>>>>>>> petervnv1@gmail.com> >>>>>>>>>> >>> wrote:
>>> > I also noticed that the current install (unstable packages
from 2 days
>>> > ago)
>>> > is giving me some problems, specially when clients are
behind
>>> > restrictive
>>> > firewalls (and yes I have jetty listening on 443 on AWS and
advertising
>>> > that
>>> > ICE candidate).
>>> >
>>> > I see a lot of these SCTP error messages and DTLS handshake
and socket
>>> > removal errors in the logs:
>>> >
>>> > org.jitsi.videobridge.Endpoint.log() SCTP connection with
a9ec1f49 not
>>> > ready
>>> > yet.
>>> > org.jitsi.impl.neomedia.transf
orm.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 122
>>> > org.jitsi.impl.neomedia.transf
orm.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -62
>>> > org.jitsi.impl.neomedia.transf
orm.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: -14
>>> > org.jitsi.impl.neomedia.transf
orm.dtls.DatagramTransportImpl.log()
>>> > Unknown
>>> > DTLS handshake message type: 68
>>> > org.ice4j.socket.MergingDatagramSocket.log() Cannot find
socket to
>>> > remove.
>>> >
>>> >
>>> > On Tue, Apr 4, 2017 at 4:27 PM, Peter Villeneuve < >>>>>>>>>> petervnv1@gmail.com> >>>>>>>>>> >>> > wrote:
>>> >>
>>> >> Thanks Damian,
>>> >>
>>> >> I think I'm going to purge the ubuntu server and install
everything
>>> >> again
>>> >> from scratch.
>>> >> What is the current recommended packages that are known to
work well
>>> >> with
>>> >> latest Chrome and ffox (and jigasi)?
>>> >>
>>> >> Should I use stable or unstable packages?
>>> >>
>>> >> Cheers,
>>> >> Peter
>>> >>
>>> >> On Tue, Apr 4, 2017 at 4:16 PM, Damian Minkov < >>>>>>>>>> damencho@damencho.com> >>>>>>>>>> >>> >> wrote:
>>> >>>
>>> >>> I haven't seen this, its some problem with capabilities,
not sure
>>> >>> what
>>> >>> can be the cause of this.
>>> >>>
>>> >>> On Apr 4, 2017 07:27, "Peter Villeneuve" < >>>>>>>>>> petervnv1@gmail.com> wrote:
>>> >>>>
>>> >>>> Anyone else seeing this NPE in smack or is it just me?
>>> >>>> Any hint where I should start looking?
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Peter
>>> >>>>
>>> >>>> On Mon, Apr 3, 2017 at 5:42 PM, Peter Villeneuve >>>>>>>>>> >>> >>>> <petervnv1@gmail.com> >>>>>>>>>> >>> >>>> wrote:
>>> >>>>>
>>> >>>>> Hi all,
>>> >>>>>
>>> >>>>> I updated to latest unstable Debian packages and I'm
getting the
>>> >>>>> following error when trying to dial out via Jigasi
>>> >>>>>
>>> >>>>> 2017-04-03 16:32:51.757 INFO: [65]
>>> >>>>>
>>> >>>>> impl.protocol.jabber.Operation
SetBasicTelephonyJabberImpl.registrationStateChanged().118
>>> >>>>> Jingle : ON
>>> >>>>> 2017-04-03 16:32:51.758 INFO: [65]
>>> >>>>> org.jitsi.jigasi.JvbConference
.registrationStateChanged().546 XMPP
>>> >>>>> (15b34a97146@callcontrol.meet.my.domain):
>>> >>>>> RegistrationStateChangeEvent[
>>> >>>>> oldState=Unregistered; ne$
>>> >>>>> 2017-04-03 16:32:51.769 SEVERE: [70]
>>> >>>>> org.jivesoftware.smack.Connection.notifyListener() null
>>> >>>>> java.lang.NullPointerException
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.replaceNode(ConcurrentHashMap.java:1106)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Concurren
tHashMap.remove(ConcurrentHashMap.java:1097)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager.removeUse
rCapsNode(EntityCapsManager.java:359)
>>> >>>>> at
>>> >>>>>
>>> >>>>> net.java.sip.communicator.impl.
protocol.jabber.extensions.caps.EntityCapsManager$CapsPacke
tListener.processPacket(EntityCapsManager.java:980)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.Connect
ion$ListenerWrapper.notifyListener(Connection.java:877)
>>> >>>>> at
>>> >>>>>
>>> >>>>> org.jivesoftware.smack.PacketR
eader$ListenerNotification.run(PacketReader.java:403)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.Executors
$RunnableAdapter.call(Executors.java:511)
>>> >>>>> at java.util.concurrent.FutureTas
k.run(FutureTask.java:266)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>> >>>>> at
>>> >>>>>
>>> >>>>> java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>> >>>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>>>
>>> >>>>>
>>> >>>>> Anyone else experiencing this? Where should I start to
look to
>>> >>>>> debug
>>> >>>>> this?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Peter
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> dev mailing list
>>> >>>> dev@jitsi.org
>>> >>>> Unsubscribe instructions and other list options:
>>> >>>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> dev mailing list
>>> >>> dev@jitsi.org
>>> >>> Unsubscribe instructions and other list options:
>>> >>> http://lists.jitsi.org/mailman/listinfo/dev
>>> >>
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > dev mailing list
>>> > dev@jitsi.org
>>> > Unsubscribe instructions and other list options:
>>> > http://lists.jitsi.org/mailman/listinfo/dev
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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

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

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

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

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

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