Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Troubleshooting corrupted Cassandra commit logs in VMware Cloud Foundation (57372)

Last Updated: 12/15/2018Categories: TroubleshootingTotal Views: 6856Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The Cassandra service is running but in degraded mode.

The LCM Service fail to start with a messages similar to the following "lcm.pid not readable"

# service lcm status

* lcm.service - LCM app

Loaded: loaded (/etc/systemd/system/lcm.service; enabled; vendor preset: enabled)

Active: failed (Result: resources) since Thu 2018-05-17 17:04:12 UTC; 12s ago

Process: 50860 ExecStart=/home/vrack/lcm/lcm-app/bin/lcm-service.sh start (code=exited, status=0/SUCCESS)

May 17 17:04:09 sddc-manager.mv.rackspace.com systemd[1]: Starting LCM app...

May 17 17:04:09 sddc-manager.mv.rackspace.com systemd[1]: lcm.service: PID file /home/vrack/lcm/logs/lcm.pid not readable (yet?) after start: No such file or directory

May 17 17:04:12 sddc-manager.mv.rackspace.com systemd[1]: lcm.service: Daemon never wrote its PID file. Failing.

May 17 17:04:12 sddc-manager.mv.rackspace.com systemd[1]: Failed to start LCM app.

May 17 17:04:12 sddc-manager.mv.rackspace.com systemd[1]: lcm.service: Unit entered failed state.

May 17 17:04:12 sddc-manager.mv.rackspace.com systemd[1]: lcm.service: Failed with result 'resources'.

For  VMware Cloud Foundation for Service Providers 2.4.x you see messages similar to the following in the  /var/opt/cassandra/logs/debug.log  on the SDDC Manager Controller VM

ERROR [main] 2018-05-29 17:36:40,103 JVMStabilityInspector.java:82 - Exiting due to error while processing commit log during initialization.

org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Could not read commit log descriptor in file /var/opt/cassandra/data/commitlog/CommitLog-6-1527302840621.log

For VMware Cloud Foundation for Integrated Systems 2.2.x and 2.3.x you see messages similar to the following in /opt/vmware/cassandra/apache-cassandra-2.2.4/logs/debug.log on the SDDC Manager Controller VM.

ERROR [main] 2018-08-14 18:32:36,075 JVMStabilityInspector.java:78 - Exiting due to error while processing commit log during initialization.
org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: Could not read commit log descriptor in file /opt/vmware/cassandra/apache-cassandra-2.2.4/bin/../data/commitlog/CommitLog-5-1534191227161.log

For VMware Cloud Foundation for Integrated Systems 3.x you see messages similar to the following in /var/opt/cassandra/logsdebug.log on the SDDC Manager Controller VM.

ERROR [main] 2018-12-14 14:38:57,488 JVMStabilityInspector.java:102 - Exiting due to error while processing commit log during initialization.
org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Could not read commit log descriptor in file /var/opt/cassandra/data/commitlog/CommitLog-6-1541589396779.log

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

If the SDDC Manager Controller VM runs out of disk space, the Cassandra database will start overwriting the CommitLogxxxx.log files, which can cause several database logs to become corrupted . When Cassandra is committing these logs to its database it will run in a degraded mode; this will cause the LCM service to stop running.

Resolution

To resolve this issue:

For  VMware Cloud Foundation for Service Providers 2.4.x

Run the following command to check the status of the Cassandra service

service cassandra status

Inspect the /var/opt/cassandra/logs/debug.log located on the SDDC Manager Controller VM and  identify the corrupted commitLogs.log file name.

less /var/opt/cassandra/logs/debug.log

org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Could not read commit log descriptor in file /var/opt/cassandra/data/commitlog/CommitLog-6-1527302840621.log

Run the following commands to stop the watchdogserver service and the Cassandra service.

/home/vrack/lcm/lcm-app/bin/lcm-watchdogserver.sh stop
service cassandra stop

Navigate to /var/opt/cassandra/data/commitlog directory and remove  the corrupted CommitLog.log file that was identified in Step 2.

cd /var/opt/cassandra/data/commitlog

rm  CommitLog-#-######.log

Run the following commands to start the watchdogserver service and the Cassandra service.

/home/vrack/lcm/lcm-app/bin/lcm-watchdogserver.sh start
service cassandra start

Repeat Steps 1 to 5 until all corrupted commit logs are deleted and there is no automation of remediating a commit log corruption failure.

The LCM service will start once there aren't any corrupted CommitLogs.

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

For VMware Cloud Foundation Integrated Systems 2.2.x and 2.3.x

Run the following command to check the status of the Cassandra service

systemctl status cassandra

Inspect the /opt/vmware/cassandra/apache-cassandra-2.2.4/logs/debug.log  located on the SDDC Manager Controller VM and  identify the corrupted commitlogs file name..

less /opt/vmware/cassandra/apache-cassandra-2.2.4/logs/debug.log

org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: Could not read commit log descriptor in file /opt/vmware/cassandra/apache-cassandra-2.2.4/bin/../data/commitlog/CommitLog-5-1534191227161.log

Run the following commands to stop the scs service and cassandra service

systemctl stop scs
systemctl stop cassandra

Navigate to /opt/vmware/cassandra/apache-cassandra-2.2.4/bin/../data/commitlog directory and remove  the corrupted CommitLog.log that was identified in step 2.

cd /opt/vmware/cassandra/apache-cassandra-2.2.4/bin/../data/commitlog

rm CommitLog-#-######.log

Run the following commands to start the scs service and cassandra service

systemctl start scs
systemctl start cassandra

Repeat Steps 1 to 5 until all corrupted commit logs are deleted and there is no automation of remediating a commit log corruption failure.

The LCM service will start once there aren't any corrupted CommitLogs.

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

For VMware Cloud Foundation Integrated Systems 3.x

Run the following command to check the status of the Cassandra service

systemctl status cassandra

Inspect the /var/opt/cassandra/logs/debug.log  located on the SDDC Manager Controller VM and  identify the corrupted commit logs file name..

less /var/opt/cassandra/logs/debug.log

org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: Could not read commit log descriptor in file /var/opt/cassandra/data/commitlog/CommitLog-5-1534191227161.log

Run the following commands to stop the scs service and cassandra service

systemctl stop scs
systemctl stop cassandra

Navigate to /var/opt/cassandra/data/commitlog/ directory and remove  the corrupted CommitLog.log that was identified in step 2.

cd /var/opt/cassandra/data/commitlog/

rm CommitLog-#-######.log

Run the following commands to start the scs service and cassandra service

systemctl start scs
systemctl start cassandra

Repeat Steps 1 to 5 until all corrupted commit logs are deleted and there is no automation of remediating a commit log corruption failure.

The LCM service will start once there aren't any corrupted CommitLogs.

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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.5.x

VMware Cloud Foundation 3.0.x

VMware Cloud Foundation 2.3.x

VMware Cloud Foundation 2.2.x

Take Our Survey

Support Assistant