[
https://issues.apache.org/jira/browse/CASSANDRA-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981976#comment-16981976
]
Mike Kelly commented on CASSANDRA-15273:
----------------------------------------
The fix from [~musinsky] doesn't seem to have helped for me. I'm now seeing:
{noformat}
Nov 25 18:19:31 test.example.com systemd[1]: Starting LSB: distributed storage
system for structured data...
-- Subject: Unit cassandra.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cassandra.service has begun starting up.
Nov 25 18:19:31 test.example.com runuser[7211]: pam_unix(runuser:session):
session opened for user cassandra by (uid=0)
Nov 25 18:19:32 test.example.com cassandra[7201]: Starting Cassandra: OK
Nov 25 18:19:32 test.example.com systemd[1]: New main PID 7289 does not exist
or is a zombie.
Nov 25 18:19:32 test.example.com systemd[1]: Failed to start LSB: distributed
storage system for structured data.
-- Subject: Unit cassandra.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cassandra.service has failed.
--
-- The result is failed.
Nov 25 18:19:32 test.example.com systemd[1]: Unit cassandra.service entered
failed state.
Nov 25 18:19:32 test.example.com systemd[1]: cassandra.service failed.
{noformat}
> cassandra does not start with new systemd version
> -------------------------------------------------
>
> Key: CASSANDRA-15273
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15273
> Project: Cassandra
> Issue Type: Bug
> Reporter: Aleksandr Yatskin
> Priority: Urgent
>
> After update systemd with fixed vulnerability
> https://access.redhat.com/security/cve/cve-2018-16888, the cassandra service
> does not start correctly.
> Environment: RHEL 7, systemd-219-67.el7_7.1, cassandra-3.11.4-1
> (https://www.apache.org/dist/cassandra/redhat/311x/cassandra-3.11.4-1.noarch.rpm)
> ---------------------------------------------------------------
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
