Skip to end of metadata
Go to start of metadata


I can't connect to the CoprHD UI login page with a web browser after installing the storageos rpm.


There are many possible causes to the problem.

Follow the steps below and you have a better chance to pinpoint the root cause:

  1. Make sure you are accessing https://<VIP_address>:443/. The port number is optional, but accessing port 4443 from a web browser won't lead you to the login page.
  2. See if you can ping the VIP address. If the VIP address is not reachable, keepalived service probably didn't start. Check the status by running "systemctl status keepalived" and seek help from the CoprHD google group.
  3. If the VIP is reachable but not port 443, there's probably something wrong with the nginx service. Check the status by running "systemctl status nginx" and usually you will see the following:

nginx.service - Nginx service

   Loaded: loaded (/etc/systemd/system/nginx.service; enabled)

   Active: inactive (dead)

           start condition failed at Thu 2015-08-13 17:45:57 PDT; 14h ago

           ConditionFileNotEmpty=/opt/storageos/conf/storageos.crt was not met

The last line indicates that one of the prerequisite files for nginx: /opt/storageos/conf/storageos.crt (the other one being /opt/storageos/conf/storageos.key) wasn't generated by syssvc.

The next step is to look into the /opt/storageos/logs/syssvc.log file.

Check towards the end of the log file and try to find any log messages starting with ERROR. Post any of these error messages to the CoprHD google group.

If you see repeated warnings like the following, the error is in coordinatorsvc and you need to check the /opt/storageos/logs/coordinatorsvc.log file instead:

2015-08-13 09:38:22,164 [main-SendThread(]  WARN (line 1102) Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect Connection refused

        at Method)


        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(

        at org.apache.zookeeper.ClientCnxn$

 If you see repeated messages the following, the problem is on the dbsvc side and you should look into the /opt/storageos/logs/dbsvc.log file:


2015-08-17 20:41:25,072 [main] WARN (line 98) no dbsvc instance running. Coordinator exception message: The coordinator cannot locate any service with path /service/dbsvc/2.3
2015-08-17 20:41:25,072 [main] WARN (line 65) hostsupplier is empty. May be dbsvc hasn't started yet. waiting for 10000 msec