Jibri is installed and running but issue during start recording in jitsi-meet.

Question

Jibri is installed and running but issue during start recording in jitsi-meet.

515solutions opened this issue 2 years ago · 19 comments

515solutions commented 2 years ago

jibri is installed successfully and running.

checked the jifofo logs:-
tail -F /var/log/jitsi/jicofo.log

having issue unable to find an available jibri or failed to start jibri session.

Answer 1 · 2022-08-02T13:02:15.000Z

Is it docker-compose setup ?

Answer 2 · 2022-08-04T02:34:08.000Z

No it is not.

…

On Tue, Aug 2, 2022 at 8:02 AM Debendra Oli ***@***.***> wrote: Is it docker-compose setup ? — Reply to this email directly, view it on GitHub <#489 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVYBJCOBYEVOF4WN44O4VHLVXEL6FANCNFSM545WNLGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 3 · 2022-08-04T08:25:17.000Z

Looks like jibri is not configured properly hence not available to jicofo.

Answer 4 · 2022-08-04T14:50:52.000Z

Could you point out the issue? Also would you send me the docker file.

…

On Thu, Aug 4, 2022 at 3:25 AM Debendra Oli ***@***.***> wrote: Looks like jibri is not configured properly hence not available to jicofo. — Reply to this email directly, view it on GitHub <#489 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVYBJCKH5TECSG6YOQQFXKDVXN47PANCNFSM545WNLGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 5 · 2022-08-04T15:15:27.000Z

I cannot really say without looking the jibri logs.

Answer 6 · 2022-08-04T15:18:00.000Z

Do you want me to send you logs

…

Sent from my iPhone

On Aug 4, 2022, at 10:15 AM, Debendra Oli ***@***.***> wrote: I cannot really say without looking the jibri logs

Answer 7 · 2022-08-04T17:59:56.000Z

You can post here.

Answer 8 · 2022-08-06T12:40:30.000Z

Attached are the logs

…

On Thu, Aug 4, 2022 at 1:00 PM Debendra Oli ***@***.***> wrote: You can post here. — Reply to this email directly, view it on GitHub <#489 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVYBJCKRJHTJ2I6IBO2NOCDVXQAKPANCNFSM545WNLGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 9 · 2022-08-09T17:15:45.000Z

Hi Just following up on the recording issue. I already shared the logs with you guys couple of days ago Thanks Navroze

…

On Thu, Aug 4, 2022 at 1:00 PM Debendra Oli ***@***.***> wrote: You can post here. — Reply to this email directly, view it on GitHub <#489 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVYBJCKRJHTJ2I6IBO2NOCDVXQAKPANCNFSM545WNLGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 10 · 2022-08-09T17:33:18.000Z

Those logs are not enough, you need to provide full jibri logs from /var/logs/jitsi/jibri/log.0.log.

I am not sure about the exact filename but just to give you a gist.

Answer 11 · 2022-08-09T18:28:37.000Z

Here is the log file..

…

On Tue, Aug 9, 2022 at 1:08 PM navroze brar ***@***.***> wrote: Here is the log file. On Tue, Aug 9, 2022 at 12:33 PM Debendra Oli ***@***.***> wrote: > Those logs are not enough, you need to provide full jibri logs from > /var/logs/jitsi/jibri/log.0.log. > > I am not sure about the exact filename but just to give you a gist. > > — > Reply to this email directly, view it on GitHub > <#489 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AVYBJCL526F6LFSCNWZKNVDVYKI6RANCNFSM545WNLGA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

Answer 12 · 2022-08-29T18:33:08.000Z

Hello Did you guys get a chance to look at logs? We need to go to production next month and would need go live with recording feature Thanks Navroze

…

On Mon, Aug 15, 2022 at 12:29 PM navroze brar ***@***.***> wrote: Just following up on the log file sent by me last week Did you find anything? On Tue, Aug 9, 2022 at 1:08 PM navroze brar ***@***.***> wrote: > Here is the log file. > > On Tue, Aug 9, 2022 at 12:33 PM Debendra Oli ***@***.***> > wrote: > >> Those logs are not enough, you need to provide full jibri logs from >> /var/logs/jitsi/jibri/log.0.log. >> >> I am not sure about the exact filename but just to give you a gist. >> >> — >> Reply to this email directly, view it on GitHub >> <#489 (comment)>, or >> unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AVYBJCL526F6LFSCNWZKNVDVYKI6RANCNFSM545WNLGA> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >

Answer 13 · 2022-08-30T08:10:20.000Z

There are no logs to look at. Use github interface to paste your logs.

Answer 14 · 2022-08-30T21:16:55.000Z

I am going to attach log file here
@debendraoli
log.0 (1).txt
Please let me know what do you think

Answer 15 · 2022-08-31T05:32:34.000Z

WARNING: [30] [hostname=35.223.189.86 id=35.223.189.86] MucClient.lambda$getConnectAndLoginCallable$7#630: Error connecting:
org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [/35.223.189.86:5222] (/35.223.189.86:5222)' failed because: java.net.SocketTimeoutException: connect timed out

You jibri is not reaching your prosody. Looks like prosody port is not open.

Answer 16 · 2022-10-07T13:27:45.000Z

@debendraoli Prosody Port is already opened but still it is not working. Do you have any other suggestion?

Answer 17 · 2022-10-07T16:36:37.000Z

Issue is with network port which is failing to reach to the destination.

Logs clearly states that. There is no other way around.

Try reaching your prosody from your jibri instance manually.

Try following:
curl prosody_ip_here:5222

Either your prosody port is not reachable due to firewall or you have wrong ip address configured jibri trying to reach.

Answer 18 · 2022-10-11T07:10:14.000Z

Just following up on the log file sent by me last week Did you find anything?

…

On Tue, Aug 9, 2022 at 1:08 PM navroze brar ***@***.***> wrote: Here is the log file. On Tue, Aug 9, 2022 at 12:33 PM Debendra Oli ***@***.***> wrote: > Those logs are not enough, you need to provide full jibri logs from > /var/logs/jitsi/jibri/log.0.log. > > I am not sure about the exact filename but just to give you a gist. > > — > Reply to this email directly, view it on GitHub > <#489 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AVYBJCL526F6LFSCNWZKNVDVYKI6RANCNFSM545WNLGA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

Answer 19 · 2022-10-11T09:54:05.000Z

I previously pointed out above that your jibri cannot reach your prosody server.

I suggest you create topic on community forum. https://community.jitsi.org/