Jitsi jibri installation

I have installed on one machine both Jibri and JITSI MEET . I am having an error when i start the recording . The log files for JVB.log is showing an error

2020-08-14 09:49:56.278 WARNING: [22] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$8#669: [MucClient id=shard hostname=localhost] error connecting
org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: ‘localhost:5222’ failed because: localhost/127.0.0.1 exception: java.net.ConnectException: Connec$
at org.jivesoftware.smack.SmackException$ConnectionException.from(SmackException.java:278)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:619)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:902)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:383)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$8(MucClient.java:664)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2020-08-14 09:50:01.207 INFO: [20] TaskPools.#81: TaskPools detected 4 processors, creating the CPU pool with that many threads
2020-08-14 09:50:01.209 INFO: [20] Videobridge.createConference#255: create_conf, id=eae7d8f2c386f378 gid=-1 logging=false
2020-08-14 09:50:01.279 WARNING: [22] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$8#669: [MucClient id=shard hostname=localhost] error connecting
org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: ‘localhost:5222’ failed because: localhost/127.0.0.1 exception: java.net.ConnectException: Connec$
at org.jivesoftware.smack.SmackException$ConnectionException.from(SmackException.java:278)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:619)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:902)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:383)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$8(MucClient.java:664)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

My JICOFO Log

rg.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-condi$
stream:errorReceived SIGTERM</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1064)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)
Jicofo 2020-08-14 10:14:34.177 SEVERE: [37] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() XMPP connection closed on error: system-shutdown You can read more about the meaning of <stream:error><system-shutdown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>Received SIGTERM</text></stream:error> Jicofo 2020-08-14 10:14:34.177 INFO: [37] org.jitsi.jicofo.ProtocolProviderHandler.log() XmppProtocolProvider(focus@auth.meet.yugapat.com/focus14225473011 (Jabber)): RegistrationStateChang
Jicofo 2020-08-14 10:14:34.178 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.log() Left brewery room: JibriBrewery@internal.auth.meet.yugapat.com
Jicofo 2020-08-14 10:14:34.179 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.log() Removed brewery instance: jibribrewery@internal.auth.meet.yugapat.com/Live
Jicofo 2020-08-14 10:14:34.179 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.log() Jibri: jibribrewery@internal.auth.meet.yugapat.com/Live went offline
Jicofo 2020-08-14 10:14:34.180 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.log() Left brewery room: JvbBrewery@internal.auth.meet.yugapat.com
Jicofo 2020-08-14 10:14:34.180 INFO: [37] org.jitsi.jicofo.ComponentsDiscovery.log() Connection lo

@damencho need your guidance struggling to get the jibri installed for recording and streaming .

root@ip-172-31-32-216:/var/log/jitsi# echo hello | nc localhost 5222

<?xml version='1.0'?>root@ip-172-31-32-216:/var/log/jitsi#

Hi! Make sure that the prosody (XMPP Server) is up and running. Neither your JVB or Jicofo could connect to your Prosody Server. You could check this by running this command:

systemctl status prosody

It must be running, without errors and listening, at least, on ports 5222 and 5437. You could check the listening ports by running the following:

ss -ln64

I hope this can help you!

Hi

Thanks for the help @danhcs, I did check if the service is running and it is running . Prosody is listening at 5222 and also on 5347

tcp6 0 0 :::443 :::* LISTEN 1092/nginx: master
tcp6 0 0 :::4444 :::* LISTEN 1092/nginx: master
tcp6 0 0 :::5280 :::* LISTEN 1501/lua5.2
tcp6 0 0 ::1:5347 :::* LISTEN 1501/lua5.2
tcp6 0 0 :::3333 :::* LISTEN 950/java
tcp6 0 0 ::1:5349 :::* LISTEN 1098/turnserver
tcp6 0 0 ::1:5349 :::* LISTEN 1098/turnserver
tcp6 0 0 ::1:5349 :::* LISTEN 1098/turnserver
tcp6 0 0 ::1:5349 :::* LISTEN 1098/turnserver
tcp6 0 0 :::5222 :::* LISTEN 1501/lua5.2
tcp6 0 0 :::2222 :::* LISTEN 950/java
tcp6 0 0 :::8080 :::* LISTEN 946/java
tcp6 0 0 :::80 :::* LISTEN 1092/nginx: master
tcp6 0 0 :::5269 :::* LISTEN 1501/lua5.2
tcp6 0 0 :::8086 :::* LISTEN 972/influxd
tcp6 0 0 :::22 :::* LISTEN 1038/sshd
udp 0 0 172.31.32.216:3478 0.0.0.0:* 1098/turnserver
udp 0 0 172.31.32.216:3478 0.0.0.0:* 1098/turnserver
udp 0 0 172.31.32.216:3478 0.0.0.0:*

Here is a summary of netstat

Any wrong config?

I am not too familiar with IPv6 stack, but maybe it is an IP address issue. Your prosody server is listening in all IPv6 interfaces (::), and your JVB and Jicofo are trying to connect to an IPv4 address (127.0.0.1). Could you try to run the following test:

telnet localhost 5222

Then type TEST and hit the Enter key. If everything was good, It should return something like this:

<?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' xmlns='jabber:client'><stream:error><not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error></stream:stream>Connection closed by foreign host.

Ran this command

root@yugapat:/# telnet localhost 5222
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
TEST

<?xml version='1.0'?>Connection closed by foreign host.

This is the output i got

<?xml version='1.0'?>Connection closed by foreign host.

“”"<?xml version='1.0'?><stream:stream xmlns=‘jabber:client’ xmlns:stream=‘http://etherx.jabber.org/streams’ xml:lang=‘en’>stream:error</stream:error></stream:stream>Connection closed by foreign host.
“”"""

It seems that there’s no problem with your prosody server. It’s not an IP issue too. I guess that it may be related to the JVB and Jicofo connection.

I see from the logs that you JVB is using the MUC mode. This requires a prosody account for JVB instead of a component. Could you share your configuration details? Is it your firtst install? Are you upgrading? Are you using a self-signed certificate? What is the content of the /etc/jitsi/videobridge/config and /etc/jitsi/videobridge/sip-communicator.properties files?