httpd: Could not reliably determine the server's fully qualified domain name

arondas · 11-13-2016, 11:04 AM

Hi Team,

We are currently facing a defect related to missing ssl certificate issues related to our content server which is based on linux and the database is based on SAP Maxdb. However Database server is different and is based on Unix.

So we have got a suggestion from SAP as below. As per their suggestion we have downloaded the latest content server patch and unpacked it and kept it in a separate location.

Now below are the steps which was suggested to follow.

==============================================================================

Installing the patch on Content Server (Linux):

1. Log on to the Unix system as the Content Server Administrator.

2. Unpack the files to a temporary directory.

3. Stop the Apache Web Server with the command "apachectl stop". You will find this command in the directory "bin" of the server installation.

4. For Apache 1.3: Replace the Shared Libraries in the directory "libexec" of your Content Server/Cache Server installation against the files from the ZIP archive.

5. For Apache 2.0 and higher: Replace the Shared Libraries in the directory "modules" of your Content Server/Cache Server installation against the files from the ZIP archive.

6. Check the execution rights of the program files. Some UNIX variants require execution rights to be set for shared libraries. The relevant command is "chmod755 ".

7. Start the Apache Web Server with the command "apachectl start".
=====================================================================================

Now in course of the following the steps above we were supposed to stop the Apache webservice using "apachectl stop"

However immediately after giving the command we are getting the below error message.

httpd: Could not reliably determine the server's fully qualified domain name, using server's fqdn for ServerName httpd (no pid file) not running

As a part of investigation we checked the below location to confirm whether the server name is mentioned there or not. /app/apache/vvzcs/conf/httpd.conf Server name is maintained there.

So can you kindly suggest what can we do in this scenario please ?
It is a long pending defect and needs to be sorted out.

bathory · 11-15-2016, 03:28 AM

Hi and welcome to LQ,

Since you're new here, you should try to give more details so we could help you. Like what is the Linux distribution you're running, the apache version and how it was installed etc.

Quote:

httpd: Could not reliably determine the server's fully qualified domain name, using server's fqdn for ServerName

The above is not an error, but a warning.
To get rid of it use a hostname for the ServerName directive in httpd.conf and make sure that there exist also an entry in /etc/hosts for it:

Code:

httpd.conf:
Servername www.domain.com

/etc/hosts:
1.2.3.4 www.domain.com

Quote:

httpd (no pid file) not running

The above message means that apache is not running. Try to start it and see what you get.
In case of an error, post the relevant part of error_log

Regards

TB0ne · 11-15-2016, 07:42 AM

Quote:

Originally Posted by arondas

Hi Team,
We are currently facing a defect related to missing ssl certificate issues related to our content server which is based on linux and the database is based on SAP Maxdb. However Database server is different and is based on Unix.

So we have got a suggestion from SAP as below. As per their suggestion we have downloaded the latest content server patch and unpacked it and kept it in a separate location. Now below are the steps which was suggested to follow.
==============================================================================
Installing the patch on Content Server (Linux):

1. Log on to the Unix system as the Content Server Administrator.
2. Unpack the files to a temporary directory.
3. Stop the Apache Web Server with the command "apachectl stop". You will find this command in the directory "bin" of the server installation.
4. For Apache 1.3: Replace the Shared Libraries in the directory "libexec" of your Content Server/Cache Server installation against the files from the ZIP archive.
5. For Apache 2.0 and higher: Replace the Shared Libraries in the directory "modules" of your Content Server/Cache Server installation against the files from the ZIP archive.
6. Check the execution rights of the program files. Some UNIX variants require execution rights to be set for shared libraries. The relevant command is "chmod755 ".
7. Start the Apache Web Server with the command "apachectl start".
=====================================================================================

Now in course of the following the steps above we were supposed to stop the Apache webservice using "apachectl stop" However immediately after giving the command we are getting the below error message.

httpd: Could not reliably determine the server's fully qualified domain name, using server's fqdn for ServerName httpd (no pid file) not running

As a part of investigation we checked the below location to confirm whether the server name is mentioned there or not. /app/apache/vvzcs/conf/httpd.conf Server name is maintained there.

So can you kindly suggest what can we do in this scenario please ? It is a long pending defect and needs to be sorted out.

bathory gave some good advice, but I can't help but wonder why (since you're obviously paying for support from your SAP people), you didn't contact them with this error?