Jibri recording failed from compiled jibri

I’ve setup the repository and compile the Jibri from source https://github.com/jitsi/jibri.git without changing any files and I’ve followed the steps to produce a jibri.jar from https://github.com/jitsi/jibri/blob/master/doc/debian_package.md, and move the jibri-8.0-SNAPSHOT-jar-with-dependencies.jar and rename/replace the jibri.jar in /opt/jitsi/jibri/ then restart the service, but I’m still having a problem in recording with the prompt err message “Recording failed to start”.

I’ve already tried to Ubuntu xenial & bionic 64
and adjust the jdk version from 11 to 8 but the problem still persist.

Any hints/suggestions to fix this? Please help. Thanks in advance!

some logs from /var/log/jitsi/jibri/log.0.txt

When updating the jibri.jar from https://github.com/jitsi/jibri
record_failed.txt (6.4 KB)

When running default jibri.jar
record_working.txt (6.0 KB)

please help sir @bbaldino

Ffmpeg logs will have more info, but looks like an alsa device problem:

2020-06-03 10:32:02.512 INFO: [49] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegProcessUpdate() Ffmpeg quit abruptly. Last output line: plug:bsnoop: Input/output error

I wouldn’t expect this to be different between the two jars…but is it possible you’re running them as different users?

here’s the ffmpeg log when record failed ffmpeg_recordfailed.txt (2.9 KB)

2020-06-03 17:25:01.321 INFO: [616] ffmpeg.call() [alsa @ 0x14dff20] cannot open audio device plug:bsnoop (No such file or directory)

but i have this from aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7

and this from arecord -l

**** List of CAPTURE Hardware Devices ****
card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7

user: jibri

Did you managed to solve this? Im having this same error ussing the jibri docker image. :frowning: Should I override the Dockerfile to use the unstable jibri package instead?