500 Internal Server Error when adding “Dates of existence” in Authority Record

[Pembelani Netshifhefhe]

Hello,

We are experiencing a 500 Internal Server Error in Access to Memory when editing an Authority Record.

The error occurs specifically when attempting to add “Dates of existence” within the Description area and saving the record. The issue is reproducible and happens consistently when this field is populated.

Has anyone encountered a similar issue, or are there known issues related to this field?

Any assistance would be greatly appreciated.

Thank you.

[Johan Pieterse]

Hi

Try entering a full real date if you did not.

Also you can look at the log for the error

/usr/share/nginx/error.log

Johan Pieterse
082 337-1406

--
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 visit https://groups.google.com/d/msgid/ica-atom-users/7db0a5f3-ee80-4f40-b258-4eb747d37c1fn%40googlegroups.com.

[Dan Gillean]

Hi there, 

As Johan suggests, whenever you encounter a 500 error, the first step is to gather more information. You can start by checking the webserver error logs. 

For a general guide on 500 errors and resolving commonly reported issues, see this thread: 

• https://groups.google.com/g/ica-atom-users/c/wVrhL-TAaDY/m/Isu3jUY-AAAJ

That thread has many initial suggestions for common issues. Based on your initial description, this sounds like an unusual issue, suggesting two possibilities to me. 

The first possibility is a database schema mismatch - meaning that your version of AtoM and the current database configuration do not match. This can happen if a step in the upgrade process is accidentally skipped. See the "problems following an upgrade section" in the linked thread for some initial suggestions. 

The second possibility is data corruption. This can happen when long-running processes (like imports, move operations, uploads, etc) are interrupted mid-process and partial rows are left in the database, which can lead to all sorts of unexpected issues. See the "data corruption" section of the previous thread for further information, including a link to a command-line task that checks for (and attempts to fix) common forms of data corruption. 

Finally, if the logs don't cover what you find, try searching the error message in the user forum—someone has likely reported a similar issue before, and you may find old threads with additional suggestions. 

Cheers, 

Dan Gillean, MAS, MLIS

Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

he / him

To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/CAA4s_cAhUb8Cvbi7tmd6zP80rkgQOM79JO1cov3atSCnNM%2B2YQ%40mail.gmail.com.