AtoM not loading

[Maritime Museum]

I've been having a problem for the last few days of AtoM not loading at all. 

I've been getting a timeout message and changing my page loading time isn't helping, neither is clearing the cache on my computer. The problem is larger than just my computer since it isn't loading on other computers and the public facing version on our website is doing the same. Does anyone have any ideas? 

Thanks

[Dan Gillean]

Hi there, 

Any time you encounter a 500 or 504 error, the first thing we recommend doing is having a system administrator check the webserver error logs to see if there is more information about the cause of the error. See:

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

Sometimes timeouts are caused  by a lack of system resources - for a production-ready, public-facing installation, we recommend the following as minimum targets in our documentation: 

Processor: 2 vCPUs @ 2.3GHz
Memory: 7GB
Disk space (processing): 50GB at a minimum for AtoM’s core stack plus more storage would be required for supporting any substantial number of digital objects.

See: https://www.accesstomemory.org/docs/latest/admin-manual/installation/requirements/#minimum-hardware-requirements

It may be wise to first see if you can identify where exactly the bottleneck is occurring. Two other methods of gathering information: 

1. You can try a tool like htop to see server resources and active processes in realtime, and look for issues. See: 
• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/#troubleshooting-resources-limits
2. You can potentially see if the browser is able to return more information if you enable Debug mode. See: 
• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/debug/

Finally, if your system has enough resources then for timeout issues your next best bet may be to take a look at the execution limits. These are configured in the PHP pool set up during installation (found at /etc/php/7.4/fpm/pool.d/atom.conf if you followed our recommended installation instructions), and may also be set at the server level, in the general php.ini file on your system. See: 

• https://www.accesstomemory.org/docs/latest/admin-manual/installation/execution-limits/#installation-execution-limits
  

Remember to restart PHP-FPM if you make any changes. 

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/9c49380b-d3ec-4750-adb7-35c7a429786an%40googlegroups.com.