Symptom
You can see the nstuil crashes with following crash_stack.
nsutil.crashdump.xxxxxx-xxxxxx.xxxxxxx.trc
[CRASH_SHORTINFO] Exception short info:
SIGNAL 11 (SIGSEGV) caught, thread: 4[thr=0]: <SYSTEM>, addr: xxxx, time: xxx
[OK] in 00:00:00 001
...
[CRASH_STACK] Stacktrace of crash:
----> Symbolic stack backtrace <----
0: pthread_cancel_init + 0x2
1: Execution::initialize_libgcc_s_handle() + 0x3f
2: pthread_create + 0x38
3: Execution::Thread::start(Execution::Thread::CreationFlags, unsigned long, int, bool) + 0xf92
4: mainInitialPhase + 0x7a1
5: System::mainWrapper(int, char**, char**) + 0x95
6: __libc_start_main + 0xef
Read more...
Environment
- HANA 2.0
Product
Keywords
KBA , HAN-DB , SAP HANA Database , 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.
SAP Knowledge Base Article - Preview