Storage Engine will not start: "Unable to bind to address" shown in debug.log and/or system.log (4230150)

When trying to start the Storage Engine service it runs for a short time and then stops.

Displayed in the Debug.log or system.log is similar to the following:

ERROR [main] 2012-11-21 20:38:54,578 AbstractCassandraDaemon.java (line 271) Fatal configuration error
org.apache.cassandra.config.ConfigurationException: Unable to bind to address /:9260. Set listen_address in cassandra.yaml to an interface you can bind to, e.g., your private IP address on EC2

Note: The IP Address in the error is most likely the previous IP address of the UC Analytics server. 

In the doradus.log file you will see the following:

2012-11-23 14:45:14,194 INFO DBConnection: Connecting to Cassandra node :9260
2012-11-23 14:45:35,194 ERROR DBConnection: Could not connect to Cassandra
org.apache.thrift.transport.TTransportException: java.net.ConnectException: Connection timed out

Use command prompt to check if something else (another application) is binded to port 9260 by running:

netstat -an | find "9260"

When the Storage Engine is running, the IP address of the UC Analytics machine will be listening on 9260.

Use ipconfig from the command prompt to verify the IP address matches the IP that is displayed in the error. If not, it will need to be updated.

RESOLUTION

1. Edit cassandra.yaml with Notepad from "C:\Program Files\Quest\UC Analytics\Storage Engine\conf"

2. Use CTRL+F to find the IP address referenced in the error. It will appear twice in cassandra.yaml

- seeds:

- listen_address:

3. Update the IP addresses in cassandra.yaml

4. Save and close the file.

5. Edit the doradus.yaml file with Notepad from "C:\Program Files\Quest\UC Analytics\Query Engine\config"

6. Edit the line the says dbhost: with the correct IP address. (Use CTRL+F to locate the old address)

7. Save and close the file.

8. Start the Storage Engine

9. Verify that the UC-Analytics server is now listening on port 9260