NO PUEDO EDITAR, SE CUELGA EL SERVIDOR

[Lourdes Fernández Ruiz]

Buenas tardes:

Cada vez que intento editar una descripción archivística o una Institución archivística sale el siguiente mensaje: 500 Internal Server Error.

   ¿Podría orientarme alguien?

    Muchas gracias.

       Lourdes

[Dan Gillean]

Hola Lourdes, 

Whenever you encounter a 500 error, we recommend that someone looks at the webserver error logs to learn more information about the problem. 

If you have followed our recommended installation instructions, you can check the most recent error log entries with: 

• 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.

My guess is that the job scheduler needs a restart - this is often the cause of unexplained errors when trying to edit descriptions. The details for installing the job scheduler (Gearman) can be found here: 

• https://www.accesstomemory.org/docs/latest/admin-manual/installation/asynchronous-jobs/

If you have already installed and configured Gearman, then it's possible that the job scheduler simply needs a restart. 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/a181aac1-b280-468f-b2ca-f73866ff0abcn%40googlegroups.com.