Jibri didn't save file in defined path

[Mohammad_Reza_Hossei]

Hello friends
I have set up a Jibri service on the latest version of Jitsi
Currently, the saving and recording of a Jitsi ROM is done on the user’s own device, which is downloaded after the end of the recording.

I want the recorded files from each event to be saved in a path like srv/recording so that I can access the files later.

I have done all the settings now but there is a problem

output of systemctl status jibri.service :

● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-03-27 14:03:05 UTC; 1 day 16h ago
Process: 17922 ExecStart=/opt/jitsi/jibri/launch.sh (code=exited, status=1/FAILURE)
Main PID: 17922 (code=exited, status=1/FAILURE)

Mar 27 14:03:05 jitsi-ubuntu-4gb-hel1-1 systemd[1]: jibri.service: Scheduled restart job, restart c>
Mar 27 14:03:05 jitsi-ubuntu-4gb-hel1-1 systemd[1]: Stopped Jibri Process.
Mar 27 14:03:05 jitsi-ubuntu-4gb-hel1-1 systemd[1]: jibri.service: Start request repeated too quick>
Mar 27 14:03:05 jitsi-ubuntu-4gb-hel1-1 systemd[1]: jibri.service: Failed with result ‘exit-code’.
Mar 27 14:03:05 jitsi-ubuntu-4gb-hel1-1 systemd[1]: Failed to start Jibri Process.

[yasen]

This shows that Jibri is not working - it says it failed to start.

Without Jibri your option for recording is only a local one, that’s why you don’t have the server-side recording by Jibri, only the local in-browser ones.

You should try to fix Jibri - check its logs in /var/log/jitsi/jibri/ to see why it’s not starting.

[Mohammad_Reza_Hossei]

hi yasen

tnx for helping

this is outpot of jibir log from /var/log/jitsi/jibri :

==> log.0.txt <==
2023-03-27 14:03:05.247 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.1.txt <==
2023-03-27 14:03:04.714 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.2.txt <==
2023-03-27 14:03:04.214 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.3.txt <==
2023-03-27 14:03:03.725 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.4.txt <==
2023-03-27 14:03:03.143 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.5.txt <==
2023-03-27 13:29:27.467 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.6.txt <==
2023-03-27 13:29:26.989 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.7.txt <==
2023-03-27 13:29:26.485 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.8.txt <==
2023-03-27 13:29:25.968 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

==> log.9.txt <==
2023-03-27 13:29:25.364 INFO: [1] MainKt.handleCommandLineArgs#186: Jibri run with args [–config, /etc/jitsi/jibri/config.json]

I think the problem is due to the changes I made in the configuration

[Freddie]

What guide did you follow to install Jibri? Did you install on a server that already has a desktop environment? Do you have a properly-configured jibri.conf?

[Mohammad_Reza_Hossei]

Hello freddie

I used YouTube’s guide to install Jibri on a virtual server on Hertzner
And this server does not have a graphical desktop environment

and yes , i already config the jibri.conf with xmpp credential

[Freddie]

The log lines you share seem to point to Jibri trying to run using config.json. Not sure what guide you’re referring to on YouTube, but I’d recommend you try using this one instead:

TUTORIAL - How to Install the NEW JIBRI

If you’re here, you likely already know what Jibri is and you are looking to deploy it in your own environment (or upgrade your already installed instance to the latest version). You WILL need to install this latest version of Jibri or upgrade to this latest version (if you already deployed Jibri) as there will no longer be support for the previous version soon. To make this as concise as possible, I won’t go into the architecture and all the features of Jibri. You can check out my other Tutori…

And you can check this tutorial for troubleshooting tips:

TUTORIAL: Jibri Overview, Troubleshooting Tips & Tricks - Solve your Jibri Problems, Quickly!

It seems that most people find Jibri implementation to be the most challenging of the suite of solutions. I am by no measure an expert on this, but I’ve done several installs of Jibri, purged it a number of times and reinstalled, so I thought I should share some of what I’ve gained with anyone who may find it useful. I’ll try to explain this in layman terms, so the information is not overwhelming. This is a long read, but it will save you a lot of time and a lot of headache trying to figure out …

[aposazhennikovspb]

I have the same issue. I used this manual for install TUTORIAL - How to Install the NEW JIBRI
I can download record on my own computer, but i doesn’t create at /srv/recordings