--
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.
Hello everyone,
as Matthias already wrote, we have quite a lot of empty entries in our Admin – UI.
Our System:
We are currently running OC 11.8 and updated in September from OC 8.5.
We have 3 Server: admin – node, worker – node and a presentation node.
Our Problem:
These videos can be viewed with the paella player without problems.
Even the Metadata gets displayed inside the paella player.
But if you want to do anything to these videos except watching them, these entries do not work in any way, shape or form.
(Standalone Video Editor):
This is a big Problem for us, as we want to enable our lecturers to edit their videos by themselves.
But currently videos with empty entries in the admin – ui, cannot be edited at all.
We tested a lot of these videos and with all of them, only the preview video and the video title can be loaded.
Everything else will not be loaded (video – waveform, video – length, smil catalogue, metadata,…).
As the metadata fields inside the standalone video editor are empty, we tried to change the metadata and publish the video with the new information. After this we receive a 500 (Server Error).
ERROR:
POST https://<admin-node>/editor/a21a169f-7f21-4562-9a5d-ee1d6fda62fd/metadata.json 500 (Server Error)
This error does not leave an entry in our worker – log or in our admin – log, but does leave a warning in our presentation – node (see attachment).
2022-11-07T09:10:07,715 | WARN | (WebApplicationExceptionMapper:73) - javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
(Admin – UI):
In addition to the standalone video editor, changing information inside the admin – ui does not work either.
Neither Metadata changes, nor changes to the ACL can be applied, although we receive the “metadata saved” message.
But if we close the video details window and open it again, all changes are lost.
Republishing or deleting these videos does not work (“republish metadata”, “publish” and “delete” workflow).
As this is our production system, I cannot simply take one of these videos and run tests, but the one video that I could run some tests on, Opencast wrote an ERROR into the log:
2022-10-26T14:06:44,892 | ERROR | (DublinCoreUtil:100) - Unable to load metadata from catalogue 'https://<admin-node>/assets/assets/eccad833-b6ec-4007-bb54-45a999a82f5f/d759521b-c413-407f-a855-0230ac5b686b/6/dublincore.xml'
But I cannot be sure if this error is the real culprit, as the video was processed by a lecturer, and I only go this error after the "publish" workflow was started… (the whole error – log can be found in the attachments), and I cannot even be sure how the database entry of this video was looking like, as I cannot access this video anymore.
The only operation that does work is to retract a video (“retract” – workflow).
Further Investigation:
(Database):
These videos (with empty entries in the admin – ui) have a corresponding entry inside our database.
While these videos contain a similar number of mediapackage.xml files (compared to videos that used the same workflow, belong to the same series and come from the same source), these mediapackage.xml files themselves are shorter.
After checking these mefdiapackage.xml files, I found that they contain all the needed metadata for these videos.
It seems like the database should not be our problem.
(File System):
Because of this I continued with our filesystem.
As far as I
can tell, the video files are located in 4 directories:
/mh_default_org/api
/mh_default_org/engage-player
/mh_default_org/internal
/mh_default_org/oaipmh-default
These directories contain subdirectories, each with their own associated file.
(These subdirectories get saved in some mediapackage.xml for reference).
We found that /api, /engage-player and /oaipmh-default contain at least one doublincore.xml file.
But /internal is missing this doublincore.xml file.
Currently we are suspecting that this is the reason for these empty admin – ui entries as I suspect /internal may correlate to the admin – ui.
Our questions:
So, we still have the doublincore.xml files with all needed metadata, but we cannot get this data into the admin – ui.
Greg wrote that we would go through these recordings to fix the metadata, but I do not understand how to do this, as the workflows do not work (I could only test this with one video though, as I cannot simply risk disabling a video that may still be used).
Is there another way to change the metadata?
Or is it as simple as copying a directory from e.g. /mh_default_org/api/<uuid> to /mh_default_org/internal/<uuid>?
But these directories will then be missing inside the mediapackage.xml file in our database, and I would suspect this would not work?
Can anyone
help me with this problem?
Take care,
Andreas | TH Deggendorf
We managed
to solve our problem.
So we have about 4000 videos that showed up as empty lines inside the admin-ui.
But the opencast media portal and the paella player could access the metadata, strangely enough neither the Opencast editor, nor the Standalone Editor did work.
If we wanted to run a workflow on one of these videos like “publish” or “republish-metadata” these workflows failed.
In addition, we could not use the api to get any metadata from any of the empty videos with /api/events/<video-id>
We always received
the following error (API, workflows, metadata):
Exception message WorkflowOperationException: org.opencastproject.assetmanager.api.AssetManagerException: An asset with checksum ec2ade4e91e4d277ca4b1988f03a4781 (md5) has already been archived but trying to copy or link asset StoragePath(orgId=mh_default_org, mpId=8ff51d53-a7b3-4b06-bd3b-3a8eb646a886, version=3, mpeId=5a4f80c4-0f65-4d2b-b55a-60617e241711) to it failed
We think this error first occurred during our update from opencast 8.5 to opencast 11.8.
After quite some investigation we concluded that this problem arose from the archive and the stored snapshots.
Let me explain:
Usually, the archive stores all snapshots that are created for one video.
As we had a very “custom” workflow sometimes these snapshots contain 6 video files. In addition, we saw that these snapshots were sometimes not referencing other snapshots, as some video files were edited.
In addition to that, many videos were in some way, shape or form changed and stored upwards of 10 snapshots.
Because of this we use an asset-delete workflow operation, to reduce our snapshots.
So, after updating opencast the index rebuild did not find the archive snapshot. Although the archive stored a snapshots, the rebuild somehow always searched for the wrong snapshot number.
(if the snapshot was named “4” the index rebuild looked for snapshot “3”)
This is due to the database, where the wrong snapshot is stored.
As we delete previous snapshots, this snapshot cannot be found.
And this produced our empty lines inside the admin – ui.
As these videos were published though, the media portal and the paella player could access the dublincore.xml and extract the metadata.
Our
solution:
Inside the Archive we rename the snapshot (“4” gets renamed to “3”).
After this we republish (“publish” workflow) the video. If you just want to have the metadata back, the “republish-metadata” workflow is insufficient, as the “publish” workflow pulls the video files back into the archives and rewrites the manifest.xml files.
So, with the “publish” workflow everything inside the admin – ui is fine, the publications work and the assets are mapped correct.