Installation Guide

server” (page 11).) In the controller installation with a remote Keystone server, entering the UUID
provider type is done by editing the keystone.conf file on the remote server. (See “Setting the
provider type to UUID on the remote Keystone server” (page 13).)
8.9 The controller ceases to operate when running Network Protector
8.9.1 Problem description
In a controller installation supporting the Network Protector application, if the Cassandra service
fails, Network Protector and the controller cease to operate.
8.9.2 Solution
Restart the Cassandra service:
1. Verify that the SDNC service is started (sudo service sdnc status). You should see
the following output:
sdnc start/running, process nnnn
2. Use the following command to determine whether Cassandra is running:
ps –ef | grep –i Cassandra
• If Cassandra is not running, you will see output similar to the following:
sdn 16941 16487 0 15:01 pts/0 00:00:00 grep --color=auto cassandra
In this case, go to step 3.
• If Cassandra is running, output similar to the following example appears, which indicates
that Cassandra is not causing the controller to halt.
sdn 22162 1 6 15:09 ? 00:00:05 /usr/lib/jvm/java-7-openjdk-amd64/bin/java -ea
-javaagent:/opt/sdn/cassandra/lib/jamm-0.2.5.jar -XX:+UseThreadPriorities
-XX:ThreadPriorityPolicy=42 -Xms1024M -Xmx1024M -Xmn256M -XX:+HeapDumpOnOutOfMemoryError
-Xss256k -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled
-XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly -XX:+UseTLAB -XX:+UseCondCardMark
-Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote.port=7199
-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
-Dlog4j.configuration=log4j-server.properties -Dlog4j.defaultInitOverride=true
. . .
org.apache.cassandra.service.CassandraDaemonsdn 22431 18086 0 15:11 pts/0 00:00:00 grep
--color=auto Cassandra
3. If Cassandra is not running, disable Network Protector on the controller.
4. If there is no Cassandra process running, then determine whether the Cassandra .pid file is
present in /opt/sdn/cassandra/data/cassandra.pid.
• If the .pid file is present, delete it (rm –rf
/opt/sdn/cassandra/data/cassandra.pid) and go to step 5.
• If the .pid is not present, go to step 5.
5. Change to the Cassandra bin directory:
cd /opt/sdn/cassandra/bin
6. Use this command to restart the Cassandra server:
./caServer.sh start
7. Use this command to verify that Cassandra has started:
./caServer.sh status
You should then see output similar to the following:
24 Troubleshooting