Closed styrken closed 1 year ago
@styrken few questions for you. This is first time you are using ibm_db adapter ? Are you facing this always or intermittently ?
Looking at call stack, its crashing while ibm_db adapter is fetching server info DB, not sure what caused this. Can you provide us info on how to reproduce this ?
It's not first time. We are upgrading an old Rails app (3+) to 6.1. Most works but this segmentation fault is sometimes thrown (on a specific page).
@styrken try downgrading or upgrading rails & ruby to previous or next version. Sometimes it resolves.
@praveen-db2 okey let me try downgrading ruby
Hello @praveen-db2, we have tried using ruby 2.7.6p219
and we get this segmentation fault:
* Puma version: 5.6.5 (ruby 2.7.6-p219) ("Birdie's Version")
* Min threads: 5
* Max threads: 5
* Environment: staging
* PID: 2237751
* Listening on http://0.0.0.0:3000
Use Ctrl-C to stop
/data/apps/apps/shared/bundle/ruby/2.7.0/gems/puma-5.6.5/lib/puma/server.rb:179: SEGV received in SEGV handler
[BUG] Segmentation fault at 0x0000000000000000
ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [x86_64-linux]
-- Control frame information -----------------------------------------------
c:0007 p:---- s:0067 e:000066 CFUNC :getsockopt
c:0006 p:0059 ./start-staging.sh: line 7: 2237751 Aborted (core dumped) RAILS_ENV=staging IBM_DB_HOME=/data/dsdriver/ LD_LIBRARY_PATH=/data/dsdriver/lib:$LD_LIBRARY_PATH bundle exec rails s -b 0.0.0.0
@styrken its crashing in gem puma. Not sure whats causing these. We can help if anything related to ibm_db gem. Rest you need to figure out.
Hi @praveen-db2 , it seems to start working by simply switching to the Thin web-server instead of PUMA.
Hi,
I am getting this strange segmentation fault. Any pointers on how to debug that? Not sure if its a ruby issue or db issue.