[v.3.0.2] record list does not refresh without re-sync

[amg-web]

After recording is done the processing message appeared in a few minutes and stay endless.

I have to use re-sync to get list of records updated.

[scouillard]

Hi, Would you please share the server logs that appears after ending a meeting that is being recorded? Thank you.

[amg-web]

glv3.txt bbb26_logs.zip

gl shows meeting as processing. actually it's already published. gl logs without pushing re-sync

[hiroshisuga]

Same here. My /var/log/bigbluebutton/post_publish.log looks like:

I, [2023-03-23T16:14:55.373732 #234556] INFO -- : Recording Ready Notify for [ebf87fc2b006750f384e447342c1250e8062b46b-1679555664043] starts I, [2023-03-23T16:14:55.373784 #234556] INFO -- : Task: Getting meeting metadata I, [2023-03-23T16:14:55.374302 #234556] INFO -- : Making callback for recording ready notification I, [2023-03-23T16:14:55.374401 #234556] INFO -- : Task: Getting external meeting id I, [2023-03-23T16:14:55.374424 #234556] INFO -- : Task: Getting meeting metadata I, [2023-03-23T16:14:55.375880 #234556] INFO -- : Sending request to https://MY_SERVERS_URL//recording_ready I, [2023-03-23T16:14:55.487564 #234556] INFO -- : Recording notifier successful: ebf87fc2b006750f384e447342c1250e8062b46b-1679555664043 (code 200) I, [2023-03-23T16:14:55.487635 #234556] INFO -- : Recording Ready notify ends

I replaced my server's FQDN with MY_SERVERS_URL. This line seems weird but I am not sure...

[amg-web]

v.3.0.3.1 record list stll not refreshed. even if I visit in a few hours

[lightweight]

If you (or the Greenlight admin) 're-sync' the room's recordings (via the Administrator Panel -> Server Rooms -> the room's three-dot menu -> 'Re-Sync Recordings') any that have completed successfully should show up. I think this is a bug in Greenlight 3.0.2...

[amg-web]

@lightweight I know this way, but it does not work for non admin users. shell Admin login everyday and resync users records? or may be user want to see his record asap ?

[lightweight]

Yeah, it's a problem. I guess a frequent cron job running rake server_recordings_sync as noted in #5063 is an interim option... but it needs a fix in Greenlight.

[amg-web]

@lightweight thanks

I expected records database on BBB side. it whould produce records operations api response faster.

[amg-web]

@lightweight after running cron I have this in room settings:

second record is not listed, as I deleted it. but processing lines is still there. everyhting is ok in user record list:

[lightweight]

Hmm - so the recordings aren't showing (that you expect to show)? Are they perhaps 'unpublished' and need to be published to show?

Also - I run BBB using Docker, and I haven't yet worked out how to get the 'video' functionality to work - seems very cool...

[amg-web]

Hmm - so the recordings aren't showing (that you expect to show)? Are they perhaps 'unpublished' and need to be published to show?

record added, but processing lines are not removed

[amg-web]

Also - I run BBB using Docker, and I haven't yet worked out how to get the 'video' functionality to work - seems very cool...

looks good and processed faster then 3rd party bbb mp4 script, but result looks different and people does not want to change familiar record layout

[scouillard]

Hi amg-web, Would you please share the logs from GLv3.0.3 and BBB, like you did before? I thought #5114 would fix it as per the error logs from your BBB logs. Thank you.

[amg-web]

@scouillard bbb265.zip

[scouillard]

When a recording is ready, the BBB server will hit up the GL server /recording_ready endpoint with the recording data. However, the request does not seem to reach your Greenlight server. We need to test the connection between your two servers. Could you ssh into your BBB server and ping your hostname?

[amg-web]

@scouillard Thanks I found failed location in my configs It was custom location for mp4 records and it catched /recording_ready uri

[scouillard]

Glad to hear @amg-web!

[lightweight]

When a recording is ready, the BBB server will hit up the GL server /recording_ready endpoint with the recording data. However, the request does not seem to reach your Greenlight server. We need to test the connection between your two servers. Could you ssh into your BBB server and ping your hostname?

That's very useful - I'll check my install, too. I'm running my BBB via the Docker recipe and I need to work out which container needs to be able to see the Greenlight container - can you clarify which service actually submits the request to recording_ready?

[lightweight]

@scouillard - I'm trying to work out exactly how the 'Greenlight server' that the 'BBB server' contacts (to confirm a completed recording) is defined - is it the site's FQDN? I need to work out what I need to tweak in my Docker container configs to a) which server is talking to Greenlight, b) how it's trying to address it, c) why it's failing now, and d) how to ensure it's got the right address specified... I can use extra_aliases to specify other hosts' addresses for each container, but I'm not sure what needs to be specified where...

[scouillard]

Hi, Your GLv3 url should be set up in your GLv2 ENV file. https://docs.bigbluebutton.org/greenlight/v3/migration#configuring-the-environment

After changing your ENV variable, please don't forget to run docker-compose build

Just FYI, that should not be an issue for you - or anyone really, your BBB server will contact your GL server as the /recording_ready endpoint is provided in the intial url query parameters to create a meeting that has recording enabled.