Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-74558

BBB error message when activity deleted

    XMLWordPrintable

Details

    • MOODLE_400_STABLE
    • MOODLE_400_STABLE
    • MDL-74558-master
    • Hide
      Setup
      1. Make sure debugging is turned off

        mdk run undev
        

      2. Clear cron: php admin/cli/cron.php
      Test
      1. Log in as admin
      2. Create a BBB activity in a given course
      3. Delete the activity
      4. Run ad-hoc tasks

        php admin/cli/adhoc_task --execute
        

      5. Confirm that the error "Cannot find the BigBlueButton activity" with debugging trace does not appear in the logs.
      Show
      Setup Make sure debugging is turned off mdk run undev Clear cron: php admin/cli/cron.php Test Log in as admin Create a BBB activity in a given course Delete the activity Run ad-hoc tasks php admin/cli/adhoc_task --execute Confirm that the error " Cannot find the BigBlueButton activity " with debugging trace does not appear in the logs.

    Description

      When we delete a BBB activity, Moodle sends an end_meeting request. BBB returns the error message below:

      Execute adhoc task: core_course\task\course_delete_modules
      ... started 21:12:25. Current memory use 8.6 MB.
      ++ Entity not found : {"meetingid":"cc2c3d38a0c0f6ef512503173d32dc5bf168ab73-2-1[0]","xmlmessage":"We could not find a meeting with that meeting ID - perhaps the meeting is not yet running?"}. ++
      * line 466 of /mod/bigbluebuttonbn/classes/local/proxy/bigbluebutton_proxy.php: call to mod_bigbluebuttonbn\local\proxy\proxy_base::assert_returned_xml()
      * line 187 of /mod/bigbluebuttonbn/classes/meeting.php: call to mod_bigbluebuttonbn\local\proxy\bigbluebutton_proxy::end_meeting()
      * line 161 of /mod/bigbluebuttonbn/lib.php: call to mod_bigbluebuttonbn\meeting->end_meeting()
      * line 900 of /course/lib.php: call to bigbluebuttonbn_delete_instance()
      * line 66 of /course/classes/task/course_delete_modules.php: call to course_delete_module()
      * line 341 of /lib/cronlib.php: call to core_course\task\course_delete_modules->execute()
      * line 198 of /lib/cronlib.php: call to cron_run_inner_adhoc_task()
      * line 76 of /lib/cronlib.php: call to cron_run_adhoc_tasks()
      * line 81 of /admin/cron.php: call to cron_run()
      ... used 255 dbqueries
      ... used 0.77006506919861 seconds
      Adhoc task complete: core_course\task\course_delete_modules

      This could lead to false positives as this error message is displayed because the meeting does not exist at the time of activity deletion.

       

      The error appears the same in moosh when performing the category-delete command

      STEPS TO REPRODUCE:

      1. Login as admin
      2. Create BBB activity
      3. Delete the activity
      4. Run cron.

      A possible workaround would be to not use the activity at all, but we would need to change logic.

       

       

      Attachments

        1. MDL-74558_master.png
          67 kB
          Angelia Dela Cruz
        2. MDL-74558_v400.png
          38 kB
          Angelia Dela Cruz

        Issue Links

          Activity

            People

              shamiso.jaravaza Shamiso Jaravaza
              shamiso.jaravaza Shamiso Jaravaza
              Laurent DAVID Laurent DAVID
              Jun Pataleta Jun Pataleta
              Angelia Dela Cruz Angelia Dela Cruz
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 46 minutes
                  46m

                  Clockify

                    Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.