We get this error when we start our Cassandra recently. New main PID x does not belong to service, and PID file is not owned by root. Refusing. After checking, we found that it is a bug for cassandra startup file.
Table of Contents
Error Log for Unit Cassandra.service entered failed state
systemctl status cassandra
cassandra.service – LSB: distributed storage system for
Aug 09 17:20:26 desktop43.example.com cassandra[2463]: Starting Cassandra: OK
Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not belong to service, and PID file is not owned by root. Refusing.
Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not belong to service, and PID file is not owned by root. Refusing.
Aug 09 17:20:26 desktop43.example.com systemd[1]: Failed to start LSB: distributed storage system for structured data.
Aug 09 17:20:26 desktop43.example.com systemd[1]: Unit cassandra.service entered failed state.
Aug 09 17:20:26 desktop43.example.com systemd[1]: cassandra.service failed.
Boost Your Website Speed!
If you want your website to run as fast as ours, consider trying Cloudways. Their powerful cloud infrastructure and optimized stack deliver exceptional performance. Free migration!Fix Unit Cassandra.service entered failed state
The fix for systemd CVE-2018-16888 required changes to init scripts, so that PID files end up owned by the “root” user. Here is the fix for this issue.
https://issues.apache.org/jira/browse/CASSANDRA-15273
After this file /etc/rc.d/init.d/cassandra is changed, the issue is gone.
- OS vulnerability:https://access.redhat.com/security/cve/cve-2018-16888
- Cassandra bug:https://issues.apache.org/jira/browse/CASSANDRA-15273
- script fix: https://issues.apache.org/jira/secure/attachment/12993922/0001-Fix-Red-Hat-init-script-on-newer-systemd-versions.patch
- file: /etc/rc.d/init.d/cassandra