[
https://issues.apache.org/jira/browse/CASSANDRA-19565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838494#comment-17838494
]
Thomas De Keulenaer commented on CASSANDRA-19565:
-------------------------------------------------
bq. It's a pity we don't have a repro, we could upgrade jna on a 4.0 PR and see
if it fails then, confirming the jna upgrade is the bit causing the problem
You probably also need to lock the machine down with SE Linux to force libffi
to create executable files.
[ElasticSearch|https://github.com/elastic/elasticsearch/issues/77014] also had
this issue.
{quote}
Do we have an idea of the specific controls that need to be enabled to
reproduce?
We know at least some of them I think:
* SELinux enabled & configured to prevent mmap() from creating anonymous
executable & writeable mappings
* /tmp, /var/tmp, /dev/shm all nonexistent or mounted noexec
* $HOME nonexistent for the elasticsearch user
* All mount points in /etc/mtab not writable by elasticsearch, or mounted noexec
* $ES_TMPDIR (and hence java.io.tmpdir and/or jna.tmpdir) pointing somewhere
writeable and not mounted noexec.
* $TMPDIR unset
{quote}
Also, on Cassandra 5.x with JNA >= 5.10.0 you can specify LIBFFI_TMPDIR.
I think it is best to set this to the same value as jna.tmpdir. Perhaps in
cassandra-env.sh?
> SIGSEGV on Cassandra v4.1.4
> ---------------------------
>
> Key: CASSANDRA-19565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19565
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Thomas De Keulenaer
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.1.x, 5.0.x, 5.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]
