Bug #19834: Segmentation fault while running in docker

• Status: Rejected
• Assignee: -
• Target version: -
• ruby -v: ruby 2.6.3p62 (2019-04-16 revision 67580) [aarch64-linux]
• Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN

2023-08-09 12:44:32 /usr/local/lib/ruby/2.6.0/openssl/buffering.rb:383: [BUG] Illegal instruction at 0x0000ffff90d911a0
2023-08-09 12:44:32 ruby 2.6.3p62 (2019-04-16 revision 67580) [aarch64-linux]
2023-08-09 12:44:32 
2023-08-09 12:44:32 -- Control frame information -----------------------------------------------
2023-08-09 12:44:32 c:0046 p:---- s:0274 e:000273 CFUNC  :syswrite_nonblock
2023-08-09 12:44:32 c:0045 p:0013 s:0268 e:000267 METHOD /usr/local/lib/ruby/2.6.0/openssl/buffering.rb:383
2023-08-09 12:44:32 c:0044 p:0021 s:0261 e:000260 BLOCK  /usr/local/lib/ruby/2.6.0/net/protocol.rb:277 [FINISH]
2023-08-09 12:44:32 c:0043 p:---- s:0253 e:000252 IFUNC 
2023-08-09 12:44:32 c:0042 p:---- s:0250 e:000249 CFUNC  :each
2023-08-09 12:44:32 c:0041 p:---- s:0247 e:000246 CFUNC  :each_with_index

I am using Ruby 2.6.3 in my project. It works fine until this week, I don't know why this is occurring. I have tried the solution mentioned in https://bugs.ruby-lang.org/issues/18555#note-6 the above issue, but it doesn't solve my problem.

• ruby -v changed from 2.6.3 to ruby 2.6.3p62 (2019-04-16 revision 67580) [aarch64-linux]

This issue happens when ever I try to access the db from console or while making any request from browser.

[e-mail] (Ramachandran A) wrote:

2023-08-09 12:44:32 /usr/local/lib/ruby/2.6.0/openssl/buffering.rb:383: [BUG] Illegal instruction at 0x0000ffff90d911a0
2023-08-09 12:44:32 ruby 2.6.3p62 (2019-04-16 revision 67580) [aarch64-linux]
2023-08-09 12:44:32 
2023-08-09 12:44:32 -- Control frame information -----------------------------------------------
2023-08-09 12:44:32 c:0046 p:---- s:0274 e:000273 CFUNC  :syswrite_nonblock
2023-08-09 12:44:32 c:0045 p:0013 s:0268 e:000267 METHOD /usr/local/lib/ruby/2.6.0/openssl/buffering.rb:383
2023-08-09 12:44:32 c:0044 p:0021 s:0261 e:000260 BLOCK  /usr/local/lib/ruby/2.6.0/net/protocol.rb:277 [FINISH]
2023-08-09 12:44:32 c:0043 p:---- s:0253 e:000252 IFUNC 
2023-08-09 12:44:32 c:0042 p:---- s:0250 e:000249 CFUNC  :each
2023-08-09 12:44:32 c:0041 p:---- s:0247 e:000246 CFUNC  :each_with_index

I am using Ruby 2.6.3 in my project. It works fine until this week, I don't know why this is occurring. I have tried the solution mentioned in https://bugs.ruby-lang.org/issues/18555#note-6 the above issue, but it doesn't solve my problem. This issue happens when ever I try to access the db from console or while making any request from browser.

[byroot (Jean Boussier)]

• Status changed from Open to Rejected

Ruby 2.6.3 has reached end of life aeons ago.

byroot (Jean Boussier) wrote in #note-3:

Ruby 2.6.3 has reached end of life aeons ago.

We are working on legacy project, we can't update the ruby version in our project. How can I solve this issue without upgrading Ruby?

[byroot (Jean Boussier)]

You can of course attempt to debug it and patch it yourself.

But that version being end of life means Ruby core won't spend time on it. And even if we wanted we couldn't because you didn't include nearly enough information anyway.

[austin (Austin Ziegler)]

[e-mail] (Ramachandran A) wrote in #note-4:

byroot (Jean Boussier) wrote in #note-3:

Ruby 2.6.3 has reached end of life aeons ago.

We are working on legacy project, we can't update the ruby version in our project. How can I solve this issue without upgrading Ruby?

You probably can’t. The last version of Ruby 2.6 was Ruby 2.6.10, and you should try using that before trying to debug and patch this yourself. You say that you’re running this in Docker. Has the docker image been updated since last week? That is, could the underlying OpenSSL library be different than the one that Ruby 2.6.3 is expecting (this is not impossible). Has your docker image always been running aarch64, or is that a recent change from x86_64?

Your other option is to try to find someone who would be willing to investigate and provide some level of commercial support, but given that Ruby 2.6 is ~two years EOL, I would not expect such support to be cheap, if you can even find it (a quick search did not find anything from my perspective).