SAP Knowledge Base Article - Preview

2786903 - Server hung after signal 11 at kstcpnetctlrCancelRequests() and undo_blockingcall_nowait() - SAP ASE

Symptom

  • ASE server completely hung
  • Configured memory dump on signal 11 could not complete
  • Relevant error log snippets include: 

Current process (0x0) infected with signal 11 (SIGSEGV)
Current Process is running on a Non-Engine Thread
Address 0x0x00000000014f3a62 (kstcpnetctlrCancelRequests+0x31f)

  • If ASE is configured for a shared memory dump, the dump will fail with a subsequent signal 11 in undo_blockingcall_nowait:

...
Initiating shared memory dump for signal 11.
Writing segment 0:

Current process (0x0) infected with signal 11 (SIGSEGV)
Current Process is running on a Non-Engine Thread
Address 0x0x00000000014c3ffc (undo_blockingcall_nowait+0x68)

Run to completion task iocRunController(ac0a0470) exception 11
nthrd_backtrace
krtctskException
undo_blockingcall_nowait
shm__write_memsegment
...
Warning: The internal timer is not progressing. If this message is generated multiple times, report to SAP Technical Support and restart the server (alarminterval=-887).

  • The dataserver process needs to be killed on the OS level.


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR818324, CR#818324, 818324, CR#819187, CR819187, 819187, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  stack, registers, unresponsive, hang, hanging, memdump , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

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.