Just upgraded BBB. New recordings not showing in Greenlight

Carl Gosselin

unread,

Mar 27, 2020, 9:06:06 AM3/27/20

to BigBlueButton-dev

Hello - just upgraded to the latest version of BBB. Worked great in my testing environment. But in production, the recordings seem to be stuck in the raw folder. The recordings are not moving through the workflow to create a playback recording.

I looked at the folder permissions and everything looks ok:

$ ls -ahl /var/bigbluebutton

total 2.4M

drwxr-xr-x 549 bigbluebutton bigbluebutton 68K Mar 27 12:23 .

drwxr-xr-x 17 root root 4.0K Mar 27 05:59 ..

drwxr-xr-x 3 bigbluebutton bigbluebutton 4.0K Mar 24 17:37 0007e6f27e3be1c05641d577af7c7be9d7baf8d5-1585071442218

drwxr-xr-x 3 bigbluebutton bigbluebutton 4.0K Mar 26 17:34 0007e6f27e3be1c05641d577af7c7be9d7baf8d5-1585244047508

drwxr-xr-x 3 bigbluebutton bigbluebutton 4.0K Mar 26 17:55 0007e6f27e3be1c05641d577af7c7be9d7baf8d5-1585245303615

drwxr-xr-x 3 bigbluebutton bigbluebutton 4.0K Mar 25 19:01 018afcafb188b1af3871adee8fbc0acaa950aeaa-1585162870573

drwxr-xr-x 3 bigbluebutton bigbluebutton 4.0K Mar 26 16:00 018afcafb188b1af3871adee8fbc0acaa950aeaa-1585238430131

...

You can find attached the bbb-rap-worker.log.

The 27th (yesterday) is when I performed the upgrade. The log idendifies permissions issues but when I reviewed them on the command line it shows the permissions are set for bigbluebutton...

$ ls -ahl /var/bigbluebutton/recording

total 136K

drwxr-xr-x 6 bigbluebutton bigbluebutton 4.0K Mar 31 2019 .

drwxr-xr-x 549 bigbluebutton bigbluebutton 68K Mar 27 12:23 ..

drwxr-xr-x 3 bigbluebutton bigbluebutton 4.0K Mar 27 06:27 process

drwxr-xr-x 3 bigbluebutton bigbluebutton 4.0K Mar 31 2019 publish

drwxr-xr-x 483 bigbluebutton bigbluebutton 52K Mar 27 12:25 raw

drwxr-xr-x 8 bigbluebutton bigbluebutton 4.0K Apr 17 2019 status

I can see the recordings in the raw folder but it's not moving through the rest of the workflow.

Can anyone help?

bbb-rap-worker copy.log

Carl Gosselin

unread,

Mar 27, 2020, 10:09:55 PM3/27/20

to BigBlueButton-dev

I can't seem to resolve this issue. No one can see their new recordings in greenlight after the BBB upgrade last night. Can someone help?

I've looked at the following but can't seem to figure out the issue:

bbb-record --watch

bbb-record --debug

reviewing all different sorts of logs

Is anyone else experiencing this issue?

Raw files are being produced but not going any further.

Mohamed Ali Ahmed

unread,

Mar 28, 2020, 2:43:26 AM3/28/20

to BigBlueButton-dev

Hi Carl,

I am also facing the same issue after upgrading Greenlight yesterday. Can anyone please help?

Dr.D

unread,

Mar 28, 2020, 3:41:36 AM3/28/20

to BigBlueButton-dev

I had the same issue and going it running ..

My logic is the image pulled down did not have the correct bbb-secret in it..

I fixed the .env file and them rebuild the image by doing a 'docker-compose down' and a 'docker-compose up -d'

then a 'bbb-conf --clean'

Carl Gosselin

unread,

Mar 28, 2020, 9:00:11 AM3/28/20

to BigBlueButton-dev

Thanks Dr.D. Unfortunately for me the bb-secret is fine. I also verified the configuration with the following command and everything seems fine as well:

$ docker run --rm --env-file .env bigbluebutton/greenlight:v2 bundle exec rake conf:check

output:

Checking environment: Passed

Checking Connection: Passed

Checking Secret: Passed

Checking SMTP connection: Passed

I can't seem to resolve this issue. If anyone can further guide me I would really appreciate it.

Clients still cannot see their new recordings.

Carl Gosselin

unread,

Mar 28, 2020, 10:24:37 AM3/28/20

to BigBlueButton-dev

ok. I just noticed a new recording in my list for playback. This session was recorded 3 days ago.

Can I conclude that it now takes 3 days to publish a recording?

If so, how can I expedite this process? I've got 96GB of RAM and 20CPUs working for me.

context: in a 2-day period last week, we had 600 sessions.

Dr.D

unread,

Mar 28, 2020, 3:43:59 PM3/28/20

to BigBlueButton-dev

I guess is still the handshaking..between packages,,

Did you do this?

sudo docker run --rm bigbluebutton/greenlight:v2 bundle exec rake secret

Then get the secret_key_base number .. ? and put that in the .env ...

The new image would have a new key_base I would thing..

So the .env need check 4 things..

SECRET_KEY_BASE

BIGBLUEBUTTON_ENDPOINT

BIGBLUEBUTTON_SECRET

DB_PASSWORD --

The other thing to look at is 'docker images' and 'docker-compose images'..

Make sure you are running the "new" image you just loaded.. looking at the dates in docker.. if the image running

is not just installed that could be an issue.. docker purge....

I am just been playing with this a few weeks.. But I found most easy ways I to break it..

and this is one.. This give more of a 404.. if you get a 500 it seems like the database password...assuming

you not hacking code and just swapping out images..

Don

On Saturday, March 28, 2020 at 9:00:11 AM UTC-4, Carl Gosselin wrote:

Carl Gosselin

unread,

Mar 28, 2020, 6:36:22 PM3/28/20

to BigBlueButton-dev

Thanks Dr.D. So I have the following entries in .env

SECRET_KEY_BASE

BIGBLUEBUTTON_ENDPOINT

BIGBLUEBUTTON_SECRET

However, I don't have the following in the .env

DB_PASSWORD --

Is this because I'm not using the latest version of greenlight?

I'm hesitant to run the following command for fear that my version of greenlight may not work anymore if I run it:

sudo docker run --rm bigbluebutton/greenlight:v2 bundle exec rake secret

Are you saying that the latest version of BBB will also require a new SECRET_KEY_BASE for the command above?

Reply all

Reply to author

Forward