Unable to run jibri setup successfully

Hi , today we faced these kind of errors in our log after installation of jibri

2021-11-06 11:51:56.900 INFO: [1] org.jitsi.jibri.Main.log() Jibri run with args [–config, /etc/jitsi/jibri/config.json]
2021-11-06 11:51:57.079 INFO: [1] org.jitsi.jibri.Main.log() Checking legacy config file /etc/jitsi/jibri/config.json
2021-11-06 11:51:57.079 INFO: [1] org.jitsi.jibri.Main.log() Legacy config file /etc/jitsi/jibri/config.json doesn’t exist
2021-11-06 11:51:57.445 INFO: [1] org.jitsi.jibri.Main.log() Jibri starting up with id
2021-11-06 11:51:57.900 INFO: [1] org.jitsi.jibri.webhooks.v1.JwtInfo.log() got jwtConfig: {}

2021-11-06 11:51:57.901 INFO: [1] org.jitsi.jibri.webhooks.v1.JwtInfo.log() Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: /etc/jitsi/j$2021-11-06 11:51:58.098 INFO: [1] org.jitsi.jibri.Main.log() Using port 3333 for internal HTTP API
2021-11-06 11:51:58.117 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status
2021-11-06 11:51:58.394 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.log() Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(heal$2021-11-06 11:51:58.407 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.log() Connecting to xmpp environment on domain.name with config XmppEnvironmentConfig(n$2021-11-06 11:51:58.409 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.log() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided cert$2021-11-06 11:51:58.433 INFO: [1] org.jitsi.jibri.Main.log() Using port 2222 for HTTP API
2021-11-06 11:51:58.441 WARNING: [25] org.jitsi.xmpp.mucclient.MucClient.log() Disabling certificate verification!
2021-11-06 11:51:58.675 INFO: [25] org.jitsi.xmpp.mucclient.MucClient.log() Connected.
2021-11-06 11:51:58.676 INFO: [25] org.jitsi.xmpp.mucclient.MucClient.log() Logging in.
2021-11-06 11:51:58.785 INFO: [25] org.jitsi.xmpp.mucclient.MucClient.log() Joined MUC: jibribrewery@internal.auth.domain.name
2021-11-06 11:52:58.093 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status
2021-11-06 11:53:58.093 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status
2021-11-06 11:54:58.093 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status
2021-11-06 11:55:49.610 WARNING: [37] org.jivesoftware.smack.AbstractXMPPConnection.callConnectionClosedOnErrorListener() Connection XMPPTCPConnection[jibri@au$org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc$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)
2021-11-06 11:55:49.639 WARNING: [37] org.jitsi.xmpp.mucclient.MucClient.log() Closed on error:
org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc$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)
2021-11-06 11:55:58.093 FINE: [16] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status

Did anyone face similar errors?

Share your jibri.conf (don’t forget to mask out your domain)

jibri.conf_latest.txt (2.0 KB)

log.0 (1).txt (886 Bytes)

I have attached both log & jibri.conf file here

log file.txt (4.6 KB)

That error is now resolved but still there’s an FFMPEG error.

You have a sound device issue.
Does your kernel support snd_aloop?

No, Currently we are trying to resolve the snd_aloop issue.

what is your kernel?

uname -a

Linux **.co 5.4.0-1058-aws #61~18.04.3-Ubuntu SMP Fri Oct 1 14:04:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

You need the generic kernel on AWS. Search here and on google for how to replace the kernel in your AWS instance.

1 Like