Navigating to the hostname or IP address of the backup server does not load the ZMC login page

This article is for Amanda Enterprise (AE)

This article is for Zmanda Recovery Manager For MySQL (ZRM)

Symptoms

Navigating to the hostname or IP address of the backup server in your browser does not load the ZMC login page.

Troubleshooting Tips

The first thing to verify is whether the Apache service is actually running. The following can be run as the root user on the backup server:
 

# /etc/init.d/zmc_aee status
...
Server Version: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8r mod_fastcgi/2.4.6
Server uptime: 15 hours 56 minutes 18 seconds
1 requests currently being processed, 2 idle workers

Lines such as the above in the output of an AE 3.3 and later server indicate the Apache server is running. If similar lines are not seen on a AE 3.3 and later server or the Apache service is not seen to be running with the same command run on a previous AE version, try restarting ZMC services as shown below when run as the root user:
 

# /etc/init.d/zmc_aee restart

When the Apache server is confirmed to be running, verify that there is a service listening on the http and https ports or whichever ports you specified during install if the default ports were already taken?

 

# netstat -tl
...
tcp        0      0 *:http                     *:*                         LISTEN      
...
tcp        0      0 *:https                    *:*                         LISTEN

If so, you can also prove whether you can connect to the service directly from the backup server with telnet using the default or alternate port selected during install:

 

$ telnet localhost 443

Use CTRL-] to close the connection and “quit” to quit telnet.

If you can connect to the https service from the backup server itself but not from a remote host, verify if a firewall may be blocking the http and https ports on the backup server when trying to connect to the Apache web server:
 

# iptables -L

If firewall rules show that not all connections are being accepted, verify if there are rules specifically for ports http and https being passed through the firewall for whichever port you specified during install.