[jira] [Commented] (CASSANDRA-13148) Systemd support for RPM
[ https://issues.apache.org/jira/browse/CASSANDRA-13148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146153#comment-17146153 ] Nicolas Chauvet commented on CASSANDRA-13148: - It would be fine to have someone assignee for the task. If anyone know how this issue can be escalated ? Please help. The issue "workarounded" for existing cassandra 3.11 releases, but cassandra4 should probably default to systemd. > Systemd support for RPM > --- > > Key: CASSANDRA-13148 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13148 > Project: Cassandra > Issue Type: New Feature > Components: Packaging >Reporter: Spiros Ioannou >Priority: Normal > > Since CASSANDRA-12967 will provide an RPM file, it would be greatly > beneficial if this package included systemd startup unit configuration > instead of the current traditional init-based, which misbehaves on > RHEL7/CentOS7. -- 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
[jira] [Commented] (CASSANDRA-15273) cassandra does not start with new systemd version
[ https://issues.apache.org/jira/browse/CASSANDRA-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055721#comment-17055721 ] Nicolas Chauvet commented on CASSANDRA-15273: - It would be appropriate to introduce systemd support for 4.0 instead See also: https://issues.apache.org/jira/browse/CASSANDRA-13148 https://github.com/apache/cassandra/pull/398 > 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 > Components: Packaging >Reporter: Aleksandr Yatskin >Assignee: Michael Semb Wever >Priority: Urgent > Fix For: 2.2.17, 3.0.21, 3.11.7, 4.0-alpha > > Attachments: > 0001-Fix-Red-Hat-init-script-on-newer-systemd-versions.patch > > > 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
[jira] [Commented] (CASSANDRA-13330) /var/run/cassandra directory not created on Centos7
[ https://issues.apache.org/jira/browse/CASSANDRA-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16999896#comment-16999896 ] Nicolas Chauvet commented on CASSANDRA-13330: - For information, I've submitted a PR with a tmpfile as part of the systemd service introduction: https://issues.apache.org/jira/browse/CASSANDRA-13148 > /var/run/cassandra directory not created on Centos7 > --- > > Key: CASSANDRA-13330 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13330 > Project: Cassandra > Issue Type: Bug > Components: Local/Config > Environment: CentOS Linux release 7.3.1611 (Core) (x86_64) > datastax-ddc.noarch 3.9.0-1 > datastax-ddc-tools.noarch 3.9.0-1 > java-1.8.0-openjdk.x86_64 1:1.8.0.121-0.b13.el7_3 > java-1.8.0-openjdk-headless.x86_64 1:1.8.0.121-0.b13.el7_3 >Reporter: Tobi >Priority: Low > > After updating cassandra from 3.4 to 3.9 via the datastax repo the startup > script /etc/init.d/cassandra was unable to stop cassandra. After checking the > startscript we found that it's tried to read pid file from > /var/run/cassandra/cassandra.pid > But as this path does not exist, the cassandra process could not be stopped. > As a fix we created /usr/lib/tmpfiles.d/cassandra.conf with this content > d /var/run/cassandra 0750 cassandra cassandra - > - > After that the directory was created on boot and the pid file could we > written in it -- 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
[jira] [Commented] (CASSANDRA-13148) Systemd support for RPM
[ https://issues.apache.org/jira/browse/CASSANDRA-13148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16999884#comment-16999884 ] Nicolas Chauvet commented on CASSANDRA-13148: - Hello, I have created a pull request at [https://github.com/apache/cassandra/pull/398] with a basic systemd unit file along RPM support to install the files as appropriate. This is targetted as 3.11 (instead of trunk) because most (CentOS 7) end-users are already affected since a recent change in system prevented to use the current initscript. (see also https://issues.apache.org/jira/browse/CASSANDRA-15273 ) About using sd_notify, I agree it would be a nice improvement, but so far isn't needed for a basic systemd file as a start. Please review. (side note, this is my first PR for the project). > Systemd support for RPM > --- > > Key: CASSANDRA-13148 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13148 > Project: Cassandra > Issue Type: New Feature > Components: Packaging >Reporter: Spiros Ioannou >Priority: Normal > > Since CASSANDRA-12967 will provide an RPM file, it would be greatly > beneficial if this package included systemd startup unit configuration > instead of the current traditional init-based, which misbehaves on > RHEL7/CentOS7. -- 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
