Deployment: Self-hosted, local VM on VMWARE vSphere
EaaSI Version: 2021.10
Browser: Firefox version 102.0.1 (64-bit)
Description: Attempting to upload content or software results is an “TypeError r is null” message. This occurs with both software and content uploads. Most recently on the upload of an Adobe CS2 two-disk ISO. (~10GB). There is sufficient space on disk for this upload. I’m including a screenshot of the error, a front-end log and backend server.log, and a tail -f of the server.log while the error occurred.
Are you able to reproduce the issue or did it happen once? What steps can you take to repeat the issue? What did you expect to occur and what was the actual outcome? This happens on any content or software upload so may be a general upload issue. We have been uploading similar items the last few weeks without issue. The expected behavior is that the ISO files upload to eaasi and are viewable in the interface.
Urgency:If possible, please give an indication of how urgently the issue needs to be addressed - is there a timeline or deadline (e.g. upcoming demo, researcher request, etc.) that EaaSI support staff should be aware of? We are in the middle of a study with EaaSI, however the study can continue locally if necessary. Would be nice to figure this out this week however, we are finishing the study next week and it would be nice to have this running before work stops.
@ekaltman, it looks like you are running out of disk space sometimes:
2022-07-18 23:06:25.157 |I| (default task-640) [FileSystemBackend] Saving new blob 'user-upload/8aa96126-f759-481c-a82a-3377a8c49f51'...
2022-07-18 23:07:03.369 |W| (default task-640) [FileSystemBackend] Writing blob's data failed!
: java.io.IOException: No space left on device
In the current legacy implementation, all files are temporarily uploaded into an internal blob-store first and are then imported into object-archives from there. All temporary blobs are eventually garbage-collected at some predefined periods, resulting in multiple copies left behind from previous uploads and increased storage consumption in the meantime. We are still experimenting with a more robust and less resource-hungry solution for uploads.
Increasing the disk space does appear to have solved the issue. However, we did have an upload failure after I increased the logical partition size and extended the file system. I think there might have been some lag in EaaSI’s access to the increased storage. Anyway, the issue is fixed, thanks!
