error 500 on archival description dates

[audeale...@gmail.com]

Good morning,

I am testing AtoM 2.5.3 and get an error 500 message on creating an archival description with Begin date and End date in the form : YYYY - YYYY. See the printscreen (in attached file).

However, when I adapt the dates (Begin and End) in the form: YYYY-MM-DD, then it works fine.

In earlier AtoM versions (in production: 2.4), there was no similar issue. Could it have something to do with the installation (some module missing, for ex.) or the configuration? Otherwise, everything works fine on this new installation, including the jobs.

I searched the list to find a message about a similar issue but without results.

Thanks for your help.

Best wishes,

Aude

[Dan Gillean]

Hi Aude, 

AtoM 2.5 upgrades MySQL from version 5.6 to 5.7, and in MySQL 5.7 some of the default SQL modes have changed. We have found that upgrading users often overlook these changes when installing the new version, and my first suspicion is that you may have the wrong SQL modes enabled, leading to the error. 

The most likely cause of the issue is the STRICT_TRANS_TABLES mode, whichI believe is enabled by default in 5.7 and later. In the "Create the database" section of the installation docs for 2.5, we recommend setting different default SQL modes and NOT using this mode. See the bottom half of this section:

• https://www.accesstomemory.org/en/docs/2.5/admin-manual/installation/linux/ubuntu-bionic/#create-the-database

If you want to check or change the SQL modes of an installation, the following page might help:

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/common-atom-queries/#check-server-sql-modes

Remember to restart MySQL after making changes:

• sudo systemctl restart mysql

You may also want to clear your cache and restart PHP-FPM before re-testing as well: 

• Clear cache: https://www.accesstomemory.org/docs/2.5/admin-manual/maintenance/clear-cache/
  
• Restart PHP-FPM depends on the version of PHP you have installed. 
• PHP 7.0: sudo systemctl restart php7.0-fpm
• PHP 7.2: sudo systemctl restart php7.2-fpm

Let us know if this helps! 

If not, then we recommend taking a look at the webserver error logs to get more information about the cause of the error. Some tips on how to do that can be found here: 

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/logging/#maintenance-webserver
  

Feel free to share what you find. 

One last possibility is 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

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/d53bdd5a-8d04-42d9-9930-07f9c9a4e57bn%40googlegroups.com.

[audeale...@gmail.com]

Hi Dan,

Thanks a lot for your help and the detailed answer. I forwarded it to the IT department and will let you know how it goes.

Best regards,

Aude