Ah00558 apache2 ошибка

14 Dec, 21


by Antoniy Yushkevych



1 min Read

Trying to fix Apache error AH00558? We can help you with it.

Apache shows this message when it couldn’t find the server name.

At Bobcares, we often get requests regarding Apache errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix Apache error for our customers.

When does this Apache error AH00558 occur?

This error message appears mainly when:

• Stopping an Apache service
• We start an Apache service
• We restart an Apache service

But, why this appears is the main question. Today, let’s discuss in detail on Apache error AH00558 and see how our Support Engineers find the fix for this warning message.

How we fix Apache error AH00558?

Recently, one of our customers approached us saying that he is getting a warning error message like the one shown below when he is trying to restart the Apache service.

So, we checked in detail and found that there was no  “ServerName” directive added in the configuration file. That’s why Apache complained about this error message.

So, we added the following in ‘/etc/apache2/apache2.conf’ file.

ServerName FQDN

Here, FQDN is the Fully Qualified Domain Name. Usually, this will be something like srv.domain.com which correctly resolves to an IP address.
Finally, we restarted the service using ‘service apache2 restart‘. This removed the Apache AH00558 warning.

Note: The  ServerName directive can either be an IP-address, or fully qualified domain name, or hostname, depending on the way we are planning to set up Apache.

Also, we handled a situation where the customers approached us with the same Apache warning message, but he said that he needs to run Apache for internal testing purposes only.

So, we set the ServerName directive to the IP-address of his server and restarted the service. Finally, Apache restarted without the error AH00558.

ServerName IP Address 

[Need any assistance with Apache errors? – We’ll help you]

Conclusion

In short, this error message can be avoided by adding the ServerName directive in the Apache configuration file. Today, we discussed in detail how our Support Engineers fix this warning message.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

In this article, we will look into the steps required to solve  «AH00558: httpd: Could not reliably determine the server’s fully qualified domain name,» error. the Recently I was working to bring up my Apache web server to host my PHP Applications on Port 443 but while bringing up the service I noticed «AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using localhost.localdomain. Set the ‘ServerName’ directive globally to suppress this message» error on the output. So I thought to put all the troubleshooting steps in an article so that it will help you guys also if you are facing the same issue.

Also Read: Dynamic Memory Allocations with malloc(), calloc(), free() and realloc() functions in C

Step 1: Check the httpd Service Status

After setting up my Apache web Server when I restarted the httpd service using service httpd restart command then I saw that the httpd.service is failing with below error message.

[root@localhost private]# service httpd restart
Redirecting to /bin/systemctl restart httpd.service
Job for httpd.service failed because the control process exited with error code.See "systemctl status httpd.service" and "journalctl -xe" for details.

I tried to check the complete error message on the output by checking the httpd service status using service httpd status -l command as shown below.

[root@localhost ~]# service httpd status -l
Redirecting to /bin/systemctl status -l httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2020-10-14 06:06:41 EDT; 44s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 6576 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 6576 (code=exited, status=1/FAILURE)

Oct 14 06:06:40 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
Oct 14 06:06:41 localhost.localdomain httpd[6576]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message
Oct 14 06:06:41 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 14 06:06:41 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
Oct 14 06:06:41 localhost.localdomain systemd[1]: Unit httpd.service entered failed state.
Oct 14 06:06:41 localhost.localdomain systemd[1]: httpd.service failed.

Step 2: Check journalctl Logs

If you want to check more about the error then you can look for journalctl logs using journalctl -xe command as shown below. You can check 32 Best journalctl command examples in Linux(Redhat/CentOS) Part-1 and 32 Best journal command examples in Linux(RedHat/CentOS) Part — 2 to know more about journalctl.

[root@localhost ~]# journalctl -xe
Oct 14 05:55:08 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 14 05:55:08 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Oct 14 06:06:41 localhost.localdomain httpd[6576]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. S
Oct 14 06:06:41 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 14 06:06:41 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.

Step 3: Check /etc/hosts file

Error is basically talking about using fully qualified domain name so if you are running any local web server then you can first look into the /etc/hosts file and check the mapping of FQDN to IP Address is correct or not. If the Server hostname is published through DNS Server then you need not to verify from this file and you should go ahead with the next steps.

[root@localhost ~]# vi /etc/hosts

Step 4: Check Apache configuration using apachectl

You can also verify the apache configuration by using apachectl configtest command as shown below. This will tell you about any Syntax error or any other error configuration file currently has. In my case it shows the "AH00558: httpd: Could not reliably determine the server's fully qualified domain name" error which means it has some issue.

[root@localhost ~]# apachectl configtest
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message
Syntax OK

Step 5: Check Apache ssl.conf configuration file

Next step is to check the apache ssl.conf configuration file. Here you need to check the ServerName directive and verify that Server Name is correct here. Since the error talks about using Global ServerName directive so you can try to provide the ServerName at the end of the file i.e outside any VirtualHost directive as you can see below.

[root@localhost ~]# vi /etc/httpd/config.d/ssl.conf
Add ServerName at the end of ssl.conf
BrowserMatch "MSIE [2-5]" 
nokeepalive ssl-unclean-shutdown 
downgrade-1.0 force-response-1.0

# Per-Server Logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log 
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x "%r" %b"

</VirtualHost>
ServerName test.cyberithub.com:443

Step 6: Check SELinux Policy

Then you also need to check the SELinux configuration by using sestatus command. There is a chance that SELinux rule might block the apache service. In our case, currently it is set to enforcing mode so I would like to change the Current mode from Enforcing to Permissive and then check once. If you don’t need SELinux, then you can disable it as well.

[root@localhost ~]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31

We can temporaily disable the SELinux by using setenforce 0 command as shown below and then if we again check the SELinux status using sestatus command then we can see it has now changed to Permissive mode.

[root@localhost ~]# setenforce 0
[root@localhost ~]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31

Step 7: Check Firewall Rules

If you are running any firewall in your Server then you need to allow the Port 443 through firewall. More on service command Man Page.

[root@localhost ~]# service firewalld status
Redirecting to /bin/systemctl status firewalld.service
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-10-14 04:17:20 EDT; 2h 9min ago
Docs: man:firewalld(1)
Main PID: 15329 (firewalld)
CGroup: /system.slice/firewalld.service
└─15329 /usr/bin/python2 -Es /usr/sbin/firewalld --nofork --nopid

Oct 14 04:17:19 localhost.localdomain systemd[1]: Stopped firewalld - dynamic firewall daemon.
Oct 14 04:17:19 localhost.localdomain systemd[1]: Starting firewalld - dynamic firewall daemon...
Oct 14 04:17:20 localhost.localdomain systemd[1]: Started firewalld - dynamic firewall daemon.
Oct 14 04:17:20 localhost.localdomain firewalld[15329]: WARNING: AllowZoneDrifting is enabled. This is considered an insecure configuration option. It will ...g it now.
Hint: Some lines were ellipsized, use -l to show in full.

You can allow https service through firewall using firewall-cmd —zone=public —add-service=https command as shown below. You can check 26 Useful firewall CMD Examples on RedHat/CentOS 7 to know more about firewall-cmd command.

[root@localhost ~]# firewall-cmd --zone=public --add-service=https

Step 8: Check IPTABLES Rules

If you are running IPTABLES in your Server then you need to allow Port 443 from that as well using below iptables command. You can check 30 Most Popular IPTABLES command in Linux to know more about iptables.

[root@localhost ~]# iptables -A INPUT -p tcp --dport 443 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT
[root@localhost ~]# iptables -A OUTPUT -p tcp --sport 443 -m conntrack --ctstate ESTABLISHED -j ACCEPT

Step 9: Restart httpd service and Check the Status

Now we can again try to restart the httpd service using service httpd restart command and check if this helps.

[root@localhost ~]# service httpd restart
Redirecting to /bin/systemctl restart httpd.service

This time we do not see any error on the output, so let’s check the httpd service status again by using service httpd status command. Here we can see that service is now started successfully without any error.

[root@localhost ~]# service httpd status
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2020-10-14 06:29:14 EDT; 8s ago
Docs: man:httpd(8)
man:apachectl(8)
Main PID: 6902 (httpd)
Status: "Processing requests..."
CGroup: /system.slice/httpd.service
├─6902 /usr/sbin/httpd -DFOREGROUND
├─6903 /usr/sbin/httpd -DFOREGROUND
├─6904 /usr/sbin/httpd -DFOREGROUND
├─6905 /usr/sbin/httpd -DFOREGROUND
├─6906 /usr/sbin/httpd -DFOREGROUND
└─6907 /usr/sbin/httpd -DFOREGROUND

Oct 14 06:29:14 localhost.localdomain systemd[1]: Starting The Apache HTTP Server...
Oct 14 06:29:14 localhost.localdomain systemd[1]: Started The Apache HTTP Server.

Hopefully you found this article useful in resolving "AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message" error.

Popular Recommendations:-

How to Install PHP on RedHat/CentOS 7 with Easy Steps

Useful C Program to List Network Interfaces using only 30 Lines of Code

Best Explanation of Wrapper Classes in Java: Autoboxing and Unboxing with Examples

5 Best Ways to Become root user or Superuser in Linux (RHEL/CentOS/Ubuntu)

7 Easy Steps to Install PHP on RHEL 8/CentOS 8

Easy Steps to Install Java on Ubuntu 20.04

Best Steps to Install Java on RHEL 8/CentOS 8

15 ansible-vault command examples to encrypt and decrypt sensitive data/files on Linux

When you are starting Apache server, you might get the AH00557 and AH00558 warning message as shown below.

# /usr/local/apache2/bin/apachectl start
AH00557: httpd: apr_sockaddr_info_get() failed for dev-server
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
Apache/2.4.2 mod_ssl (Pass Phrase Dialog)
Some of your private key files are encrypted for security reasons.
In order to read them you have to provide the pass phrases.
Server www.example.com:443 (RSA)
Enter pass phrase:
OK: Pass Phrase Dialog successful.

You’ll also get the same warning message even when you stop the Apache HTTPD server as shown below.

# /usr/local/apache2/bin/apachectl stop
AH00557: httpd: apr_sockaddr_info_get() failed for dev-server
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message

If you are using service httpd to stop and start, you ‘ll get the similar warning message.

# service httpd start
Starting httpd: httpd: apr_sockaddr_info_get() failed for dev-server
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

To fix the above warning message, add the “ServerName” directive to the httpd.conf file accordingly.

# vi /usr/local/apache2/conf/httpd.conf
ServerName 192.168.1.2

Note: Depending on how your are planning to setup the Apache, the above ServerName directive can either be a hostname, or ip-address, or fully qualified domain name. If you are just running the Apache for internal testing purpose, you can simply set it to the ip-address of the server.

If you want to use hostname in the httpd.conf file, make sure you also have a corresponding entry in the /etc/hosts file for that hostname as shown below.

# vi /usr/local/apache2/conf/httpd.conf
ServerName dev-server

# vi /etc/hosts
127.0.0.1   dev-server localhost.localdomain localhost

Now when you start the apache again, you’ll not get the warning message anymore.

# service httpd stop
Stopping httpd:    [  OK  ]