1

THIS QUESTION SHOULD BE MARKED AS CLOSED

I've recently compiled MapServer 6.2 on a CentOS 6.3 machine, using

./configure --with-ogr=/usr/bin/gdal-config --with-gdal=/usr/bin/gdal-config --with-proj=/usr --with-geos=/usr/bin/geos-config --with-postgis=/usr/bin/pg_config --with-php=/usr/include/php --with-wfs --with-wfsclient --with-wmsclient --enable-debug --with-threads --with-wcs --with-sos --with-gd --with-freetype=/usr/bin --with-jpeg --with-cairo --with-curl

if that is of interest, anyway.

So after that, Apache/2.2.15 silently fails to restart, i.e. when apachectl graceful, it says "httpd not running, trying to start". There is nothing of interest in the Apache errors_log, /var/log/messages, and it is weird because so far it has always worked.

Restarting the machine multiple times did not solve the problem. Some other stuff I did:

[root@R12X0210 cgi-bin]# service httpd status
httpd is stopped
[root@R12X0210 cgi-bin]# ps aux|grep httpd
root      1846  0.0  0.0 103236   864 pts/0    S+   12:11   0:00 grep httpd

I suspect this might have something to do with a php module that was altered/added by MapServer, but I don't really know... I don't even know how to properly debug this.

EDIT: Alright, /var/log/httpd/error_log is not necessarily empty, it rather shows those two things after doing /sbin/service/httpd start

[Wed Dec 19 17:33:24 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Dec 19 17:33:24 2012] [error] Server should be SSL-aware but has no certificate configured [Hint: SSLCertificateFile] ((null):0)

Does the SSL error result in the termination of the start mechanism? The thing is we have a unsigned certificate running, i.e. we're testing https Access but not yet in production mode. Absolutely nothing has been changed in the SSL configuration of Apache before it stopped working.

EDIT2: In the meantime, I reinstalled httpd with yum reinstall httpd, this did not solve the problem, either.

grssnbchr
  • 157
  • 2
  • 8

1 Answers1

1

If PostgreSQL is running on the same machine make sure it is listening on 0.0.0.0 or on 127.0.0.1, or on :: on port 5432. To check this, the following command should return something:

sudo netstat -tlnp|egrep ':5432'

If you have PostgreSQL running on a different machine, check that the hosts file is configured correctly and that the proper host is used in the PostgreSQL configuration of your PHP application