HTTP ERROR 500 - first time installation

Omeka S Installing
1

First time installation:

Centos/RHEL 7
MySQL v 7.3
Apache v 2.4.37
PHP v 7.2

I’ve configured the database.ini
I installed Omeka in the folder /var/www/html

The error log shows this:

172.24.6.1 - - [21/Jan/2020:10:45:07 -0500] “GET /favicon.ico HTTP/1.1” 404 209
“http://crescent.sjcme.edu/” “Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebK
it/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36”
172.24.6.1 - - [21/Jan/2020:10:45:14 -0500] “GET /omeka/admin HTTP/1.1” 302 - "-
" “Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Geck
o) Chrome/79.0.3945.130 Safari/537.36”
172.24.6.1 - - [21/Jan/2020:10:45:14 -0500] “GET /omeka/install HTTP/1.1” 500 -
“-” “Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Ge
cko) Chrome/79.0.3945.130 Safari/537.36”

What else could be wrong?

2

That log you posted looks like it’s actually the Apache access log, not the error log.

What are you seeing on the install page? An “Internal Server Error,” an “Omeka has encountered an error”, or something else?

3

I am seeing the message:

This page isn’t working.
crescent.sjcme.edu is currently unable to handle this request
HTTP ERROR 500

I know apache is working in general. It is able to serve up a simple page.

4

When I go to my site: http://crescent.sjcme.edu/omeka , it does redirect me to the install URL :
http://crescent.sjcme.edu/omeka/install

That’s when I get the error.

5

Okay, that sounds like something that should have more information in your Apache error log. Can you try to check that? Again, the prior log looks like it was the access log, while the error log is usually in more or less the same place with a slightly different name.

6

The error_log is not telling me much. I tried altering the httpd.conf file to change loglevel to debug, but it does not seem to have had any effect.

7

You’re certain it’s the error log you’re looking at?

The lines you posted, those structured lines starting with IP addresses, are definitely access log lines, while the error log should be more text-based, sentences or phrases. If you’re sure you’re looking at the error log, is it showing just nothing? Typically a 500 error will result in something being logged to Apache’s error log.

8

Looks like I finally got something:

[Tue Jan 21 16:41:57.521419 2020] [authz_core:debug] [pid 4476:tid 139787965036288] mod_authz_core.c(820): [client 172.24.6.1:53938] AH01626: authorization result of Require all granted: granted
[Tue Jan 21 16:41:57.521455 2020] [authz_core:debug] [pid 4476:tid 139787965036288] mod_authz_core.c(820): [client 172.24.6.1:53938] AH01626: authorization result of : granted
[Tue Jan 21 16:41:57.521547 2020] [authz_core:debug] [pid 4476:tid 139787965036288] mod_authz_core.c(820): [client 172.24.6.1:53938] AH01626: authorization result of Require all granted: granted
[Tue Jan 21 16:41:57.521553 2020] [authz_core:debug] [pid 4476:tid 139787965036288] mod_authz_core.c(820): [client 172.24.6.1:53938] AH01626: authorization result of : granted
[Tue Jan 21 16:41:57.521585 2020] [proxy:debug] [pid 4476:tid 139787965036288] mod_proxy.c(1254): [client 172.24.6.1:53938] AH01143: Running scheme unix handler (attempt 0)
[Tue Jan 21 16:41:57.521595 2020] [proxy_ajp:debug] [pid 4476:tid 139787965036288] mod_proxy_ajp.c(743): [client 172.24.6.1:53938] AH00894: declining URL fcgi://localhost/var/www/html/omeka/index.php
[Tue Jan 21 16:41:57.521602 2020] [proxy_fcgi:debug] [pid 4476:tid 139787965036288] mod_proxy_fcgi.c(1021): [client 172.24.6.1:53938] AH01076: url: fcgi://localhost/var/www/html/omeka/index.php proxyname: (null) proxyport: 0
[Tue Jan 21 16:41:57.521605 2020] [proxy_fcgi:debug] [pid 4476:tid 139787965036288] mod_proxy_fcgi.c(1028): [client 172.24.6.1:53938] AH01078: serving URL fcgi://localhost/var/www/html/omeka/index.php
[Tue Jan 21 16:41:57.521613 2020] [proxy:debug] [pid 4476:tid 139787965036288] proxy_util.c(2315): AH00942: FCGI: has acquired connection for ()
[Tue Jan 21 16:41:57.521619 2020] [proxy:debug] [pid 4476:tid 139787965036288] proxy_util.c(2368): [client 172.24.6.1:53938] AH00944: connecting fcgi://localhost/var/www/html/omeka/index.php to localhost:8000
[Tue Jan 21 16:41:57.521622 2020] [proxy:debug] [pid 4476:tid 139787965036288] proxy_util.c(2405): [client 172.24.6.1:53938] AH02545: fcgi: has determined UDS as /run/php-fpm/www.sock
[Tue Jan 21 16:41:57.521727 2020] [proxy:debug] [pid 4476:tid 139787965036288] proxy_util.c(2577): [client 172.24.6.1:53938] AH00947: connected /var/www/html/omeka/index.php to httpd-UDS:0
[Tue Jan 21 16:41:57.521760 2020] [proxy:debug] [pid 4476:tid 139787965036288] proxy_util.c(2948): AH02823: FCGI: connection established with Unix domain socket /run/php-fpm/www.sock ()
[Tue Jan 21 16:41:57.548439 2020] [proxy:debug] [pid 4476:tid 139787965036288] proxy_util.c(2330): AH00943: FCGI: has released connection for (*)

9

You might want to turn off the “debug” log level you turned on, since all that’s in this latest paste of the logs is very detailed information that doesn’t include the actual error.