Support Notes: Apache configuration support

October 2nd, 2012 by Carl Lambrecht

At times, problems may be encountered when setting up Apache to host PHP pages containing Salience PHP wrapper method call which includes a “HTTP/1.0 500 Internal Server Error” when visiting the PHP page and a corresponding /var/log/httpd/error_log “PHP Fatal error: Call to undefined function…” error message entry.

Figure 1: Visiting PHP page with Salience PHP method calls locally hosted by Apache

Figure 2

Figure 2: 1st error—HTTP/1.0 500 Internal Server Error

Figure 3

Figure 3: 2nd error—"PHP Fatal error: Call to undefined function…" in error_log

This is even after verifying the dynamic extension to the saliencefive.so has been added in the php.ini configuration file loaded by Apache.

Under this circumstance, it is observed that the start, stop, or restart of Apache daemon produces the warning message, “httpd: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName”

Figure 4: httpd start/stop/restart warning

This warning indicates that httpd (Apache daemon) was unable to determine its own name and it may raise no concern since the message informs that Apache would automatically assign a domain name. However, the server needs to know its own name under certain circumstances in order to generate self-referential redirects. This is the main cause for the PHP page hosting problems.

To eliminate the errors, add a fully-qualified ServerName defined in the main httpd configuration file (typically located in /etc/httpd/conf/).

Examples:
SeverName localhost
ServerName 127.0.0.1
ServerName 10.201.2.99 (substitute for actual server IP address)

Figure 5: Adding ServerName entry to httpd.conf

Figure 6: Successfully reaching PHP page

Comments are closed.