Troubleshooting starting DataStax Enterprise 

Troubleshooting tips for starting DataStax Enterprise.

The DataStax Enterprise Help Center also provides troubleshooting information.

To identify and resolve start problem, try these steps before contacting DataStax Support.

Start DataStax Enterprise 

Start DataStax Enterprise:

Verify DataStax Enterprise status 

  • Package and Installer-Services installations:
    $ sudo service dse status
  • Tarball and Installer-No Services installations:
    $ install_location/nodetool status

Review the log files 

If DataStax Enterprise is not running, or starts running and then stops, look for errors at the end of the system log file:
$ cat /var/log/cassandra/system.log

Discover the process ID 

It is possible that an active DSE or Cassandra process is interfering with starting DataStax Enterprise. For example, on a local development node:

  1. Verify the node status:
    • Package and Installer-Services installations:
      $ nodetool status
    • Tarball and Installer-No Services installations:
      $ install_location/nodetool status
    Datacenter: Cassandra
    =====================
    Status=Up/Down
    |/ State=Normal/Leaving/Joining/Moving
    --  Address    Load       Owns  Host ID                               Token                Rack
    UN  127.0.0.1  206.23 KB  54%   392b0ca3-3090-440f-8a17-93702234aeec  1093280155279701211  rack1
  2. However, there can be a situation where Cassandra is running, but DataStax Enterprise is not. For example, if your environment had earlier product versions installed or the product was not shut down gracefully, look for the Cassandra process ID and terminate the Cassandra process:
    $ pgrep -f cassandra
    29474
    $ sudo kill -9 29474

Subprocesses not killed when DataStax Enterprise is shut down improperly 

To prevent this problem, avoid using kill 9 and shut down DataStax Enterprise properly.
  • Package and Installer-Services installations:
    $ nodetool status
  • Tarball and Installer-No Services installations:
    $ install_location/nodetool status
If DataStax Enterprise is shut down with kill -9, you must restart the node or manually kill any remaining sub-processes:
  • Package and Installer-Services installations:
    For example, if DataStax Enterprise was started using $ sudo services dse start or $ sudo /etc/init.d/dse start and the main process was killed using $ kill -9 `cat /var/run/dse/dse.pid`:
    1. To view the subprocesses left behind (all DSE processes run under user cassandra [default]):
      $ pgrep -c -ucassandra >/dev/null && ps -o pid,ppid,user,args `pgrep -ucassandra`
    2. To shut down the subprocesses:
      $ sudo pkill -ucassandra
  • Tarball and Installer-No Services installations:
    For example, if DataStax Enterprise was started using $ sudo dse cassandra -k -t and the main process was killed using $ sudo kill -9 `cat /var/run/dse/dse.pid` or $ sudo pkill -9 -f jmxremote.port=7199:
    1. To view the subprocesses left behind:
      $ pgrep -c -f dse-5.1 >/dev/null && ps -o pid,ppid,user,args `pgrep -f dse-5.0

      All DataStax Enterprise processes run under user cassandra.

    2. To shut down the subprocesses:
      $ sudo pkill -f dse-5.1
Note: The kill command (SIGTERM) shuts down the subprocesses.