ERROR 500 INTERNAL SERVER ERROR

[Gonzalo Granara]

Hola, soy principiante en ATOM y tengo un problema que no logro resolver.

Migré un conjunto de fondos de un CVS y no me permite editarlos, publicarlos ni realizar otras acciones. Cada vez que lo intente, aparece el siguiente error:

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

Agradezco mucho que alguien me pueda orientar.

Saludos, Gonzalo

[Dan Gillean]

Hola Gonzalo, 

Our Troubleshooting documentation page should provide you with some options. See: 

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/
  

Any time you encounter a 500 error, the first thing we generally recommend is to check the webserver error logs for more information. 

If you have followed our recommended installation instructions, you will find information on how to access these here: 

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

Feel free to share any message you find there so we can provide further suggestions. You can also try searching the error message in the AtoM User Forum to see if you can find older threads with suggestions related to the error. 

In general, it's important to make sure that a CSV import matches AtoM's expectations. You can see instructions for preparing Archival Description CSV imports in our documentation, and in the following slides: 

• Docs: https://www.accesstomemory.org/docs/latest/user-manual/import-export/csv-import/
• Slides: https://www.slideshare.net/accesstomemory/csv-import-in-atom

If your descriptions look like they imported correctly, but you are still experiencing these errors, then it's possible the CSV was well-formatted, but the process timed out before completing, leaving some internal data missing or corrupted. This can sometimes happen when performing large CSV imports via the user interface, for example. 

Sometimes, running some of the common command-line maintenance tasks can help resolve these issues. In particular, I would suggest: 

• Rebuild the nested set
• Generate slugs
• Populate the search index
• Clear the application cache
• Restart PHP-FPM

All of these commands are run using the command-line interface, from AtoM's root installation directory - if you've followed our recommended installation instructions, this is typically /usr/share/nginx/atom. You will find further links and instructions for each task on the Troubleshooting page.

If that STILL doesn't work, then my final suggestion would be to check for data corruption, such as missing Object IDs in the database. Once again, we have some suggestions on where to start in the Troubleshooting docs: 

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/#dealing-with-data-corruption
  

Good luck! Let us know how it goes!

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/04157566-ef8c-477a-8191-349378ee9e3cn%40googlegroups.com.