500 Internal Server Error

69 views
Skip to first unread message

Innocent Oling

unread,
Oct 16, 2023, 7:08:14 AM10/16/23
to AtoM Users
Hello Dan,

I am experiencing a 500 internal Server Error and I kindly need some assistance.

This is a fresh installation of AtoM 2.7 on Ubuntu 20.04 LTS. I carefully followed the installation on https://www.accesstomemory.org/en/docs/2.7/admin-manual/installation/ubuntu/#installation-ubuntu-serve-php-fpm.

Upon finishing with the installation and getting to start the web interface, I was greeted by this error message "500 Internal Server Error". I quickly rushed to check the server logs and this was present:
2023/10/16 08:57:47 [error] 5267#5267: *47 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 09:09:16 [error] 5267#5267: *51 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 09:25:40 [error] 5267#5267: *55 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 09:25:45 [error] 5267#5267: *55 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 10:28:33 [error] 5267#5267: *60 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 10:28:36 [error] 5267#5267: *60 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 10:43:23 [error] 5267#5267: *65 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 10:43:26 [error] 5267#5267: *65 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 13:45:45 [error] 935#935: *1 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"
2023/10/16 13:45:50 [error] 937#937: *4 FastCGI sent in stderr: "PHP message: No connection information in your runtime configuration file for datasource [propel]" while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php7.4-fpm.atom.sock:", host: "192.168.0.14"

Also, when I checked the status of atom-worker, I saw this error:

atom-worker.service - AtoM worker
     Loaded: loaded (/lib/systemd/system/atom-worker.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Mon 2023-10-16 14:02:09 EAT; 3s ago
    Process: 1475 ExecStart=/usr/bin/php7.4 -d memory_limit=-1 -d error_reporting=E_ALL symfony jobs:worker (code=exited, status=1/FAILURE)
   Main PID: 1475 (code=exited, status=1/FAILURE)

The installation device meets the required specifications outlined in the system requirement section.

I have also tried tweaking the php resource limits to troubleshoot the error in vain.

I will be available should you require additional information from my side and thank you in advance for your support.

Dan Gillean

unread,
Oct 16, 2023, 11:09:53 AM10/16/23
to ica-ato...@googlegroups.com
Hi there, 

For the job scheduler, I suspect that you might need to reset the fail counter first, so you can successfully restart the atom-worker. We have included some automated restart attempts in the worker configuration in case something fails, but to prevent the job scheduler from being caught in an unending loop, these automated restart attempts are limited to 3 tries in a 24-hour period, after which the fail counter must be manually reset. You can do this with: 
  • sudo systemctl reset-failed atom-worker
  • sudo systemctl restart atom-worker
  • sudo systemctl status atom-worker
The first command resets the fail counter; the second restarts the job scheduler's worker, and the third should return the status again, which should be running if all goes well. See: 
For the first issue: 

I found at least one previous forum thread that recommended ensuring you have the file permissions properly set to use the www-data user, and then running any general AtoM Symfony tasks by explicitly specifying that user. You can reset the filesystem permissions with: 
Let's restart PHP-FPM, to ensure we are seeing the latest version of things. For a 2.7.x release using the recommended Ubuntu 20.04 and PHP 7.4, you can do this with: 
  • sudo systemctl restart php7.4-fpm
Now we can specify the www-data user when we run some common maintenance tasks, to see if we can get things working. For example: 
  • Clear the application cache: sudo -u www-data php symfony cc
  • Make sure every record has a slug: sudo -u www-data php symfony propel:generate-slugs
  • Rebuild the nested set: sudo -u www-data php symfony propel:build-nested-set
  • Rebuild the search index:  sudo -u www-data php symfony search:populate
Hopefully that will fix the issue! All of the above commands should have links on our Troubleshooting page: 
If you are still having issues, please let us know a bit more about your installation, such as: 
  • What is the full version number returned when you run: php symfony tools:get-version (or shown in Admin > Settings if you can get there)?
  • Does your installation have any code customizations, including a custom theme plugin, that we should know about?
  • Was this an upgrade - i.e. have you attempted to load a sqldump from another AtoM instance into this installation?
  • Does your system meet the recommended hardware requirements included in our docs, here?
    • Processor: 2 vCPUs @ 2.3GHz
    • Memory: 7GB
    • Disk space (processing): 50GB at a minimum for AtoM’s core stack
  • Can you share the output you get from our search status task? sudo -u www-data php symfony search:status
  • Anything else that would be helpful for us to know?

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/55d6eb1f-deb4-43ae-89fd-a5641300f07fn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages