FWIW, we have not seen the "capture agent thinks ingest fails, but the
server says all is well" issue locally. This issue has only come up
during testing when a UC Berkeley capture agent is connected to a USask
server.
Kevin Chan
Operations Team
Educational Technology Services
University of California, Berkeley
On 9/14/2012 9:14 AM, Greg Logan wrote:
On 12-09-14 12:52 AM, Tobias Wunden wrote:
Basically workspace/collection has 11G in it and files/collection has 42m in
it. They are not duplicates of each other. Pretty much all of the extra space
in workspace/collection is in ingest-temp.
Ok, that may have something to do with failed ingests, where the ingest is not
cleand up if the connection breaks. Do the files have a checksum file next to
it (may be hidden)? Once the file has been written to the workspace, the
checksum is created as well as the hard link to the working file repository. If
ingests fails to write the file, it should definitely be removed from the
workspace.
Jonathan, Berkeley ran into an issue (talk to Kevin) when testing
against USask infrastructure where the ingest would fail, repeatedly,
and fill up the ingest with broken zip files. We never did find out
what was causing it, so we just assumed that it was a connection issue
between Berkeley and USask. If you're seeing the same issue then
perhaps it's more of an artifact of your network?
My two cents, and maybe not terribly relevant without paying deep
attention to the rest of the thread,
G
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
