[
https://issues.apache.org/jira/browse/CASSANDRA-19565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838156#comment-17838156
]
Brandon Williams commented on CASSANDRA-19565:
----------------------------------------------
bq. But I admit, it is also unclear to me why this is only an issue in
Cassandra 4.1.4 and not on 4.0.12.
I think the difference must be in the jna versions. I've seen noexec on tmp
many times, and the solution has always been to redefine java.io.tmpdir to a
more forgiving path, but it seems newer jna will try to write other locations
too (and then segfault if they don't work.)
> SIGSEGV on Cassandra v4.1.4
> ---------------------------
>
> Key: CASSANDRA-19565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19565
> Project: Cassandra
> Issue Type: Bug
> Reporter: Thomas De Keulenaer
> Priority: Normal
> Fix For: 4.1.x
>
> Attachments: hs_err_pid1116450.log
>
>
> Hello,
> Since upgrading to v4.1. we cannat run CAssandra any more. Each start
> immediately crashes:
> {{Apr 17 08:58:34 SVALD108 cassandra[1116450]: # A fatal error has been
> detected by the Java Runtime Environment:
> Apr 17 08:58:34 SVALD108 cassandra[1116450]: # SIGSEGV (0xb) at
> pc=0x00007fccaab4d152, pid=1116450, tid=1116451}}
> I have added the log from the coe dump.
> This issue is perhaps related to
> https://davecturner.github.io/2021/08/30/seven-year-old-segfault.html ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
