Jibri connecting but non recording

I installed Jitsi meet on a XEN DomU virtual server, behind a NAT and it seems to work properly.
I installed an instance of JiBri on another Xen DomU virtual Server on the same XEN host.
It’s based on an Ubuntu 18.04 server installation

Jitsi activates correctly the recording button.
When I chick the button the message “Recording -preparinfg to record the meeting” appears and stays on for nearly 90 seconds then an error message “Recording failed to start” appears and the voice message “Recording not started” is played.
Going to the process, I see the Chrome conversation starting (I have a browser0.log file in the logs and a directory with a json is created in teh recordings directory) but the recording doesn’t start (empry ffmpeg0.txt file in the log directorry and no recording file in the recordings directory).

These are mu configuration files:
Jitsi server:
/etc/prosody/conf.d/jitsi.fermimn.edu.it.cfg.lua:

– Plugins path gets uncommented during jitsi-meet-tokens package install - that’s where token plugin is located
–plugin_paths = { “/usr/share/jitsi-meet/prosody-plugins/” }

VirtualHost “jitsi.fermimn.edu.it”
– enabled = false – Remove this line to enable this host
authentication = “anonymous”
– Properties below are modified by jitsi-meet-tokens package config
– and authentication above is switched to “token”
–app_id=“example_app_id”
–app_secret=“example_app_secret”
– Assign this host a certificate for TLS, otherwise it would use the one
– set in the global section (if any).
– Note that old-style SSL on port 5223 only supports one certificate, and will always
– use the global one.
ssl = {
key = “/etc/prosody/certs/jitsi.fermimn.edu.it.key”;
certificate = “/etc/prosody/certs/jitsi.fermimn.edu.it.crt”;
}
– we need bosh
modules_enabled = {
“bosh”;
“pubsub”;
“ping”; – Enable mod_ping
}

    c2s_require_encryption = false

Component “conference.jitsi.fermimn.edu.it” “muc”
storage = “memory”
–modules_enabled = { “token_verification” }
admins = { “focus@auth.jitsi.fermimn.edu.it” }

Component “jitsi-videobridge.jitsi.fermimn.edu.it”
component_secret = “83qIxVUJ”

VirtualHost “auth.jitsi.fermimn.edu.it”
ssl = {
key = “/etc/prosody/certs/auth.jitsi.fermimn.edu.it.key”;
certificate = “/etc/prosody/certs/auth.jitsi.fermimn.edu.it.crt”;
}
authentication = “internal_plain”

Component “focus.jitsi.fermimn.edu.it”
component_secret = “aat@iF3Z”

– jibri
Component “internal.auth.jitsi.fermimn.edu.it” “muc”
modules_enabled = {
“ping”;
}
– storage = “null”
storage = “memory”
muc_room_cache_size = 1000

VirtualHost “recorder.jitsi.fermimn.edu.it”
modules_enabled = {
“ping”;
}
authentication = “internal_plain”

/etc/jitsi/jicofo/sip-communicator.properties:

org.jitsi.jicofo.jibri.BREWERY=JibriBrewery@internal.auth.jitsi.fermimn.edu.it
org.jitsi.jicofo.jibri.PENDING_TIMEOUT=90

/etc/jitsi/meet/jitsi.fermimn.edu.it-config.js:

/* eslint-disable no-unused-vars, no-var */

var config = {
// Connection
//

hosts: {
    domain: 'jitsi.fermimn.edu.it',

    muc: 'conference.jitsi.fermimn.edu.it'
},

bosh: '//jitsi.fermimn.edu.it/http-bind',

testing: {
    enableFirefoxSimulcast: false,

    p2pTestMode: false
},


desktopSharingChromeExtId: null,

desktopSharingChromeSources: [ 'screen', 'window', 'tab' ],

desktopSharingChromeMinExtVersion: '0.1',

fileRecordingsEnabled: true,

liveStreamingEnabled: true,

hiddenDomain: 'recorder.jitsi.fermimn.edu.it',

channelLastN: -1,


enableWelcomePage: true,

enableUserRolesBasedOnToken: false,


p2p: {
    enabled: true,
    stunServers: [
        { urls: 'stun:stun.l.google.com:19302' },
        { urls: 'stun:stun1.l.google.com:19302' },
        { urls: 'stun:stun2.l.google.com:19302' }
    ],

    preferH264: true

},

analytics: {
    // The Google Analytics Tracking ID:
    // googleAnalyticsTrackingId: 'your-tracking-id-UA-123456-1'

    // The Amplitude APP Key:
    // amplitudeAPPKey: '<APP_KEY>'

    // Array of script URLs to load as lib-jitsi-meet "analytics handlers".
    // scriptURLs: [
    //      "libs/analytics-ga.min.js", // google-analytics
    //      "https://example.com/my-custom-analytics.js"
    // ],
},

deploymentInfo: {
    // shard: "shard1",
    // region: "europe",
    // userRegion: "asia"
}

};

/* eslint-enable no-unused-vars, no-var */

/etc/jitsi/videobridge/sip-communicator.properties:

org.jitsi.videobridge.AUTHORIZED_SOURCE_REGEXP=focus@auth.jitsi.fermimn.edu.it/.*
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=10.0.50.220
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=77.240.236.201

JiBri server:

/etc/jitsi/jibri/config.json:

{
// Where recording files should be temporarily stored
“recording_directory”:"/srv/recordings",
// The path to the script which will be run on completed recordings
// “finalize_recording_script_path”: “/path/to/finalize_recording.sh”,
“finalize_recording_script_path”: “/usr/local/bin/endrecording.sh”,
“xmpp_environments”: [
{
// A friendly name for this environment which can be used
// for logging, stats, etc.
“name”: “prod environment”,
// The hosts of the XMPP servers to connect to as part of
// this environment
“xmpp_server_hosts”: [
“jitsi.fermimn.edu.it”
],
// The xmpp domain we’ll connect to on the XMPP server
“xmpp_domain”: “jitsi.fermimn.edu.it”,
// Jibri will login to the xmpp server as a privileged user
“control_login”: {
// The domain to use for logging in
“domain”: “auth.jitsi.fermimn.edu.it”,
// The credentials for logging in
“username”: “jibri”,
“password”: “jibriauthpass”
},
// Using the control_login information above, Jibri will join
// a control muc as a means of announcing its availability
// to provide services for a given environment
“control_muc”: {
“domain”: “internal.auth.jitsi.fermimn.edu.it”,
“room_name”: “JibriBrewery”,
“nickname”: “jibri1-nickname”
},
// All participants in a call join a muc so they can exchange
// information. Jibri can be instructed to join a special muc
// with credentials to give it special abilities (e.g. not being
// displayed to other users like a normal participant)
“call_login”: {
“domain”: “recorder.jitsi.fermimn.edu.it”,
“username”: “recorder”,
“password”: “jibrirecorderpass”
},
// When jibri gets a request to start a service for a room, the room
// jid will look like:
// roomName@optional.prefixes.subdomain.xmpp_domain
// We’ll build the url for the call by transforming that into:
// https://xmpp_domain/subdomain/roomName
// So if there are any prefixes in the jid (like jitsi meet, which
// has its participants join a muc at conference.xmpp_domain) then
// list that prefix here so it can be stripped out to generate
// the call url correctly
“room_jid_domain_string_to_strip_from_start”: “conference.”,
// The amount of time, in minutes, a service is allowed to continue.
// Once a service has been running for this long, it will be
// stopped (cleanly). A value of 0 means an indefinite amount
// of time is allowed
“usage_timeout”: “0”
}
]
}
In the next message I’ll add some log file

Next the log files:

Server JiBri

/var/log/jitsi/jibri/log0.txt
Always starts with a warning and a series of Java Exceptions:

2020-03-09 06:04:10.833 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.internal.InternalHttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.internal.InternalHttpApi will be ignored.
2020-03-09 06:04:11.269 WARNING: [1] org.glassfish.jersey.internal.Errors.logErrors() The following warnings have been detected: WARNING: HK2 service reification failed for [org.glassfish.jersey.message.internal.DataSourceProvider] with an exception:
MultiException stack 1 of 2
java.lang.NoClassDefFoundError: javax/activation/DataSource
Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource
MultiException stack 2 of 2
java.lang.IllegalArgumentException: Errors were discovered while reifying SystemDescriptor(
implementation=org.glassfish.jersey.message.internal.DataSourceProvider
contracts={javax.ws.rs.ext.MessageBodyReader,javax.ws.rs.ext.MessageBodyWriter}
scope=javax.inject.Singleton
qualifiers={}
descriptorType=CLASS
descriptorVisibility=NORMAL
metadata=
rank=0
loader=null
proxiable=null
proxyForSameScope=null
analysisName=null
id=106
locatorId=0
identityHashCode=62915435
reified=false)
WARNING: HK2 service reification failed for [org.glassfish.jersey.message.internal.DataSourceProvider] with an exception:
MultiException stack 1 of 2
java.lang.NoClassDefFoundError: javax/activation/DataSource
Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource

and so on.

The relevant part with the recording:

2020-03-09 06:04:13.129 INFO: [21] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=jitsi.fermimn.edu.it hostname=jitsi.fermimn.edu.it] connected
2020-03-09 06:04:13.572 INFO: [21] org.jitsi.xmpp.mucclient.MucClient.log() Joined MUC: jibribrewery@internal.auth.jitsi.fermimn.edu.it
2020-03-09 06:04:17.134 INFO: [35] org.jitsi.jibri.api.xmpp.XmppApi.handleJibriIq() Received JibriIq from environment [MucClient id=jitsi.fermimn.edu.it hostname=jitsi.fermimn.edu.it]
2020-03-09 06:04:17.138 INFO: [35] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Received start request
2020-03-09 06:04:17.155 INFO: [35] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Sending ‘pending’ response to start IQ
2020-03-09 06:04:17.159 INFO: [36] org.jitsi.jibri.api.xmpp.XmppApi.run() Starting service
2020-03-09 06:04:17.434 INFO: [36] org.jitsi.jibri.api.xmpp.XmppApi.handleStartService() Parsed call url info: CallUrlInfo(baseUrl=https://jitsi.fermimn.edu.it, callName=test, urlParams=)
2020-03-09 06:04:17.441 INFO: [36] org.jitsi.jibri.JibriManager.startFileRecording() Starting a file recording with params: FileRecordingRequestParams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=https://jitsi.fermimn.edu.it, callName=test, urlParams=)), sessionId=silkmrnnhqqvruva, callLoginParams=XmppCredentials(domain=recorder.jitsi.fermimn.edu.it, username=recorder, password=jibrirecorderpass)) finalize script path: /usr/local/bin/endrecording.sh and recordings directory: /srv/recordings
2020-03-09 06:04:28.941 INFO: [36] org.openqa.selenium.remote.ProtocolHandshake.createSession() Detected dialect: OSS
2020-03-09 06:04:29.053 INFO: [36] org.jitsi.jibri.selenium.JibriSelenium.() Starting empty call check with a timeout of PT30S
2020-03-09 06:04:29.159 FINE: [36] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.() Detected os as OS: LINUX
2020-03-09 06:04:29.206 INFO: [36] org.jitsi.jibri.service.impl.FileRecordingJibriService.() Writing recording to /srv/recordings/silkmrnnhqqvruva
2020-03-09 06:04:29.213 FINE: [36] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: start:recording
2020-03-09 06:04:29.217 INFO: [36] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: IDLE -> BUSY
2020-03-09 06:04:29.218 INFO: [36] org.jitsi.jibri.api.xmpp.XmppApi.updatePresence() Jibri reports its status is now JibriStatus(busyStatus=BUSY, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2020-03-09 06:04:29.221 INFO: [36] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@6210ae0
2020-03-09 06:04:33.600 FINE: [45] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Visiting url https://jitsi.fermimn.edu.it/test#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME=“Jibri”&config.analytics.disabled=true&config.p2p.enabled=false
2020-03-09 06:05:05.482 SEVERE: [45] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Timed out waiting for call page to load
2020-03-09 06:05:05.507 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Starting up to Error: SESSION Failed to join call
2020-03-09 06:05:05.510 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Starting up to Error: SESSION Failed to join call
2020-03-09 06:05:05.511 INFO: [45] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service had an error, sending error iq
2020-03-09 06:05:05.516 FINE: [45] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:recording
2020-03-09 06:05:05.519 INFO: [45] org.jitsi.jibri.JibriManager.stopService() Stopping the current service
2020-03-09 06:05:05.521 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Stopping capturer
2020-03-09 06:05:05.522 INFO: [45] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process
2020-03-09 06:05:05.524 INFO: [45] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value null
2020-03-09 06:05:05.524 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Quitting selenium
2020-03-09 06:05:05.550 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Participants in this recording:
2020-03-09 06:05:05.877 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 9 log entries for type browser
2020-03-09 06:05:06.200 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 968 log entries for type driver
2020-03-09 06:05:06.819 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 0 log entries for type client
2020-03-09 06:05:06.820 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Leaving web call
2020-03-09 06:05:06.878 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Quitting chrome driver
2020-03-09 06:05:07.011 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Chrome driver quit
2020-03-09 06:05:07.011 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Finalizing the recording
2020-03-09 06:05:17.035 SEVERE: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.finalize() Timed out waiting for process logger task to complete
2020-03-09 06:05:17.041 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.finalize() Recording finalize script finished with exit value 0
2020-03-09 06:05:17.042 INFO: [45] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: BUSY -> IDLE
2020-03-09 06:05:17.043 INFO: [45] org.jitsi.jibri.api.xmpp.XmppApi.updatePresence() Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2020-03-09 06:05:17.043 INFO: [45] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@43bccd2a

More logs on the next message.

The browser log is too long to paste here.

Jitsi server

/var/log/prosody/prosody.log:

Mar 09 06:03:52 c2s556ff7eb8940 info Client connected
Mar 09 06:03:53 c2s556ff7eb8940 info Client disconnected: closed
Mar 09 06:04:12 c2s556ff7ef50e0 info Client connected
Mar 09 06:04:13 c2s556ff7ef50e0 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Mar 09 06:04:13 c2s556ff7ef50e0 info Authenticated as jibri@auth.jitsi.fermimn.edu.it
Mar 09 06:04:35 mod_bosh info New BOSH session, assigned it sid ‘b56ce47a-c9aa-40c2-96fc-3ac68adc731c’
Mar 09 06:07:01 bosh8696cfe9-014d-4527-9fc4-94fab0922746 info BOSH client disconnected: session close

And the prosody err (/var/log/prosody/prosody.err - not relevant: too early):
Mar 09 05:58:21 portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Mar 09 05:58:21 portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281

/var/log/jitsi/jicofo.log)

Jicofo 2020-03-09 07:04:13.600 INFO: [30] org.jitsi.jicofo.xmpp.BaseBrewery.processInstanceStatusChanged().318 Added brewery instance: jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname
Jicofo 2020-03-09 07:04:13.602 INFO: [30] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibri jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname status
Jicofo 2020-03-09 07:04:13.606 INFO: [30] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname available: true
Jicofo 2020-03-09 07:04:17.084 INFO: [109] org.jitsi.jicofo.recording.jibri.JibriSession.log() Starting Jibri jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname for stream ID: null in room: test@conference.jitsi.fermimn.edu.it
Jicofo 2020-03-09 07:04:17.168 INFO: [109] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibri jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname has status pending and failure reason null, current Jibri jid is jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname
Jicofo 2020-03-09 07:04:17.169 INFO: [109] org.jitsi.jicofo.recording.jibri.JibriSession.log() Starting session with Jibri jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname
Jicofo 2020-03-09 07:04:17.170 INFO: [109] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Started Jibri session
Jicofo 2020-03-09 07:04:29.229 INFO: [30] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibri jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname status
Jicofo 2020-03-09 07:04:29.231 INFO: [30] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname available: false
Jicofo 2020-03-09 07:05:05.519 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Updating status from JIBRI: for test@conference.jitsi.fermimn.edu.it
Jicofo 2020-03-09 07:05:05.519 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibri jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname has status off and failure reason error, current Jibri jid is jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname
Jicofo 2020-03-09 07:05:05.520 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri is no longer pending, cancelling pending timeout task
Jicofo 2020-03-09 07:05:05.520 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri failed, trying to fall back to another Jibri
Jicofo 2020-03-09 07:05:05.522 SEVERE: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Unable to find an available Jibri, can’t start
Jicofo 2020-03-09 07:05:05.522 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Failed to fall back to another Jibri, this session has now failed
Jicofo 2020-03-09 07:05:05.523 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Got jibri status off and failure error
Jicofo 2020-03-09 07:05:05.525 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Publishing new jibri-recording-status: in: test@conference.jitsi.fermimn.edu.it
Jicofo 2020-03-09 07:05:05.525 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Cleaning up current JibriSession
Jicofo 2020-03-09 07:05:17.051 INFO: [30] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibri jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname status
Jicofo 2020-03-09 07:05:17.053 INFO: [30] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri1-nickname available: true
Jicofo 2020-03-09 07:07:01.668 INFO: [30] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberLeft sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@471df12e member=ChatMember[test@conference.jitsi.fermimn.edu.it/e6d34c72, jid: me_4k99f2g3uwff1@jitsi.fermimn.edu.it/ltyMtOhD]@1668372989]

/var/log/jitsi/jvb.log:

JVB 2020-03-09 07:05:00.131 FINE: [112] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-156):
JVB 2020-03-09 07:05:02.931 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=9a8da78b2a394bee conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:05:02.985 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 54ms. Sticky failure: false
JVB 2020-03-09 07:05:09.816 FINE: [135] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-400):
JVB 2020-03-09 07:05:09.817 FINE: [135] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-400).
JVB 2020-03-09 07:05:09.820 FINE: [135] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-400) with:
JVB 2020-03-09 07:05:10.132 FINE: [137] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-160):
JVB 2020-03-09 07:05:12.987 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=2ba9e85782fc81b3 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:05:13.034 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 48ms. Sticky failure: false
JVB 2020-03-09 07:05:19.816 FINE: [139] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-405):
JVB 2020-03-09 07:05:19.817 FINE: [139] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-405).
JVB 2020-03-09 07:05:19.819 FINE: [139] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-405) with:
JVB 2020-03-09 07:05:20.131 FINE: [162] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-164):
JVB 2020-03-09 07:05:23.035 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=c4ffb7f6946c50f8 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:05:23.082 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 48ms. Sticky failure: false
JVB 2020-03-09 07:05:26.656 INFO: [19] org.jitsi.videobridge.VideobridgeExpireThread.log() Running expire()
JVB 2020-03-09 07:05:29.746 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-419):
JVB 2020-03-09 07:05:29.746 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-419).
JVB 2020-03-09 07:05:29.747 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-419) with:
JVB 2020-03-09 07:05:29.815 FINE: [187] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-421):
JVB 2020-03-09 07:05:29.816 FINE: [187] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-421).
JVB 2020-03-09 07:05:29.819 FINE: [187] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-421) with:
JVB 2020-03-09 07:05:30.132 FINE: [189] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-168):
JVB 2020-03-09 07:05:33.082 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=15ec370cdd2b770 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:05:33.095 WARNING: [16] org.jitsi.videobridge.EndpointMessageTransport.log() SCTP connection with 3d659bf53d0b685 not ready yet.
JVB 2020-03-09 07:05:33.095 WARNING: [16] org.jitsi.videobridge.EndpointMessageTransport.log() No available transport channel, can’t send a message
JVB 2020-03-09 07:05:33.139 WARNING: [927] org.ice4j.ice.Agent.log() Agent contains no IceMediaStream with name stream!
JVB 2020-03-09 07:05:33.141 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 59ms. Sticky failure: false
JVB 2020-03-09 07:05:33.142 WARNING: [991] org.ice4j.ice.Agent.log() Agent contains no IceMediaStream with name stream!
JVB 2020-03-09 07:05:39.816 FINE: [191] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-425):
JVB 2020-03-09 07:05:39.816 FINE: [191] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-425).
JVB 2020-03-09 07:05:39.820 FINE: [191] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-425) with:
JVB 2020-03-09 07:05:40.132 FINE: [214] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-172):
JVB 2020-03-09 07:05:43.142 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=baa036bb82114ba0 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:05:43.192 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 50ms. Sticky failure: false
JVB 2020-03-09 07:05:49.816 FINE: [216] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-429):
JVB 2020-03-09 07:05:49.816 FINE: [216] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-429).
JVB 2020-03-09 07:05:49.820 FINE: [216] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-429) with:
JVB 2020-03-09 07:05:50.132 FINE: [239] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-176):
JVB 2020-03-09 07:05:53.193 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=9d44003db956c75a conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:05:53.240 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 47ms. Sticky failure: false
JVB 2020-03-09 07:05:59.746 FINE: [241] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-443):
JVB 2020-03-09 07:05:59.747 FINE: [241] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-443).
JVB 2020-03-09 07:05:59.747 FINE: [241] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-443) with:
JVB 2020-03-09 07:05:59.816 FINE: [64] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-445):
JVB 2020-03-09 07:05:59.816 FINE: [64] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-445).
JVB 2020-03-09 07:05:59.819 FINE: [64] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-445) with:
JVB 2020-03-09 07:06:00.132 FINE: [85] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-180):
JVB 2020-03-09 07:06:03.241 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=b5c389a2f36efed3 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:06:03.289 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 48ms. Sticky failure: false
JVB 2020-03-09 07:06:09.816 FINE: [108] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-449):
JVB 2020-03-09 07:06:09.816 FINE: [108] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-449).
JVB 2020-03-09 07:06:09.820 FINE: [108] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-449) with:
JVB 2020-03-09 07:06:10.132 FINE: [110] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-184):
JVB 2020-03-09 07:06:13.291 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=6ea2b1e080b41fa5 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:06:13.339 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 48ms. Sticky failure: false
JVB 2020-03-09 07:06:19.816 FINE: [112] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-453):
JVB 2020-03-09 07:06:19.816 FINE: [112] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-453).
JVB 2020-03-09 07:06:19.819 FINE: [112] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-453) with:
JVB 2020-03-09 07:06:20.133 FINE: [135] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-188):
JVB 2020-03-09 07:06:23.341 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=778914883ff0541e conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:06:23.396 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 56ms. Sticky failure: false
JVB 2020-03-09 07:06:26.657 INFO: [19] org.jitsi.videobridge.VideobridgeExpireThread.log() Running expire()
JVB 2020-03-09 07:06:29.748 FINE: [137] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-467):
JVB 2020-03-09 07:06:29.749 FINE: [137] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-467).
JVB 2020-03-09 07:06:29.749 FINE: [137] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-467) with:
JVB 2020-03-09 07:06:29.816 FINE: [139] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-469):
JVB 2020-03-09 07:06:29.816 FINE: [139] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-469).
JVB 2020-03-09 07:06:29.820 FINE: [139] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-469) with:
JVB 2020-03-09 07:06:30.132 FINE: [162] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-192):
JVB 2020-03-09 07:06:33.398 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=a8faea5216e326f9 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:06:33.445 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 48ms. Sticky failure: false
JVB 2020-03-09 07:06:39.816 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-473):
JVB 2020-03-09 07:06:39.816 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-473).
JVB 2020-03-09 07:06:39.819 FINE: [164] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-473) with:
JVB 2020-03-09 07:06:40.133 FINE: [187] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-196):
JVB 2020-03-09 07:06:43.446 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=7ae20ee0c5de430d conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:06:43.492 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 46ms. Sticky failure: false
JVB 2020-03-09 07:06:49.816 FINE: [189] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-477):
JVB 2020-03-09 07:06:49.816 FINE: [189] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-477).
JVB 2020-03-09 07:06:49.820 FINE: [189] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-477) with:
JVB 2020-03-09 07:06:50.133 FINE: [191] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-200):
JVB 2020-03-09 07:06:53.493 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=a73cf7da85496b9d conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:06:53.545 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 52ms. Sticky failure: false
JVB 2020-03-09 07:06:59.747 FINE: [214] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-491):
JVB 2020-03-09 07:06:59.747 FINE: [214] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-491).
JVB 2020-03-09 07:06:59.748 FINE: [214] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-491) with:
JVB 2020-03-09 07:06:59.816 FINE: [216] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-493):
JVB 2020-03-09 07:06:59.817 FINE: [216] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-493).
JVB 2020-03-09 07:06:59.821 FINE: [216] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-493) with:
JVB 2020-03-09 07:07:00.133 FINE: [239] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-204):
JVB 2020-03-09 07:07:03.547 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=3b3aa92e8a15c89d conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:07:03.603 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 57ms. Sticky failure: false
JVB 2020-03-09 07:07:09.816 FINE: [241] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-502):
JVB 2020-03-09 07:07:09.816 FINE: [241] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-502).
JVB 2020-03-09 07:07:09.819 FINE: [241] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-502) with:
JVB 2020-03-09 07:07:10.134 FINE: [64] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-208):
JVB 2020-03-09 07:07:13.605 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=9907f29d547ce347 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:07:13.650 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 45ms. Sticky failure: false
JVB 2020-03-09 07:07:19.816 FINE: [85] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-506):
JVB 2020-03-09 07:07:19.816 FINE: [85] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-506).
JVB 2020-03-09 07:07:19.820 FINE: [85] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-506) with:
JVB 2020-03-09 07:07:20.133 FINE: [108] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 0trO1-212):
JVB 2020-03-09 07:07:23.651 INFO: [20] org.jitsi.videobridge.Videobridge.log() CAT=stat create_conf,conf_id=c0db828cdf17eee6 conf_name=null,logging=false,conf_count=1,ch_count=0,v_streams=0
JVB 2020-03-09 07:07:23.699 INFO: [20] org.jitsi.videobridge.health.Health.log() Performed a successful health check in 49ms. Sticky failure: false
JVB 2020-03-09 07:07:26.658 INFO: [19] org.jitsi.videobridge.VideobridgeExpireThread.log() Running expire()
JVB 2020-03-09 07:07:29.749 FINE: [110] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Processing IQ (packetId 4Cxvb-520):
JVB 2020-03-09 07:07:29.749 FINE: [110] org.jitsi.videobridge.xmpp.ComponentImpl.processIQRequest() (serving component ‘JitsiVideobridge’) Processing IQ request (packetId 4Cxvb-520).
JVB 2020-03-09 07:07:29.750 FINE: [110] org.jitsi.videobridge.xmpp.ComponentImpl.processIQ() (serving component ‘JitsiVideobridge’) Responding to IQ (packetId 4Cxvb-520) with:

I don’t know what could bi the issue.
Any help would be appreciated
Thank you
Stefano Salvi

This is the problem, that it takes 30 seconds and jibri’s chrome cannot load the url.
You are using java8, right? What are the resources for the jibri machine, like RAM?

insalled openjdk-8 and removed openjdk-11 in Ubuntu 18.04, but the recording still doesn’ start.
The Jitsi and JiBri servers are both behind a firewall. Tomorrow I’ll try to publish it out of the NAT and analize the logs again (now I know better what to seek for) and if nothing happens, I’ll call again
Thank you

Hi

Are you able to fix this ?

I am seeing almost same problem.

Thanks in advance

On your Jibri server,
Is it able to DNS resolve jitsi.fermimn.edu.it ?
Another thing, Jibri joins like a user, but behind firewall would require NAT setting

On your Jitsi server,
If installation is on a machine behind NAT further configuration of jitsi-videobridge is needed in order for it to be accessible. Provided that all required ports are routed (forwarded) to the machine that it runs on. By default these ports are (TCP/443 or TCP/4443 and UDP 10000). The following extra lines need to be added the file /etc/jitsi/videobridge/sip-communicator.properties:

org.jitsi.videobridge.TCP_HARVESTER_PORT=4443
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=<Local.IP.Address>
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=<Public.IP.Address>

After restart videobridge,
netstat check if listen on port 4443
Normally you’ll need to restart jicofo as well

I modified the setup, getting rid of the NAT.
I found that the videobridge did’t work properly and decided for the rough solution
Now both Jitsi and jibiri servers are on the public net and talk without problem.
Jitsti has a dns entry, reachable.
I installed Java8 instead of java11 (the default) on Jibri machine.
The call to load the page “https://jitsi…it/testsalvi#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME=“Jibri”&config.analytics.disabled=true&config.p2p.enabled=false” still fails after 30 seconds.
If I try to wget the same URL it loads immediately and the content is a long HTML page with a lot of javascript.
The machine (a Xen Domu) has allocated 2 cores and 8GiB RAM.
I can’t find any entry in Jicofo log or prosody log at the time of the request.

Any suggestion?

I made some other investigation. Last was to trace the HTTPS dialog between the machines.
Jibri gets without problem (using the GET method) all’ the HTML, the CSS, the javascript, the images and the sounds.
At the end I can read the two last requests, that use the POST method:
POST /http-bind?room=testsalvi HTTP/1.1
With the post data:
which receives the response:
HTTP/1.1 200 OK
Server: nginx/1.14.2
Date: Wed, 11 Mar 2020 18:37:32 GMT
Content-Type: text/xml; charset=utf-8
Content-Length: 491
Connection: keep-alive
Strict-Transport-Security: max-age=31536000

Next the last:
POST /http-bind?room=testsalvi HTTP/1.1
With the post data:
which receives no reply at all.
Can this be useful?
Have you any idea about what’s the problem or wrong configuration?
Can I search anything more in the logs to solve the problem?
I’m getting mad!
Thank you

I think I solved the problem.
I found that the problem was that the nickname couldn’t be registered. I found this entry in Jicofo log:
Jicofo 2020-03-11 19:37:30.082 INFO: [123] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery@internal.auth.jitsi.fermimn.edu.it/jibri2-nickname available: false
Looking for such a message I found a post that suggested this was a prosody problem.
It was suggested:
– update /etc/prosody/config.lua (NOT /etc/prosody/conf.d/yourdomainname.cfg.lua ),
– add “consider_bosh_secure = true” after the original “c2s_require_encryption = false”
(if set true, change to false )
– stop jibri, stop jvb, stop jicofo, restart prosody, start jicofo, start jvb, start jibri
In my system (debian Buster) the config file was /etc/prosody/prosody.cfg.lua.
J made the changed, restarted the system and … volia … the recording bgun to run…

1 Like

Ugh, it’s so close. Your problems are the closest to what I’m seeing. I did all of those things and I still can’t start a recording. Jibri is connected but I keep getting these java errors:

WARNING: HK2 service reification failed for [org.glassfish.jersey.message.internal.DataSourceProvider] with an exception:
MultiException stack 1 of 2
java.lang.NoClassDefFoundError: javax/activation/DataSource

I just join a room, start recording and immediately get “Recording Failed to start”.

This is because you are running jibri with java11, switch to java8.

Yes, figured that out last night and correct the java version. Regardless. Still can’t get a recording working even once.

Troubleshooting Jibri seems impossible. It would be great to have some details on how to do this. I think I’ve given up at this point. :frowning:

I have just finished a working jitsi/jibri installation without NAT on 2 Debian 10 (buster) vm’s. I did this for documentation purposes, so all my steps are now available in this forum (How-to to setup integrated Jitsi and Jibri for dummies, my comprehensive tutorial for the beginner)

I had to apply some amendments to existing readme-documentation, or some additional steps (like configuring the infamous storage = 'memory' for prosody or opening port 5222 on jitsi-server). Maybe go over the steps to find some missing steps on your end?

Hope it helps! Cheers, Igor

This is great. I haven’t even read it and I can tell you’ve put in a great deal of time to document things. Thank you for that.

Also, I’m running two Vmware ESXi VMs of Ubuntu 18.04 on a local network (for my setup). I’ll go over your stuff and see if I can make some progress on my end.

Alright… I went through that. Very well done, thanks.

I don’t get a recording started, however, but I think many of the details you added helped get me closer. The mix of “recording” and “recorder” hostnames… and just the hostnames in general. Do all these hostnames need DNS entries or are some of them internal? No matter. That seems to be a clear challenge.

But, right now, my main challenge is getting past these errors:

Apr 16 21:57:45 recorder.mydomain.com:tls error Error creating context for c2s: No key present in SSL/TLS configuration for recorder.mydomain.com
Apr 16 21:57:45 recorder.mydomain.com:tls error Error creating contexts for s2sin: No key present in SSL/TLS configuration for recorder.mydomain.com
Apr 16 21:57:45 modulemanager error Unable to load module ‘storage_memory’: /usr/lib/prosody/modules/mod_storage_memory.lua: No such file or directory
Apr 16 21:57:45 storagemanager error Failed to load storage driver plugin memory on internal.auth.mydomain.com: /usr/lib/prosody/modules/mod_storage_memory.lua: No such file or directory
Apr 16 21:57:45 modulemanager error Unable to load module ‘storage_memory’: /usr/lib/prosody/modules/mod_storage_memory.lua: No such file or directory
Apr 16 21:57:45 storagemanager error Failed to load storage driver plugin memory on internal.auth.meet.mydomain.com: /usr/lib/prosody/modules/mod_storage_memory.lua: No such file or directory

Some of that seems to related to the storage = “memory”… but… hmm

A little closer.

These errors are gone:
recorder.mydomain.com:tls error Error creating context for c2s: No key present in SSL/TLS configuration for recorder.mydomain.com

They related to a reference in:
nano /etc/prosody/prosody.cfg.lua

I changed recorder.meet.mydomain.com to fall in line with everything else. Seems to get rid of those errors.

Testing the recording… still fails. :frowning:

---- more ----

Right, so the memory_ storage error… I’ve been on that one.

I changed directory to prosody’s modules folder: cd /usr/lib/prosody/modules/
Then download the memory module: wget https://hg.prosody.im/prosody-modules/raw-file/tip/mod_storage_memory/mod_storage_memory.lua

Then cat the mod_storage_memory.lua to made sure it’s code and not html or some other mangled crap: cat mod_storage_memory.lua

Restart prosody - service prosody restart - check the status service prosody status and no errors.

However, recording still fails. It fails immediately too. Not like the server’s doing anything to check, it just immediately shows the red banner of death.

Sorry to hear the struggle!.. :smirk:

I’d advise:
Step 1: Stop all 3 services prosody, jitsi-videobridge2 and jicofo (or single service on jibri),
Step 2: Remove ALL files from the log-directories /var/log/prosody and /var/log/jitsi AND /var/log/jitsi/jibri
Step 3: Restart the services in order: prosody, jitsi-videobridge2 and jicofo and then also jibri
Wait approx. 1 minute and then Stop all services again.

Now, the logfiles are not very large and no longer filling up, which makes a first analysis more comfortable. I tend to remove all lines with INFO messages to narrow it even further down.

I’m quite sure ‘it will be in there’ as they say… :wink:

Oh, PS: That thingy ‘memory_ storage’: be sure that ALL ocurrences in the file are set to “memory”!

2 Likes

Yep… first thing I’ve done right now - Reboot both servers. Then check to see what services need to start.

---- There we go.
Started Jibri because everything else was started and recording works. Steaming works. The audio is super out of sync with the video, but I’ll take it :slight_smile:

It’s called ‘tenacity’… :grinning:

1 Like