Possible Bug in Big Blue Button Plugin for Moodle (Playback of Old Recordings)

[Steffen Moser]

Hi all,

I hope I am at the correct place here to report a bug of the Big Blue Button plugin for the learning management system Moodle. The problem occurred before we upgraded from Big Blue Button 1.1 to Big Blue Button 2.0-RC2, so it is clearly not related to Big Blue Button 2.0.

Problem statement: Old recordings, generated, for example, with a Big Blue Button Moodle plugin from 2015, cannot be played back anymore after upgrading the Moodle Big Blue Button plugin to version 2.2.4. The following message is shown to the user: "Current state was not found. The recording may have been deleted or the Big Blue Button server is not compatible with the action performed." No problem occurs with version 2.1.7 of the plugin, no matter which Big Blue Button version (1.1 or 2.0-RC2) is used.

Reprocessing the recorded videos under Big Blue Button 1.1 or 2.0-RC2 doesn't solve the problem, either.

Here you'll find the results of two "getRecordings" API calls: The first one is related to a request for a non-functional recording, generated in 2016 with a plugin build of 2015. The second one is related to a request for a functional recording, generated in 2017 with a plugin build of 2016.

Maybe the non-existing differentiation between internal and external meetingID is the cause for the problem with the old recordings.

Does anybody have an idea how to solve this?

Thank you very much in advance!

Kind regards,
Steffen

[Jesus Federico]

Hi Steffen,

In the new version the URL to the actual recording is served by the plugin, in the old version the URL is the link you see in the recording list. There are two things that come to my mind.

1. Are you trying to access a recording or a link to an imported recording?

2. When you migrated the pugin, from what version to what version did you run the upgrade, was the original one 2.1.7?. The latest version (2.2.4) can (and should) only be upgraded from

Can be updated from

2.1.0-beta, 2.1.0-beta, 2.1.0-rc, 2.1.0-rc, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.1.8, 2.1.9, 2.1.10, 2.1.11, 2.1.12, 2.1.13, 2.1.14 (2016051919), 2.2-beta, 2.2-beta, 2.2-beta, 2.2-beta, 2.2-beta, 2.2-beta, 2.2-beta, 2.2-rc, 2.2-rc, 2.2-rc, 2.2-rc, 2.2 (2017101008), 2.2.1 (2017101009), 2.2.2 (2017101010), 2.2.3 (2017101011)

[Jesus Federico]

Hi Steffen,

I just run a quick test migrating from 2.1.7 to 2.2.4. All good on my end. I'll wait for your condifmration, BUT, since the error message comes from javascript, I am wondering if you tried cleaning the cache both in Moodle and in your browser.

On Thursday, July 26, 2018 at 4:56:07 AM UTC-4, Steffen Moser wrote:

[Steffen Moser]

Hi Jesus,

thank you very much for your fast reply!

On Thursday, July 26, 2018 at 4:40:36 PM UTC+2, Jesus Federico wrote:

Hi Steffen,

In the new version the URL to the actual recording is served by the plugin, in the old version the URL is the link you see in the recording list. There are two things that come to my mind.

Yes, we noticed this change of behavior, but we are not sure whether it is linked to the problem we encounter...
 

1. Are you trying to access a recording or a link to an imported recording?

What exactly do you mean by "imported recording"? The recordings have been created by using an old Moodle Big Blue Button plugin. We try to access these recordings now directly from Moodle by opening an old course and clicking on the (new) "Recording" activity, so there are no handmade hyperlinks in the course. The Big Blue Button recordings themselves have been re-processed by Big Blue Button after an upgrade of Big Blue Button from 0.8x to 0.9x as described here. As far as I remember, this didn't impair the ability to run them. Even today, when using a backup Moodle instance running an old Big Blue Button Moodle plugin (e.g. 2.1.7),  we can playback the old recordings. The problem does only seem to occur when trying to playback an old recording (produced with older or equal to 2.0.4) with the new plugin (2.2.x).
 

2. When you migrated the pugin, from what version to what version did you run the upgrade, was the original one 2.1.7?. The latest version (2.2.4) can (and should) only be upgraded from

The non-working recordings have been created in Moodle 2.9.2+ and Big Blue Button Moodle plugin 2.0.4 (2015080611).

Just a short overview of "our" history of the last two years:
 - We upgraded to Big Blue Button Moodle plugin 2.1.7 (2016051911) and later to Moodle 2.9.7.
 - We upgraded further to Moodle 3.1.7 and Big Blue Button Moodle plugin 2.1.12 (2016051917).
 - The problems started to occur after we upgraded the Big Blue Button Moodle plugin to 2.2.3 (2017101011), still on Moodle 3.7 (in order to prepare an Moodle upgrade to 3.1.12+).
 - The problem is still there with Moodle 3.1.12+ and Big Blue Button Moodle plugin 2.2.4 (2017101012).

Only recordings done with Big Blue Button Moodle plugin 2.0.4 (2015080611) or older seem to be affected. Recordings done with Big Blue Button Moodle plugin 2.1.7 (2016051911) or newer are working without any problems with even with the newest 2.2.4.

As far as I can see, the headers of the "recording record" in the "getRecordings" API call output seem to have changed between 2.0.4 and 2.1.7. The record of a 2.0.4 recording starts with:

<recording>
  <recordID>
    d2963e2362db6b5bd8ff5a9ecb65577741aa54c5-1466697431178
  </recordID>
  <meetingID>
    d2963e2362db6b5bd8ff5a9ecb65577741aa54c5-1466697431178
  </meetingID>
  <name>Online Meeting</name>
  <isBreakout>false</isBreakout>
  <published>true</published>
  <state>published</state>
  <startTime>1466697431178</startTime>
  <endTime>1466703067403</endTime>
  <participants>0</participants>
  <metadata>
    <bn-origin>Moodle</bn-origin>
    <bbb-origin-tag>moodle-mod_bigbluebuttonbn (2015080611)</bbb-origin-tag>
    <bbb-recording-tags/>
    <bbb-origin-server-common-name/>
    <bbb-origin-version>2.9.2+ (Build: 20150924)</bbb-origin-version>
    <bbb-recording-name>Online Meeting</bbb-recording-name>
    <bbb-context>SaS - Signals and Systems - SoSe 2016</bbb-context>
    <meetingName>Online Meeting</meetingName>
    <meetingId>e009eadb5b7d25f18892cbadd7d9fe9d-87-157</meetingId>
    <bbb-recording-description/>
    <bbb-origin-server-name>XXXXX</bbb-origin-server-name>
  </metadata>


The record of a 2.1.7 recording starts with:

<recording>
  <recordID>
    ce399bb4d7623856baffdff17038681ef7d7973b-1496239709834
  </recordID>
  <meetingID>0e157723bf48bc567f5885bb4d79a729c78dad98-146-265</meetingID>
  <internalMeetingID>
    ce399bb4d7623856baffdff17038681ef7d7973b-1496239709834
  </internalMeetingID>
  <name>Webinar</name>
  <isBreakout>false</isBreakout>
  <published>true</published>
   <state>published</state>
  <startTime>1496239709834</startTime>
  <endTime>1496239825573</endTime>
  <participants>1</participants>
  <metadata>
    <bn-origin>Moodle</bn-origin>
    <bbb-origin-tag>moodle-mod_bigbluebuttonbn (2016051911)</bbb-origin-tag>
    <bbb-recording-tags/>
    <bbb-origin-server-common-name/>
    <bbb-origin-version>2.9.2+ (Build: 20150924)</bbb-origin-version>
    <bbb-recording-name>Webinar</bbb-recording-name>
    <bbb-context>TPS - Technical Presentation Skills - SoSe 2017</bbb-context>
    <meetingName>Webinar</meetingName>
    <meetingId>0e157723bf48bc567f5885bb4d79a729c78dad98-146-265</meetingId>
    <bbb-recording-description/>
    <isBreakout>false</isBreakout>
    <bbb-origin-server-name>XXXXX</bbb-origin-server-name>
  </metadata>

The most prominent difference I see is that the "internalMeetingID" is missing in the old recordings. Could it be possible that this is the cause of the problem?

Kind regards,
Steffen

[Steffen Moser]

Hi Jesus,

On Thursday, July 26, 2018 at 7:11:48 PM UTC+2, Jesus Federico wrote:

Hi Steffen,

I just run a quick test migrating from 2.1.7 to 2.2.4.

O.K., I also don't have a problem between these versions.

My problem are recordings which were done with 2.0.4. We could playback them with 2.1.7, but we cannot playback them anymore since we upgraded to 2.2.3 or 2.2.4. Recordings from newer versions don't pose a problem.
 

All good on my end. I'll wait for your condifmration, BUT, since the error message comes from javascript, I am wondering if you tried cleaning the cache both in Moodle and in your browser.

Thank you for this hint. We emptied both, the browsers and Moodle's caches - but unfortunately without any success.

Kind regards,
Steffen

[Marco Filippetti]

Hi, we are facing exactly the same problem. After upgrading moodle BBB plugin to the latest version, none of our old recordings are accessible. Hopefully there will be a fix for this soon...

Regards!

Marco

[Zeeshan Ali Shah]

can u access the recordings using api mate ? giving same course name ? ..

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Jesus Federico]

Hi Stefen,

Sorry for the delay, I usually lose track if I don't get a response in 1 or 2 days.

No, the problem is not the InternalMeetingID. That is not used by the plugin.

The XML samples you posted definitely helped to narrow it down, but unfortunately it is not complete. The problem may be the XML for the playback element (which you did not include :) )

It should look something like this

<playback>

<format>

<type>presentation</type>

<url>

http://test-install.blindsidenetworks.com/playback/presentation/2.0/playback.html?meetingId=a169ddf7a2adbf4d545f8e0aed14036f50c32aa0-1533102313323

</url>

<processingTime>5819</processingTime>

<length>0</length>

<preview>

<images>

<image alt="Welcome To BigBlueButton" height="136" width="176">

http://test-install.blindsidenetworks.com/presentation/a169ddf7a2adbf4d545f8e0aed14036f50c32aa0-1533102313323
/presentation/2a47a10bf6c37b6ad2d9a672040fbde4b5ae187f-1533102313336/thumbnails/thumb-1.png

</image>

<image alt="This slide left blank for whiteboard" height="136" width="176">

http://test-install.blindsidenetworks.com/presentation/a169ddf7a2adbf4d545f8e0aed14036f50c32aa0-1533102313323
/presentation/2a47a10bf6c37b6ad2d9a672040fbde4b5ae187f-1533102313336/thumbnails/thumb-2.png

</image>

<image alt="This slide left blank for whiteboard" height="136" width="176">

http://test-install.blindsidenetworks.com/presentation/a169ddf7a2adbf4d545f8e0aed14036f50c32aa0-1533102313323
/presentation/2a47a10bf6c37b6ad2d9a672040fbde4b5ae187f-1533102313336/thumbnails/thumb-3.png

</image>

</images>

</preview>

</format>

</playback>

No worries, I'm not interested in the content. You can remove the URLs but I would like to see the rest of the XML

I am going to run a few more tests on my end and let you know if I find something. But please try to respond sooner, I may get caugth in another integration if you don't :D

Cheers,

Jesus Federico

[Jesus Federico]

No idea where the problem can be. I reproduced the migrations as you described creating recordings in the process. All of them work.

The only think I did not try was to convert recordings from 1.1 to 2.0, but that should not affect anything.

Do you still have the error in javascript? IS there anything else in the browser console?

JF

[Marco Filippetti]

Hi Jesus, sorry to jump in, but we were also affected by this issue... 

The problem for us happened affecting recordings made using BBB v1.0 and Moodle plugin version 2.0.4. After migrating BBB to V2.0 and also upgrading the plugin to version 2.2.4, the old recordings were no longer available - the error mentioned before was presented: "Current state was not found. The recording may have been deleted or the Big Blue Button server is not compatible with the action performed." After rolling back to the previous version (2.0.4) of the Moodle BBB plugin, recordings were available again. Not sure if the issue is a combination of things - new version of BBB plus new version of the plugin and old versions of recordings... could be. 

For now, we are running the latest version of BBB (2.0) but had to stick with Moodle plugin version 2.0.4.

No complaints, to be honest. It is working fine as it is for us. 

Great job you guys are doing with the BBB platform, by the way! Kudos!!!

Cheers

Marco Filippetti

--
You received this message because you are subscribed to a topic in the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bigbluebutton-dev/UPNN2emwcR8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bigbluebutton-...@googlegroups.com.

[Jesus Federico]

Hi Marco,

On Friday, August 10, 2018 at 5:33:25 PM UTC-4, Marco Filippetti wrote:

Hi Jesus, sorry to jump in, but we were also affected by this issue... 

No worries, we are here to help.

 

The problem for us happened affecting recordings made using BBB v1.0 and Moodle plugin version 2.0.4. After migrating BBB to V2.0 and also upgrading the plugin to version 2.2.4,

Alright, just to be clear. What are the steps you followed? I need to be able to reproduce it first.

Starting with BBB v1.0 and Moodle 2.0.4, create a recording and it should be shown in the activity used for creating it.

Then, what?

- Migrated the recording to a BBB 2.0 server (did you also excecuted sudo bbb-conf --setip in the BBB 2.0, assuming you are using an IP different that the one used in BBB 1.0?)

- Upgrated BigBlueButtonBN to 2.2.4 (did you migrated directly or gradually?, if you did directly you may have missed some migrations in the process. That may be irrelevant but I want to make sure and reproduce in the same way)

- With the new version you create a new recording and it shows up and the old one doesn't

Is this correct?

 

the old recordings were no longer available - the error mentioned before was presented: "Current state was not found. The recording may have been deleted or the Big Blue Button server is not compatible with the action performed."

This is a javascript error, I haven't figured out why is it comming. This is triggered when the action can not be processed, in this case the "play" action seems to be failing.

 

After rolling back to the previous version (2.0.4) of the Moodle BBB plugin, recordings were available again. Not sure if the issue is a combination of things - new version of BBB plus new version of the plugin and old versions of recordings... could be. 

The thing is that there is a validation in the server before doing the actual redirect. In the old version is was just an hyperlink to the playback content.

For now, we are running the latest version of BBB (2.0) but had to stick with Moodle plugin version 2.0.4.

No complaints, to be honest. It is working fine as it is for us. 

Thanks man. Sure thing. But it is not acceptable for our high standards, so let's fix this thing :D

 

I'll keep posting my findings here, but please help me to 1. Find the steps to reproduce it, 2. Test the changes in the plugin once they are implemented (if any)

Cheers,

JF

[Henri Urpalainen]

Hi,

Problem is not the Bigbluebutton 2.0 version it's the Bigbluebutton Moodle-plugin.

We've  BigBlueButton Server 1.1.0 (565) installation and videos are broken also there with new Moodle-plugin. This is new installation and videos transfered from old 0.9 version.

BigBlueButtonBN mod_bigbluebuttonbn

2.2.4 2017101012

Recording can be seen with the straight url to it (https://domain/playback/presentation/0.9.0/playback.html?meetingId=31853603b688f3aa1e71b18115046bcc140cfccb-1481707115800). Tried to rebuild that "broken" recording, but that didn't help.

I not sure, but i think we upgrade from this version:

$plugin->version  = 2016051903;

$plugin->component = 'mod_bigbluebuttonbn';

$plugin->maturity = MATURITY_RC;

$plugin->release  = '2.1.0';

New recording from the same activity instance can be seen with out problems and when looking page source i didn't see differences and link is same kind with 0.9.0 in it https://domain/playback/presentation/0.9.0/playback.html?meetingId=31853603b688f3aa1e71b18115046bcc140cfccb-1535437807165.

Error:

Current state was not found. The recording may have been deleted or the BigBlueButton server is not compatible with the action performed.

Henri

[Henri Urpalainen]

Hi,

Made more tests.

2.1.14 ($plugin->version  = 2016051919;) works ok, but 2.2 ($plugin->version = 2017101008;) version not.

Henri

[Henri Urpalainen]

Hi,

Moved broken record to new BBB 2.0-RC5 server and rebuild it.

Now it's found https://new_domain/playback/presentation/2.0/playback.html?meetingId=209b2953276172ed33261c0fd06fa953680e8277-1481790035756, but it still not work in Moodle where is newest BBB-plugin installed.

Henri

[Henri Urpalainen]

Hi,

Last test from me.

I think it's problem with videos recorded with BBB 0.80 or 0.90. Is there way to check what version of BBB is used to record meeting?

Made test where I recorded meeting with BBB plugin  2.1.0 (2016051903)  using our BBB 1.0 instance and upgraded Moodle plugin to 2.2.5 (2017101013) and it worked alright.

Henri

[Henri Urpalainen]

Hi,

Sorry for post flood, but our BBB is 1.1 now and i think that it was 1.0 when those old meetings have been recorded.

Maybe upgrade is not worked or something else, but why it won't work when it's rebuild on newer BBB?

Henri

[Marcus Cross]

We are getting this problem too. 

Plugin version:

2.2.6

2017101014

When I click on a recording to play it, I get this message:

[Marco Filippetti]

I guess that, as of now, the best way to deal with the problem is simply not to upgrade the Moodle plugin. The older version of the plugin works fine with the latest version of BBB. That's the choice we have made and, so far, no issues. We didn't see the point in upgrading the plugin anyways. Not a lot of benefits in doing so. Once the problem has been fixed, maybe we will consider trying the upgrade again.

Marco

--

[Jesus Federico]

Hi Henri,

One thing you missed to mention is, what version of Moodle you have?

JF

[Henri Urpalainen]

Hi,

We've tried with Moodle that is upgraded from 3.1.9 to 3.3.x and is now 3.3.7+, but it happens also in 3.1.9 Moodle with new version.

Henri

[Jesus Federico]

Hi Henri,

It turns out not to be an issue with the plugin but with BBB itself. I filed a bug report, see https://github.com/bigbluebutton/bigbluebutton/issues/6089, there should be a fix soon.

In the meanwhile if you want to workaround this bug, you can use the patched version of the plugin available here https://github.com/jfederico/moodle-mod_bigbluebuttonbn/tree/CONTRIB-7450, or you can patch your own deployed plugin with the code in the commit.

Keep in mind that this patch is not necessarily going to the next release.

Cheers,

JF

On Wednesday, September 19, 2018 at 9:18:52 AM UTC-4, Henri Urpalainen wrote:

Hi,

[Henri Urpalainen]

Hi,

Tried that workaround, but if nothing is needed in BBB-side it doesn't work for me. It gives the same error.

Current state was not found. The recording may have been deleted or the BigBlueButton server is not compatible with the action performed

Henri

[Jesus Federico]

My bad. These are the updates you would have to apply: 

https://github.com/jfederico/moodle-mod_bigbluebuttonbn/blob/ddb18f41e8e65139ec2ff6ba8c4a18a1c188dee6/locallib.php#L322-L328

But anyways, in BBB you can also fix for good all the recordings migrated from a previous version using this script.

https://github.com/jfederico/bigbluebutton/blob/v2.2-dev/record-and-playback/core/scripts/bbb-1.1-meeting-tag

The only thing you need to do is to create a file with that code  in your BigBlueButton server:

sudo vi /usr/local/bigbluebutton/core/scripts/bbb-1.1-meeting-tag

Change the permissions

sudo chmod +x /usr/local/bigbluebutton/core/scripts/bbb-1.1-meeting-tag

And run the script

sudo /usr/local/bigbluebutton/core/scripts/bbb-1.1-meeting-tag

And you should have your old recordings migrated. So, no need to patch Moodle.

Let us know how it goes.

JF

On Thursday, September 20, 2018 at 4:36:30 AM UTC-4, Henri Urpalainen wrote:

Hi,

[Henri Urpalainen]

Hi,

Now the workaround works. Thank you.

I try that script next week.

Henri

[Henri Urpalainen]

Hello,

The script is working as described. Thanks.

Henri

[acevedo...@gmail.com]

Hi Jesús,

I tried following your instructions but it ended with the following error mesagges:

root@ubuntu:~# nano /usr/local/bigbluebutton/core/scripts/bbb-1.1-meeting-tag
root@ubuntu:~# sudo chmod +x /usr/local/bigbluebutton/core/scripts/bbb-1.1-meeting-tag
root@ubuntu:~# sudo /usr/local/bigbluebutton/core/scripts/bbb-1.1-meeting-tag
Traceback (most recent call last):
        8: from /usr/local/bigbluebutton/core/scripts/bbb-1.1-meeting-tag:3:in `<main>'
        7: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
        6: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
        5: from /usr/local/bigbluebutton/core/lib/recordandplayback.rb:24:in `<top (required)>'
        4: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
        3: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
        2: from /usr/local/bigbluebutton/core/lib/recordandplayback/events_archiver.rb:21:in `<top (required)>'
        1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot load such file -- redis (LoadError)

As I'm running BigBlueButton Server 2.7.9 (666) I don't know if there are some modifications needed for the script to work.

Thanks in advance for any help.

Regards,

German