Error uploading new files

On dev, there was an error uploading files for new items. I believe the cause is the same as issue #50 (closed) error when importing metadata.

I have a temporary workaround for #50 (closed) but I'm opening this issue in case the cause turns out to be different (I haven't tested uploading new files again yet), and I'd like to know the initial problem and find a more permanent answer/solution.

added Priority label

Workaround of creating a second assetstore for incoming files works; not sure if this will make sense for production.

@vtkeithg FWIW, I was able to upload an item yesterday, although some content types were missing from the dropdown menu (I'll open a separate issue for that).

Thanks, Carrie. I've assigned myself to work on the missing content types issue.

assigned to @vtkeithg

Is this the manual add process? In the sidebar, New > Item, then filling out the fields manually? If so it seemed to work for me, but it is missing the rights step (CC license, etc.).

@pyoung1 Yes, it was the manual add process, but @vtkeithg has updated the content types since then (thank you!). I haven't had any trouble adding CC licenses, although my last submission was a few days ago.

Adding dc.rights and dc.rights.uri is fine for editing an item, but the choice seems to be missing entirely during the submission process.

I'm sorry, I should've explained better. I got the CC license questionnaire at the time of submission, and thus, no need to edit afterwards.

Which collection was that? I'm depositing into the "2017 Advancing the Human Condition Symposium" collection and it's definitely not appearing. The VTechWorks license agreement appears fine, but there's no option that I see for assigning a CC license.

Nevermind, I made a test deposit and a regular deposit in both systems on the same day, and I must've gotten them confused. I just tried depositing a new item in the "Library Publications" collection, and now I don't see it either.

Thanks, I'll create a separate issue and maybe this one can be closed.

Leave this open for now, I think. I turned off the workaround of putting incoming files into a second, local assetstore to allow for troubleshooting. So bitstream uploads (and other features, like metadata import that require uploading of files) are broken for now.

One way to replicate:

• Login as an administrator
• Menu bar on the left side of the page has a plus sign when you’re logged in. click there.
• Choose New->Item
• Pick any collection in the collection chooser that pops up (edited)
• Drag and drop a file into the area at the top of the new item page labeled “Drop files to attach them to the item, or browse”
• On the top right corner of the web page a message will pop up for a few seconds that says “Upload failed” Errors appear in dspace.log

Soumik was able to find a fix for this by adding the path to the NFS mounted assetstore as an additional ReadWritePath in the Tomcat configuration. It seems like Tomcat security didn't allow follow of symlinks in this case, because there was already an entry for the "/dspace" directories.

The actual fix will be in our Ansible project.

Unfortunately, I can't remember what was different about our initial setup that allowed uploads to the primary assetstore without this additional entry.

@pyoung1 this looks like it is working. Please review so I can close the card.

Looks OK to me, thanks.

closed