Recording Stopped (Recording failed to start)

What does dpkg -l | grep jibri shows?

ii   jibri                   8.0-18-g88af8a1-1            all      Jibri

If you clear all logs and restart jibri, you still see this as an error output:

?

I think I was wrong … the new log:

2020-01-08 14:26:23.320 INFO: [1] org.jitsi.jibri.Main.main() Jibri run with args [--config, /etc/jitsi/jibri/config.json]

2020-01-08 14:26:23.326 INFO: [1] org.jitsi.jibri.Main.main() Using config file /etc/jitsi/jibri/config.json

2020-01-08 14:26:23.327 INFO: [1] org.jitsi.jibri.Main.main() Using port 3333 for internal HTTP API

2020-01-08 14:26:23.327 INFO: [1] org.jitsi.jibri.Main.main() Using port 2222 for the HTTP API

2020-01-08 14:26:24.223 INFO: [1] org.jitsi.jibri.Main.loadConfig() Parsed config:

JibriConfig(recordingDirectory=/srv/recordings, singleUseMode=false, enabledStatsD=true, finalizeRecordingScriptPath=/srv/recordings/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[myjitsidomain.com.br], xmppDomain=myjitsidomain.com.br, controlLogin=XmppCredentials(domain=auth.myjitsidomain.com.br, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.myjitsidomain.com.br, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.myjitsidomain.com.br, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])

2020-01-08 14:26:25.052 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-01-08 14:26:25.380 INFO: [1] 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-01-08 14:26:25.383 INFO: [1] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@2c30b71f

2020-01-08 14:26:25.391 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on myjitsidomain.com.br with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[myjitsidomain.com.br], xmppDomain=myjitsidomain.com.br, controlLogin=XmppCredentials(domain=auth.myjitsidomain.com.br, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.myjitsidomain.com.br, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.myjitsidomain.com.br, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)

2020-01-08 14:26:25.393 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted

2020-01-08 14:26:25.428 WARNING: [19] org.jitsi.xmpp.mucclient.MucClient.log() Disabling certificate verification!

2020-01-08 14:26:25.520 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.HttpApi 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.HttpApi will be ignored.

2020-01-08 14:26:26.505 INFO: [19] org.jitsi.xmpp.mucclient.MucClient.log() [MucClient id=myjitsidomain.com.br hostname=myjitsidomain.com.br] connected

2020-01-08 14:26:27.113 INFO: [19] org.jitsi.xmpp.mucclient.MucClient.log() Joined MUC: jibribrewery@internal.auth.myjitsidomain.com.br

2020-01-08 14:27:00.268 INFO: [33] org.jitsi.jibri.api.xmpp.XmppApi.handleJibriIq() Received JibriIq from environment [MucClient id=myjitsidomain.com.br hostname=myjitsidomain.com.br]

2020-01-08 14:27:00.269 INFO: [33] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Received start request

2020-01-08 14:27:00.272 INFO: [33] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Sending ‘pending’ response to start IQ

2020-01-08 14:27:00.273 INFO: [35] org.jitsi.jibri.api.xmpp.XmppApi.run() Starting service

2020-01-08 14:27:00.320 INFO: [35] org.jitsi.jibri.api.xmpp.XmppApi.handleStartService() Parsed call url info: CallUrlInfo(baseUrl=https://myjitsidomain.com.br, callName=mostaliensemancipatelazily, urlParams=)

2020-01-08 14:27:00.321 INFO: [35] org.jitsi.jibri.JibriManager.startFileRecording() Starting a file recording with params: FileRecordingRequestParams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=https://myjitsidomain.com.br, callName=mostaliensemancipatelazily, urlParams=)), sessionId=gampjluyuwtlxbzn, callLoginParams=XmppCredentials(domain=recorder.myjitsidomain.com.br, username=recorder, password=jibrirecorderpass)) finalize script path: /srv/recordings/finalize_recording.sh and recordings directory: /srv/recordings

2020-01-08 14:27:01.676 INFO: [35] org.openqa.selenium.remote.ProtocolHandshake.createSession() Detected dialect: OSS

2020-01-08 14:27:01.699 INFO: [35] org.jitsi.jibri.selenium.JibriSelenium.() Starting empty call check with a timeout of PT30S

2020-01-08 14:27:01.717 FINE: [35] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.() Detected os as OS: LINUX

2020-01-08 14:27:01.725 INFO: [35] org.jitsi.jibri.service.impl.FileRecordingJibriService.() Writing recording to /srv/recordings/gampjluyuwtlxbzn

2020-01-08 14:27:01.728 FINE: [35] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: start:recording

2020-01-08 14:27:01.729 INFO: [35] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: IDLE -> BUSY

2020-01-08 14:27:01.730 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-01-08 14:27:01.730 INFO: [35] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@3a660129

2020-01-08 14:27:04.018 FINE: [44] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Visiting url https://myjitsidomain.com.br/mostaliensemancipatelazily#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-01-08 14:27:07.164 INFO: [44] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Waited 2132 milliseconds for call page to load

2020-01-08 14:27:07.182 INFO: [44] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Starting up to Running

2020-01-08 14:27:07.183 INFO: [44] org.jitsi.jibri.service.impl.FileRecordingJibriService.invoke() Selenium joined the call, starting the capturer

2020-01-08 14:27:07.224 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:bsnoop -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 /srv/recordings/gampjluyuwtlxbzn/mostaliensemancipatelazily_2020-01-08-14-27-01.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:bsnoop, -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, /srv/recordings/gampjluyuwtlxbzn/mostaliensemancipatelazily_2020-01-08-14-27-01.mp4])

2020-01-08 14:27:12.240 FINE: [45] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update

2020-01-08 14:27:12.241 INFO: [48] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegProcessUpdate() Ffmpeg quit abruptly. Last output line: plug:bsnoop: Input/output error

2020-01-08 14:27:12.242 INFO: [48] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Starting up to Error: SESSION Ffmpeg failed to start

2020-01-08 14:27:12.243 INFO: [48] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Starting up to Error: SESSION Ffmpeg failed to start

2020-01-08 14:27:12.244 INFO: [48] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service had an error, sending error iq

2020-01-08 14:27:12.248 FINE: [48] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:recording

2020-01-08 14:27:12.251 INFO: [48] org.jitsi.jibri.JibriManager.stopService() Stopping the current service

2020-01-08 14:27:12.252 INFO: [48] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Stopping capturer

2020-01-08 14:27:12.252 INFO: [48] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process

2020-01-08 14:27:12.257 INFO: [48] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value 1

2020-01-08 14:27:12.257 INFO: [48] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Quitting selenium

2020-01-08 14:27:12.295 INFO: [48] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Participants in this recording:

2020-01-08 14:27:12.430 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 17 log entries for type browser

2020-01-08 14:27:12.575 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 656 log entries for type driver

2020-01-08 14:27:12.809 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 0 log entries for type client

2020-01-08 14:27:12.809 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Leaving web call

2020-01-08 14:27:13.048 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Quitting chrome driver

2020-01-08 14:27:13.127 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Chrome driver quit

2020-01-08 14:27:13.128 INFO: [48] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Finalizing the recording

2020-01-08 14:27:13.142 INFO: [48] org.jitsi.jibri.service.impl.FileRecordingJibriService.finalize() Recording finalize script finished with exit value 0

2020-01-08 14:27:13.143 INFO: [48] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: BUSY -> IDLE

2020-01-08 14:27:13.143 INFO: [48] 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-01-08 14:27:13.144 INFO: [48] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@56c539fa

That is better :slight_smile:
Can you check /home/jibri/.asoundrc, that should be the same as
https://github.com/jitsi/jibri/blob/master/resources/debian-package/etc/jitsi/jibri/asoundrc. If it is not can you fix it and retry?
Thanks for coming back

1 Like

Are the same !

I believe the problem may be in the line below, but I did not find any post reporting the same …

2020-01-08 22:15:39.918 INFO: [1015] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegProcessUpdate() Ffmpeg quit abruptly. Last output line: plug:bsnoop: Input/output error 2020-01-08 22:15:39.919 INFO: [1015] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Starting up to Error: SESSION Ffmpeg failed to start 2020-01-08 22:15:39.919 INFO: [1015] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Starting up to Error: SESSION Ffmpeg failed to start

Any unstable versions for the feature to work?

Thanks !

Hi @damencho

I also tried to look for the error that appears in ffmpeg log and nothing … sorry to insist, but I need to resolve

2020-01-10 18:35:52.650 INFO: [392] ffmpeg.call() ALSA lib pcm_direct.c:1562:(_snd_pcm_direct_get_slave_ipc_offset) Invalid value for card 2020-01-10 18:35:52.650 INFO: [392] ffmpeg.call() [alsa @ 0x11a0f20] cannot open audio device plug:bsnoop (No such device) 2020-01-10 18:35:52.650 INFO: [392] ffmpeg.call() plug:bsnoop: Input/output error

@saghul do you have an idea? @jack-denio has checked and the .asoundrc in /home/jibri should be the one containing bsnoop.

@jack-denio What do aplay -l and arecord -l return? (remember to run as the jibri user)

Hi @saghul ! Thanks for the answer …

aplay:

root@jibri:~# aplay -l
aplay: device_list:268: no soundcards found…

arecord:

root@jibri:~# arecord -l
arecord: device_list:268: no soundcards found…

Not root, use the jibri user. You can become the jibri user as follows: su jibri

root@jibri:~# su jibri aplay -l /usr/bin/aplay: /usr/bin/aplay: cannot execute binary file

root@jibri:~# su jibri arecord -l
/usr/bin/arecord: /usr/bin/arecord: cannot execute binary file

No, first become the jibri user by running su jibri as root. Then in the new prompt run the aplay / arecord commands.

Sorry …

jibri@jibri:/root$ aplay -l aplay: device_list:268: no soundcards found...

jibri@jibri:/root$ arecord -l
arecord: device_list:268: no soundcards found…

Ok, looks like your loopback devices have not been created. Did you follow this section in the instructions? https://github.com/jitsi/jibri#alsa-and-loopback-device

It worked !

We had already checked with “lsmod | grep snd_aloop”, but redoing the process worked!

Thanks !!! @damencho and @saghul !

1 Like

@saghul and @damencho, What do I need to do besides what is on this link to integrate with Dropbox ?

That should be all. If you are getting problems, please open a new dedicated discussion topic.

Ok, thanks !