ISVM virtual machine continuously reboots every few minutes
search cancel

ISVM virtual machine continuously reboots every few minutes


Article ID: 324650


Updated On:




  • One of the ISVM virtual machines is in a boot loop (continuously rebooting every few minutes).
  • Errors mentioning one or more commitlog failures may be present in the /opt/vmware/cassandra/apache-cassandra-2.2.4/logs/debug.log file on the same ISVM VM.


Cassandra watchdog configuration on the ISVM virtual machines may cause a continuous boot loop if the service fails at startup.


This is a known issue affecting VMware Cloud Foundation 2.x.
This issue is resolved in VMware Cloud Foundation version 2.1.3, available at VMware Downloads.

To work around this issue if you do not want to upgrade, complete this procedure to stop the boot loop:
  1. Log in to the ISVM VM as the root user.
  2. Make a copy of the /opt/vmware/ism/scripts/common/ file by running this command:

    cp /opt/vmware/ism/scripts/common/ /tmp/

  3. Open the /opt/vmware/ism/scripts/common/ file using a text editor.
  4. Find the line that begins with MAX_CASS_RESTARTS and set the value to 9999999.
  5. Save and close the file.

Additional Information

This issue may be related to corrupted Cassandra commit logs. Cassandra fails to restart successfully and the watchdog service on the ISVM VMs after failing to restart Cassandra for 16 times, reboots the ISVM VMs.
To work around this issue:
  1. Stop the watchdog service on the ISVM VM by running this command:

    service ism-watchdog stop
  2. Inspect the Cassandra logs /opt/vmware/cassandra/apache-cassandra-2.2.4/logs/debug.log and identify the offending commit log file name which is corrupted.
  3. If any corrupted commit logs are noted in Step 2, remove them from the /opt/vmware/ism/logs folder using the rm command.
  4. Restart Cassandra by running this command:

    service cassandraserver start
  5. Repeat the process until all corrupted commit logs are deleted. There is no automation of remediating a commit log corruption failure.

Note: If the service does not start successfully, look for more commit log failures and remove the offending commit logs.