Hanging recording after server crash

OpenVidu Meet
1

After a server crash (not caused by OpenVidu Meet) during a recording session, the recording is hanging in status active and cannot be saved or removed via the GUI:

image
image1230Ă—153 15.6 KB

Is there a way to terminate a recording and save or remove it (CLI) ?

Another question: Will there come upgrades to OpenVidu Meet in the future? And if, how will the upgrade procedure be?

Thank you

/ Harald

2

Hello @hvillemoes ,

Find my answers bellow:

Is there a way to terminate a recording and save or remove it (CLI) ?

OpenVidu Meet periodically processes recordings (by default, every 15 minutes) to detect those that have become stale after a server crash.
If a recording shows no updates for a certain period (by default, 5 minutes) and is not associated with any active meeting, it will be classified as a Recording Stale and its status will be marked as aborted, making it eligible for deletion.

By default, this process runs automatically and requires no manual intervention.

Will there come upgrades to OpenVidu Meet in the future? And if, how will the upgrade procedure be?

Of course, OpenViduMeet will continue to receive regular updates in the future alongside new OpenVidu releases. The upgrade process will be thoroughly documented in our official documentation to ensure that moving from one version to another is clear and straightforward.

You can subscribe to our newsletter or follow our Medium blog to stay informed about all our release announcements, including what’s new and updated in each version.

Best regards
Carlos Santos

3

Thank you for your reply.

Unfortunately my OpenVidu Meet does not work as described for hanging recordings, as shown on the picture on my initial message. This recording seems to stay in state recording forever > one week.
The history is, that the OpenVidu Meet server for external reasons broke down in the middle of a recording after app. 25 minutes.

Is there a way to go “behind the curtains” and change the state in order to retreve or delete the partial recording?

Thank you / Harald

4

Hi @hvillemoes ,

We are sorry for the unusual behavior you experienced, and we will investigate it to ensure it does not happen again.

Below is the updated guide, specific to version 3.4.0, and including all credential sources.

How to delete the recording from MinIO (S3) — Version 3.4.0

The MinIO console is always available at:

https://<your-domain>/minio-console

1. Access the MinIO Console

  1. Go to:
    https://<your-domain>/minio-console

  2. Log in with:

    • Username: minioadmin

    • Password: depends on your deployment method:

      • Local Deployment
      Password is: minioadmin

      • AWS Deployment
      Retrieve the password from AWS Secrets Manager:

      • Open AWS Console → Secrets Manager
      • Search for the secret associated with your AWS deployment
      • Copy the MinIO admin password
        See OpenVidu docs Reference link

      • On-premises Deployment
      Password is stored in: /opt/openvidu/config/openvidu.env

2. Locate the Recording

Recordings for OpenVidu Meet 3.4.0 are stored at:

openvidu-appdata/openvidu-meet/recordings

Inside this directory, each recording has its own folder named after its session or recording ID.

3. Delete the Stuck Recording

  1. In MinIO, open the openvidu-appdata bucket.
  2. Enter openvidu-meet.
  3. Open the recordings folder.
  4. Find the folder corresponding to the problematic recording.
  5. Select it and choose Delete.
  6. Confirm the deletion.
1 Like
5

Thank you so much for taking the time to generate this very usable reply.