[ https://issues.apache.org/jira/browse/CASSANDRA-19565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-19565: ----------------------------------------- Attachment: cassandra_57_redhat_jdk11_amd64_attempt1.log.xz cassandra_57_debian_jdk11_amd64_attempt1.log.xz > 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: cassandra_57_debian_jdk11_amd64_attempt1.log.xz, > cassandra_57_redhat_jdk11_amd64_attempt1.log.xz, 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org