Jibri stop recording after 30s

Hi , my jibri for recording stop after 30s , jibri and jitsi-meet run on the same instance , here the log. Thanks

`2020-03-02 09:57:37.998 INFO: [35] org.openqa.selenium.remote.ProtocolHandshake.createSession() Detected dialect: OSS
2020-03-02 09:57:38.017 INFO: [35] org.jitsi.jibri.selenium.JibriSelenium.<init>() Starting empty call check with a timeout of PT30S
2020-03-02 09:57:38.035 FINE: [35] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.<init>() Detected os as OS: LINUX
2020-03-02 09:57:38.041 INFO: [35] org.jitsi.jibri.service.impl.FileRecordingJibriService.<init>() Writing recording to /var/www/recording/ufltkpywjhknzeix
2020-03-02 09:57:38.042 FINE: [35] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: start:recording
2020-03-02 09:57:38.042 INFO: [35] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: IDLE -> BUSY
2020-03-02 09:57:38.043 INFO: [35] 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-02 09:57:38.043 INFO: [35] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@5c53016c
2020-03-02 09:57:39.041 FINE: [44] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Visiting url https://azure-video-api.burhanyusuf.dev/5e58c1495f91a#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-02 09:57:40.419 INFO: [44] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Waited 1033 milliseconds for call page to load
2020-03-02 09:57:40.432 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Starting up to Running
2020-03-02 09:57:40.433 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.invoke() Selenium joined the call, starting the capturer
2020-03-02 09:57:40.477 INFO: [44] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.launch() Starting ffmpeg with command ffmpeg -y -v info -f x11grab -draw_mouse 0 -r 30 -s 1280x720 -thread_queue_size 4096 -i :0.0+0,0 -f alsa -thread_queue_size 4096 -i plug:cloop -acodec aac -strict -2 -ar 44100 -c:v libx264 -preset veryfast -profile:v main -level 3.1 -pix_fmt yuv420p -r 30 -crf 25 -g 60 -tune zerolatency -f mp4 /var/www/recording/ufltkpywjhknzeix/5e58c1495f91a_2020-03-02-09-57-38.mp4 ([ffmpeg, -y, -v, info, -f, x11grab, -draw_mouse, 0, -r, 30, -s, 1280x720, -thread_queue_size, 4096, -i, :0.0+0,0, -f, alsa, -thread_queue_size, 4096, -i, plug:cloop, -acodec, aac, -strict, -2, -ar, 44100, -c:v, libx264, -preset, veryfast, -profile:v, main, -level, 3.1, -pix_fmt, yuv420p, -r, 30, -crf, 25, -g, 60, -tune, zerolatency, -f, mp4, /var/www/recording/ufltkpywjhknzeix/5e58c1495f91a_2020-03-02-09-57-38.mp4])
2020-03-02 09:57:41.661 INFO: [48] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Starting up to Running
2020-03-02 09:57:41.662 INFO: [48] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Starting up to Running
2020-03-02 09:57:41.662 INFO: [48] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service started up successfully, sending on iq <iq to='jibribrewery@internal.auth.azure-video-api.burhanyusuf.dev/focus' id='9Cx1x-22' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='on'/></iq>
2020-03-02 09:57:55.493 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.run() Jibri client receive bitrates: {audio={download=0, upload=0}, download=0, upload=0, video={download=0, upload=0}}, all clients muted? false
2020-03-02 09:58:10.445 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.run() Jibri client receive bitrates: {audio={download=0, upload=0}, download=0, upload=0, video={download=0, upload=0}}, all clients muted? false
2020-03-02 09:58:10.445 INFO: [45] org.jitsi.jibri.selenium.JibriSelenium.invoke() Recurring call status checks generated event org.jitsi.jibri.selenium.SeleniumEvent$NoMediaReceived@5d572fa6
2020-03-02 09:58:10.446 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Running to Error: SESSION No media received
2020-03-02 09:58:10.446 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Running to Error: SESSION No media received
2020-03-02 09:58:10.447 INFO: [44] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service had an error, sending error iq <iq to='jibribrewery@internal.auth.azure-video-api.burhanyusuf.dev/focus' id='9Cx1x-24' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error'/></iq>
2020-03-02 09:58:10.447 FINE: [44] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:recording
2020-03-02 09:58:10.447 INFO: [44] org.jitsi.jibri.JibriManager.stopService() Stopping the current service
2020-03-02 09:58:10.447 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Stopping capturer
2020-03-02 09:58:10.447 INFO: [44] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process
2020-03-02 09:58:10.865 INFO: [48] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Running to Finished
2020-03-02 09:58:10.865 INFO: [44] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value 255
2020-03-02 09:58:10.865 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Quitting selenium
2020-03-02 09:58:10.877 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Participants in this recording: []
2020-03-02 09:58:10.948 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 15 log entries for type browser
2020-03-02 09:58:11.001 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 650 log entries for type driver
2020-03-02 09:58:11.147 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 0 log entries for type client
2020-03-02 09:58:11.147 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Leaving web call
2020-03-02 09:58:11.278 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Quitting chrome driver
2020-03-02 09:58:11.850 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Chrome driver quit
2020-03-02 09:58:11.851 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Finalizing the recording
2020-03-02 09:58:11.853 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.finalize() Recording finalize script finished with exit value 0
2020-03-02 09:58:11.854 INFO: [44] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: BUSY -> IDLE
2020-03-02 09:58:11.854 INFO: [44] 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-02 09:58:11.854 INFO: [44] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@41689285`

Jibri quit because it wasn’t receiving any media…do you have at least one other participant in the call sending media?

i tested with one participant only, should it at least 2 participant?

Was that participant audio and video muted?

Its working now, just setting up sip communication on videobridge

dear burhan,
we are facing the same problem, how did you solve it. can u please guide us. we are struggling with same… jibri drops the connection after 30seconds… no recording…
is there a way we can reach out to you to show you and help us out… can u help us as paid expert?
awaiting…

Its failed because ICE Server unreachable , you should setup some configuration to use turn server

Can you share your sip config file
Thank you

Hello good afternoon

I encounter the same problem, after 30 seconds 1 minute or 2, jibri loses the connection and stops recording.

These are some of the logs:
2020-05-07 15:33:20.107 INFO: [45] org.jitsi.jibri.JibriManager.invoke() The usage timeout has elapsed, stopping the currently active service
2020-05-07 15:33:20.107 FINE: [45] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:recording
2020-05-07 15:33:20.107 INFO: [45] org.jitsi.jibri.JibriManager.stopService() Stopping the current service
2020-05-07 15:33:20.107 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Stopping capturer
2020-05-07 15:33:20.107 INFO: [45] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process
2020-05-07 15:33:20.503 INFO: [259] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Running to Finished
2020-05-07 15:33:20.503 INFO: [45] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value 255
2020-05-07 15:33:20.504 INFO: [45] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Quitting selenium
2020-05-07 15:33:20.504 INFO: [259] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Running to Finished

Can u check value usage_timeout from your jibri config (json)?

Yes this is the value i have:

         "room_jid_domain_string_to_strip_from_start": "conference.",
         "usage_timeout": "2"

I suggest changing it? What will be indicated?

Thank you.

Try to set 0

Thank you!!! Its Work!

I did not take that value into account. Determine the amount of time the recording can last.

image
PS for me: You have to read the comments, not delete them

Thanks for your attention.

Glad to help u

@Burhan_Yusuf I’m facing the same issue on Jibri (stops recording after a fixed time interval). The exception I get in Jibri logs is:

2020-05-10 17:30:44.110 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.invoke() Recurring call status checks generated event org.jitsi.jibri.selenium.SeleniumEvent$NoMediaReceived@10515e63
2020-05-10 17:30:44.110 INFO: [85] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Running to Error: SESSION No media received
2020-05-10 17:30:44.110 INFO: [85] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Running to Error: SESSION No media received

My EC2 instance is behind a security group (NAT firewall) and I’m seeing the same exception in my JVB logs

2020-05-10 17:52:26.938 SEVERE: [19] AbstractHealthCheckService.run#174: Health check failed in PT0S:
java.lang.Exception: Address discovery through STUN failed

I’m pretty sure that I need to open a port for STUN discovery but I’m not sure which one. Could you please help me understand what is to be done to make ICE server reachable?

My usage_timeout is set to 0 already, and I had one participant in the call with video and audio unmuted.

Try to allow UDP port 3478 from network firewall

@Burhan_Yusuf Currently, fuser -n udp 3478 on my server does not return anything. I think there’s no process on my server that uses this port. Where can I see the port on which a STUN server is running on my server?

Are u installed coturn server? U can check this refference : https://meetrix.io/blog/webrtc/coturn/installation.html

@Burhan_Yusuf coturn server is installed with Jitsi. I resolved this by checking my /etc/turnserver.conf where I saw that the turn server was listening on port 4446. Then I updated my /etc/jitsi/videobridge/sip-communicator.properties with

org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=$HOSTNAME:4446

Then I restarted videobridge with systemctl restart jitsi-videobridge2 and my JVB was able to successfully connect with the STUN server.

For NAT, I had to add an ingress/inbound rule to my security group for allowing UDP traffic on port 4446 (port on which coturn was listening) so that JVB could reach my TURN/STUN server.

After performing these steps, my Jibri was able to record and stream successfully and without stopping.

Glad to hear that ur problem solved