CSV import error

[Tam Rayan]

Hi, 

For several days now I have been attempting to upload various archival descriptions to AtoM via the CSV import function but keep encountering the same error message:

 Oops! An Error Occurred

Sorry, something went wrong.
The server returned a 500 Internal Server Error.

Try again a little later or ask in the discussion group.
Back to previous page.

I am not sure what is causing the issue. I have used LibreOffice Calc to create the CSVs and they are UTF-8 encoded. I have attached one of the CSVs here for reference.

Any assistance is appreciated.

Thank you,

Tam

[Dan Gillean]

Hi Tam, 

At a glance I don't see anything that pops out as error-causing in your CSV template. 

Any time you encounter a 500 error, the first thing we recommend is for someone to check the webserver logs for more information on the nature of the error. If you have followed our recommended installation instructions, you can check the most recent error log entries with the following command, run from the root installation directory of your AtoM instance (which is typically installed on a server at /usr/share/nginx/atom):

• sudo tail -f /var/log/nginx/error.log

See:

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/logging/#maintenance-webserver
• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/#error-logs-and-debug-mode

Feel free to share any related error message you find here if you're not sure how to proceed, and we will try to offer suggestions on next steps. However, in many cases, this error occurs because the job scheduler needs a restart, so that would be my first guess. You will know this is the case if you look in the error logs and see a message like, "No Gearman worker available that can handle the job."

To restart the atom-worker, see:

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/#restarting-the-job-scheduler
• sudo systemctl restart atom-worker

Some notes on this:

• You can check the status of the atom-worker at any time with: sudo systemctl status atom-worker.This is useful to make sure the restart was successful.
•  When the worker dies, AtoM will attempt to automatically restart it - however, to prevent the system from being caught in an endless loop, we added a restart limit - 3 retries every 24 hours. You can reset this fail limit with the following command:
• sudo systemctl reset-failed atom-worker
• Then run the restart command again if the previous attempts didn't work.

If none of these suggestions help to resolve the issue, and/or this is not what you find in the error logs, then please let us know what you discover, as well as more information about your installation (Operating system, PHP version, etc)  and we can provide further suggestions.

Cheers, 

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

@accesstomemory

he / him

--
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-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/14c02768-b878-41f3-8d81-d518ab809286n%40googlegroups.com.