search

switnet-ltd / quick-jibri-installer

Bash installer for Jitsi Meet along with Jibri on *buntu LTS based systems | Documentation Available at the Wiki
GNU General Public License v3.0
104 stars 63 forks source link

Jibri doesnt transfer recordings #76

Closed timowevel1 closed 2 years ago

timowevel1 commented 2 years ago

Hey! Suddenly, Jibri stops sending recordings to the main server. Do you have an idea why? It just happens with the new install I made today, did something in Jitsi change?

rsync errors rsync: failed to set times on "/var/jbrecord/.": Operation not permitted (1) rsync: recv_generator: mkdir "/var/jbrecord/averagepeasantsdeviseseldom_2022-03-07-21-21-02" failed: Permission denied (13) Skipping any contents from this failed directory rsync: recv_generator: mkdir "/var/jbrecord/averagepeasantsdeviseseldom_2022-03-07-21-21-57" failed: Permission denied (13) Skipping any contents from this failed directory

Thanks!

Ark74 commented 2 years ago

Have you replicated the same error on a second installation? seems to be a permissions error.

timowevel1 commented 2 years ago

Yes indeed, I replicated it on two other machines, recordings dont get transfered anymore

Ark74 commented 2 years ago

Right now we are a short in time, we'll review this as soon as we complete some priority projects. Please don't hold your breath on it, or at least not now.

timowevel1 commented 2 years ago

No worries, I fixed it by using scp instead, just wanted to tell you^^ Thanks

From: Luis Guzman @.> Sent: Wednesday, March 9, 2022 6:04:05 PM To: switnet-ltd/quick-jibri-installer @.> Cc: timololipop @.>; Author @.> Subject: Re: [switnet-ltd/quick-jibri-installer] Jibri doesnt transfer recordings (Issue #76)

Right now we are a short in time, we'll review this as soon as we complete some priority projects. Please don't hold your breath on it, or at least not now.

— Reply to this email directly, view it on GitHubhttps://github.com/switnet-ltd/quick-jibri-installer/issues/76#issuecomment-1063151362, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGA5FLZTW3EOSHTMPUUESZTU7DKYLANCNFSM5QENAP2A. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>

timowevel1 commented 2 years ago

@Ark74 I am just curious, do you have an idea why Jitsi uses two Jibris to record ONE meeting? I am autoscaling in aws, on bootup the nickname gets changed but it happens, that two or even three instances sometimes record the same meeting. Do you have an idea?

Ark74 commented 2 years ago

It only uses one, it will try to connect to the one it responds first, if not it may go to the next node, you might want to look for a setting that might increase the wait time. Seems like your nodes are taking the same amount to respond and is not fast enough to lock one up definitely for such meeting.

timowevel1 commented 2 years ago

Yes indeed, thank you, I fixed it buy firing up chrome on startup.