Hi.
After update systemd with fixed vulnerability
https://access.redhat.com/security/cve/cve-2018-16888, the cassandra service
does not start correctly.
How to fix it? It may be necessary to add a real service unit for systemd ?
--------------------------------------------------------
systemctl status cassandra
● cassandra.service - LSB: distributed storage system for structured data
Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled)
Active: failed (Result: resources) since Fri 2019-08-09 17:20:26 MSK; 1s ago
Docs: man:systemd-sysv-generator(8)
Process: 2414 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited,
status=0/SUCCESS)
Process: 2463 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited,
status=0/SUCCESS)
Main PID: 1884 (code=exited, status=143)
Aug 09 17:20:23 desktop43.example.com systemd[1]: Unit cassandra.service
entered failed state.
Aug 09 17:20:23 desktop43.example.com systemd[1]: cassandra.service failed.
Aug 09 17:20:23 desktop43.example.com systemd[1]: Starting LSB: distributed
storage system for structured data...
Aug 09 17:20:23 desktop43.example.com su[2473]: (to cassandra) root on none
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.
