SAP Knowledge Base Article - Preview

2477404 - Server fails to start and reports 'engine has died' message with stack containing keipanic - SAP ASE

Symptom

  • ASE engine crash when starting > 1 engine
  • Either startup with multiple engines or use sp_engine to add additional engines
  • ASE log contains message 'engine has died' with a stacktrace including 'keipanic' function :

Engine 0 (os pid 1234) has died, server is performing emergency shutdown
...
keipanic
kpsched
end of stack trace, kernel service process: kpid 456789
ueshutdown: exiting

  • ASE does not crash immediately at startup (or with sp_engine) but crashes as soon as the first user activity / query is run
  • Behaviour is slighly different depending on the LD_POINTER_GUARD variable. It crashes in both cases, with :
    • LD_POINTER_GUARD=0 it kills engine 0
    • LD_POINTER_GUARD=1 kills other engines randomly
  • OS settings in /etc/sysctl.conf :
    • kernel.exec-shield=0
    • kernel.randomize_va_space=0
    • vm.legacy_va_layout=1


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.0.x & 15.5
  • Recent Linux distributions, but exact versions are not known with certainty:
    • Linux Redhat 7.x
    • SuSE 11 SP3 or higher

Product

Sybase Adaptive Server Enterprise 15.0 ; Sybase Adaptive Server Enterprise 15.5

Keywords

Exec-Shield, sysctl, sysctl.conf , keipanic+0xf5() , kpsched+0x1095(), process kernel, threaded kernel , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.