SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Exception in thread "main" org.xmpp.component.ComponentException: host-unknown
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.videobridge.Main.main(Main.java:173)
http://www.slf4j.org/codes.html#StaticLoggerBinder shows:
This error is reported when the org.slf4j.impl.StaticLoggerBinder class
could not be loaded into memory. This happens when no appropriate SLF4J
binding could be found on the class path. Placing one (and only one) of
slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or
logback-classic.jar on the class path should solve the problem.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Exception in thread "main" org.xmpp.component.ComponentException: host-unknown
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.videobridge.Main.main(Main.java:173)
Your xmpp server is telling the JVB that it does not have a configuration for the hostname the bridge is trying to connect as. which should be jitsi-videobridge.chat.example.net.
http://www.slf4j.org/codes.html#StaticLoggerBinder shows:
This error is reported when the org.slf4j.impl.StaticLoggerBinder class
could not be loaded into memory. This happens when no appropriate SLF4J
binding could be found on the class path. Placing one (and only one) of
slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or
logback-classic.jar on the class path should solve the problem.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Exception in thread "main" org.xmpp.component.ComponentException:
host-unknown
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.videobridge.Main.main(Main.java:173)
Your xmpp server is telling the JVB that it does not have a configuration
for the hostname the bridge is trying to connect as. which should be jitsi-videobridge.chat.example.net.
This and setting up the /etc/restund.conf are exactly what was needed.
Thanks so much for pointing this host error to me. I thought for sure
something was missing on my system but I didn't fully read the error!
There are my config files. If anyone finds an error, I'll update at pastiebin.
http://www.slf4j.org/codes.html#StaticLoggerBinder shows:
This error is reported when the org.slf4j.impl.StaticLoggerBinder class
could not be loaded into memory. This happens when no appropriate SLF4J
binding could be found on the class path. Placing one (and only one) of
slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or
logback-classic.jar on the class path should solve the problem.
Yes, thanks and thank you for your development efforts on andyet and
of course, jitsi meet. I'm sure you and all the brilliant Jitsi people
will have new things very soon!
Hi jungleboogie0, in prosody config smacks3 smacks2 are superseded and all included in a module just labelled smacks. Publishing logs of prosody and nginx servers might also be useful. Regards - John
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Exception in thread "main" org.xmpp.component.ComponentException:
host-unknown
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.videobridge.Main.main(Main.java:173)
Your xmpp server is telling the JVB that it does not have a configuration
for the hostname the bridge is trying to connect as. which should be jitsi-videobridge.chat.example.net.
This and setting up the /etc/restund.conf are exactly what was needed.
Thanks so much for pointing this host error to me. I thought for sure
something was missing on my system but I didn't fully read the error!
There are my config files. If anyone finds an error, I'll update at pastiebin.
http://www.slf4j.org/codes.html#StaticLoggerBinder shows:
This error is reported when the org.slf4j.impl.StaticLoggerBinder class
could not be loaded into memory. This happens when no appropriate SLF4J
binding could be found on the class path. Placing one (and only one) of
slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or
logback-classic.jar on the class path should solve the problem.
Yes, thanks and thank you for your development efforts on andyet and
of course, jitsi meet. I'm sure you and all the brilliant Jitsi people
will have new things very soon!
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Mon, 12 May 2014 11:17:02 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi jungleboogie0, in prosody config smacks3 smacks2 are superseded and all
included in a module just labelled smacks. Publishing logs of prosody and
nginx servers might also be useful. Regards - John
So I can just list "smacks"; as a module and delete?:
"smacks3";
"smacks2";
Regarding logging:
-- Logging configuration
-- For advanced logging see http://prosody.im/doc/logging
log = {
info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for
verbose logging
error = "/var/log/prosody/prosody.err";
For nginx:
error_log /var/log/nginx/error.log warn;
and
it looks like there's already a /var/log/nginx/access.log
Is this sufficient?
I also updated restund.conf to include correct IP addresses for udp_listen
& tcp_listen. The install instructions mention "Configure addresses and
ports as desired" but nothing specific is listed.
I don't know if I supposed to telnet localhost 5582 but the connection is
refused each time.
root@chat:~# telnet localhost 5582
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
Hi John,
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Mon, 12 May 2014 11:17:02 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi jungleboogie0, in prosody config smacks3 smacks2 are superseded and all
included in a module just labelled smacks. Publishing logs of prosody and
nginx servers might also be useful. Regards - John
So I can just list "smacks"; as a module and delete?:
"smacks3";
"smacks2";
Yes. You might be reading an older document somewhere, we updated this
on the official instructions[1] with this.
Hi Jungle, yeah your telnet access won't work until you don't enable this in your prosody configuration file
"admin_telnet"; -- Opens telnet console interface on localhost port 5582
Actually that looks commented out in the file you posted, that step is also not mentioned in the jitmeet template and instructions.
/var/log/nginx/error.log , /var/log/nginx/access.log, /var/log/prosody/prosody.log and /var/log/prosody/prosody.err are good places where to look at , in order to see what's going on and on bad way.
Regards - Johhn
···
On 15/05/2014 22:59, Jungle Boogie wrote:
Hi John,
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Mon, 12 May 2014 11:17:02 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi jungleboogie0, in prosody config smacks3 smacks2 are superseded and all
included in a module just labelled smacks. Publishing logs of prosody and
nginx servers might also be useful. Regards - John
So I can just list "smacks"; as a module and delete?:
"smacks3";
"smacks2";
Regarding logging:
-- Logging configuration
-- For advanced logging see http://prosody.im/doc/logging
log = {
info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for
verbose logging
error = "/var/log/prosody/prosody.err";
For nginx:
error_log /var/log/nginx/error.log warn;
and
it looks like there's already a /var/log/nginx/access.log
Is this sufficient?
I also updated restund.conf to include correct IP addresses for udp_listen
& tcp_listen. The install instructions mention "Configure addresses and
ports as desired" but nothing specific is listed.
I don't know if I supposed to telnet localhost 5582 but the connection is
refused each time.
root@chat:~# telnet localhost 5582
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
--------------------------------------------------------
From: Boris Grozev <boris@jitsi.org>
Sent: Thu, 15 May 2014 23:09:10 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hello,
On 15/05/14 22:59, Jungle Boogie wrote:
Hi John,
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Mon, 12 May 2014 11:17:02 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi jungleboogie0, in prosody config smacks3 smacks2 are superseded and all
included in a module just labelled smacks. Publishing logs of prosody and
nginx servers might also be useful. Regards - John
So I can just list "smacks"; as a module and delete?:
"smacks3";
"smacks2";
Yes. You might be reading an older document somewhere, we updated this
on the official instructions[1] with this.
Ah, good catch, thanks! I updated the examples and moved them to the
github repo.
Regards,
Boris
···
On 15/05/14 23:21, Jungle Boogie wrote:
Hi Boris,
--------------------------------------------------------
From: Boris Grozev <boris@jitsi.org>
Sent: Thu, 15 May 2014 23:09:10 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hello,
On 15/05/14 22:59, Jungle Boogie wrote:
Hi John,
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Mon, 12 May 2014 11:17:02 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi jungleboogie0, in prosody config smacks3 smacks2 are superseded and all
included in a module just labelled smacks. Publishing logs of prosody and
nginx servers might also be useful. Regards - John
So I can just list "smacks"; as a module and delete?:
"smacks3";
"smacks2";
Yes. You might be reading an older document somewhere, we updated this
on the official instructions[1] with this.
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Fri, 16 May 2014 13:17:52 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi Jungle, yeah your telnet access won't work until you don't enable this
in your prosody configuration file
"admin_telnet"; -- Opens telnet console interface on localhost port 5582
Actually that looks commented out in the file you posted, that step is
also not mentioned in the jitmeet template and instructions.
Yeah, I noticed this too.
Boris,
Maybe you could amend the install instructions[0] to remove:
prosodyctl reload
telnet localhost 5582
module:reload("turncredentials", "jitsi.example.com")
quit
Since the prosody config file[1] has telnet disabled.
Also, could it be explained how etherpad is installed on meet.jit.si ?
/var/log/nginx/error.log , /var/log/nginx/access.log,
/var/log/prosody/prosody.log and /var/log/prosody/prosody.err are good
places where to look at , in order to see what's going on and on bad way.
Regards - Johhn
On 15/05/2014 22:59, Jungle Boogie wrote:
Hi John,
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Mon, 12 May 2014 11:17:02 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi jungleboogie0, in prosody config smacks3 smacks2 are superseded and all
included in a module just labelled smacks. Publishing logs of prosody and
nginx servers might also be useful. Regards - John
So I can just list "smacks"; as a module and delete?:
"smacks3";
"smacks2";
Regarding logging:
-- Logging configuration
-- For advanced logging see http://prosody.im/doc/logging
log = {
info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for
verbose logging
error = "/var/log/prosody/prosody.err";
For nginx:
error_log /var/log/nginx/error.log warn;
and
it looks like there's already a /var/log/nginx/access.log
Is this sufficient?
I also updated restund.conf to include correct IP addresses for udp_listen
& tcp_listen. The install instructions mention "Configure addresses and
ports as desired" but nothing specific is listed.
I don't know if I supposed to telnet localhost 5582 but the connection is
refused each time.
root@chat:~# telnet localhost 5582
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
Hi John,
--------------------------------------------------------
From: john <zbeiley@gmx.de>
Sent: Fri, 16 May 2014 13:17:52 +0200
To: Jitsi Developers
Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
--domain=chat.example.net --port=5347 --secret=emiljitsi
Hi Jungle, yeah your telnet access won't work until you don't enable this
in your prosody configuration file
"admin_telnet"; -- Opens telnet console interface on localhost port 5582
Actually that looks commented out in the file you posted, that step is
also not mentioned in the jitmeet template and instructions.
Yeah, I noticed this too.
Boris,
Maybe you could amend the install instructions[0] to remove:
prosodyctl reload
telnet localhost 5582
module:reload("turncredentials", "jitsi.example.com")
quit
Since the prosody config file[1] has telnet disabled.
Just to note, that was intentional with the reload, in order to have
instructions to enable modules without restarting the server and kill all
running meetings.
Regards
damencho
--sent from my mobile
···
On May 16, 2014 11:42 PM, "Boris Grozev" <boris@jitsi.org> wrote:
On 16/05/14 20:51, Jungle Boogie wrote:
> Hi John,
> --------------------------------------------------------
> From: john <zbeiley@gmx.de>
> Sent: Fri, 16 May 2014 13:17:52 +0200
> To: Jitsi Developers
> Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
> --domain=chat.example.net --port=5347 --secret=emiljitsi
>> Hi Jungle, yeah your telnet access won't work until you don't enable
this
>> in your prosody configuration file
>>
>> "admin_telnet"; -- Opens telnet console interface on localhost port 5582
>>
>> Actually that looks commented out in the file you posted, that step is
>> also not mentioned in the jitmeet template and instructions.
>
> Yeah, I noticed this too.
>
> Boris,
>
> Maybe you could amend the install instructions[0] to remove:
> prosodyctl reload
> telnet localhost 5582
> module:reload("turncredentials", "jitsi.example.com")
> quit
>
> Since the prosody config file[1] has telnet disabled.
Just to note, that was intentional with the reload, in order to have
instructions to enable modules without restarting the server and kill all
running meetings.
At what prompt would you actually type "module:reload("
turncredentials", "jitsi.example.com")", the shell prompt? Doing this
will give an error as it doesn't know what you're trying to do.
The telnet listener is disabled in the prosody.cfg.lua.example[0] so
that's why Boris removed it from the instructions.
Reviewing the prosodyctl[1], it does not look like there's an option
to reload modules, simply "prosodyctl reload" would probably be
sufficient and now the instructions have "prosody restart".
The turn server section[2] could also use it's own full example and
some more instructions on configuring, since this is what's used to
send/receive video/audio. My restund.conf example[3] shows the IP
address needing to be updated in a few places.
On May 16, 2014 11:42 PM, "Boris Grozev" <boris@jitsi.org> wrote:
On 16/05/14 20:51, Jungle Boogie wrote:
> Hi John,
> --------------------------------------------------------
> From: john <zbeiley@gmx.de>
> Sent: Fri, 16 May 2014 13:17:52 +0200
> To: Jitsi Developers
> Subject: Re: [jitsi-dev] ./jitsivideo/jvb.sh --host=localhost
> --domain=chat.example.net --port=5347 --secret=emiljitsi
>> Hi Jungle, yeah your telnet access won't work until you don't enable
>> this
>> in your prosody configuration file
>>
>> "admin_telnet"; -- Opens telnet console interface on localhost port
>> 5582
>>
>> Actually that looks commented out in the file you posted, that step is
>> also not mentioned in the jitmeet template and instructions.
>
> Yeah, I noticed this too.
>
> Boris,
>
> Maybe you could amend the install instructions[0] to remove:
> prosodyctl reload
> telnet localhost 5582
> module:reload("turncredentials", "jitsi.example.com")
> quit
>
> Since the prosody config file[1] has telnet disabled.
Yes, I thought so. Do you want me to revert it and enable to admin
console instead?
Boris
···
On 17/05/14 11:01, Damian Minkov wrote:
Hi,
Just to note, that was intentional with the reload, in order to have
instructions to enable modules without restarting the server and kill
all running meetings.
No, its ok now. I was thinking of something like: (if you have or if you
enable telnet module you can load module turn .... like this ....) Just one
more description near current restart of prosody that you've added.
I think just reloading was not working, or there was a reason to do this
telnet stuff in order not to restart meet.jit.si when adding turn there,
and there can be other similar occasions.
Thanks
--sent from my mobile
···
On May 17, 2014 11:35 PM, "Boris Grozev" <boris@jitsi.org> wrote:
On 17/05/14 11:01, Damian Minkov wrote:
> Hi,
>
> Just to note, that was intentional with the reload, in order to have
> instructions to enable modules without restarting the server and kill
> all running meetings.
Yes, I thought so. Do you want me to revert it and enable to admin
console instead?