"Unable to complete file import." v2.4.0

[paclo...@gmail.com]

Hi all -

I am attempting to run AtoM v2.4.0 on CentOS (in a Vagrant VM at the moment). The application installs fine and loads correctly in the browser. However, when I attempt to upload an EAD 2002 XML file via the web UI, I receive the following error message:

Error encountered

Unable to complete file import. File 1100.xml could not be moved to /usr/share/nginx/atom/uploads/tmp

* The file imports correctly from the command line interface using the `import:bulk` task

* I've attempted many permutations of permissions settings, including 777 for both the `uploads` and `uploads/tmp` directories

* The nginx user can write to the directory (`touch` a new file)

* The worker process (and others) are running as the nginx user

* The nginx log indicates that "a client request body is buffered to a temporary file"

I've searched this group and the web at large in vain, so I'm hoping someone might have seen this error before or have some idea of what to investigate next.

Thanks,

Paul

[Dan Gillean]

Hi Paul, 

I could be wrong about the permissions that the job scheduler requires, but in the vagrant box, I believe that the vagrant user is the one who needs the permissions that are normally assigned to the www-data user in a production deployment. You might try the following: 

• sudo chown -R vagrant.vagrant /usr/share/nginx/atom
  

If you don't have data you need to preserve, or if you've backed it up, you can also try destroying and redeploying the vagrant box, to restore it to its original state. In the host system, in the directory where you first launched the vagrant box, try the following to destroy and reload the Vagrant box: 

• vagrant destroy
• vagrant up

A lot of development was done after the initial 2.4 Vagrant box was released, so it could be that making sure the environment is fully up-to-date will help resolve the issue. When it was released, the box tracked our 2.4 development branch (qa/2.4.x). Since 2.4 is now released, this has been changed to stable/2.4.x, so you'll need to checkout that branch before you can run git pull --rebase. I'd also recommend making sure the database is upgraded, services are restarted, etc. You can checkout the correct 2.4 branch like so, from the atom directory: 

• git checkout stable/2.4.x

After that, you can follow the instructions from slides 17 onward in the following deck, to make sure your environment is up to date. 

• https://www.slideshare.net/accesstomemory/atom-and-vagrant-installing-and-configuring-the-atom-vagrant-box-for-local-testing-and-development
  

WARNING: the step that involves running the tools:purge command will delete all data you currently have in the box. Be sure to back up anything you need to keep first. 

Finally, please be aware that we do have a new 2.5 Vagrant box out, which is in an unstable state since we're currently undertaking a lot of development to upgrade Elasticsearch to version 5.x. If you've ended up installing this box by accident, it's possible you are encountering a regression associated with ongoing development. We also released an updated 2.4 vagrant box  (version 2.4.0.1). You might want to make sure you have the correct box running. You can open the vagrantfile (that was created wherever you installed the Vagrant box on your host system) in a text editor, and look for the line that says  config.vm.box_version. If it does not say "2.4.0.1", you can edit the line to change it, then destroy the box and run the vagrant up command again. 

If none of the above helps, let us know, and I'll ask a developer for further suggestions! 

Regards, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/feb1e79f-bd00-4e74-bfce-19792961f88d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.