ClickHouse
clickhouse driver crash reported
A driver crash reported, which eventually cause our child process dead. The core dump is attached. Please help us on this.
From the core dump, there is one thread has more than 1000 frames (looks like stack overflow), which may be related with this crash. 1 __lll_lock_wait
/usr/lib64/libpthread-2.17.so
2 _L_lock_883
/usr/lib64/libpthread-2.17.so
3 _L_lock_883
/usr/lib64/libpthread-2.17.so
4 _L_lock_883
/usr/lib64/libpthread-2.17.so
5 _L_lock_883
/usr/lib64/libpthread-2.17.so
6 _L_lock_883
/usr/lib64/libpthread-2.17.so
7 _L_lock_883
/usr/lib64/libpthread-2.17.so
8 _L_lock_883
/usr/lib64/libpthread-2.17.so
9 _L_lock_883
/usr/lib64/libpthread-2.17.so
10 _L_lock_883
/usr/lib64/libpthread-2.17.so
11 _L_lock_883
/usr/lib64/libpthread-2.17.so
...
1025 _L_lock_883
/usr/lib64/libpthread-2.17.so
tail(timestamp): Mon Apr 05 2021 14:37:44 GMT+0000 (Coordinated Universal Time) tail(_missing_symbol): 1 tail(_tx): 730ca tail(callstack):
[0] /usr/lib64/libclickhouseodbc.so + 0x155e80 sp=0x2af43e0a1098 bp=0x2af441823ce8 [1] /usr/lib64/libclickhouseodbc.so + 0x163ac4 [2] /usr/lib64/libclickhouseodbc.so + 0x40d9dc [3] /usr/lib64/libclickhouseodbc.so + 0x162e50 [4] /usr/lib64/libclickhouseodbc.so + 0x453e80 [5] /usr/lib64/libclickhouseodbc.so + 0x158548 [6] /usr/lib64/libclickhouseodbc.so + 0x153b0f [7] /usr/lib64/libclickhouseodbc.so + 0xd8f00
tail(classifiers): segv tail(error.message): SIGSEGV /SEGV_MAPERR tail(hostname): tmstr02h.oebs.yandex.net histogram(hostname): tmstr02h.oebs.yandex.net ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆ 1 tail(uname.sysname): Linux tail(uname.version): 0.0.0 Linux 4.1.12-61.1.24.el7uek.2.paysys.x86_64 #2 SMP Thu Aug 8 15:33:17 MSK 2019 x86_64 tail(customer_dsi): 126600 tail(cpu.count): 1 tail(version): 11.3.0100.18093 histogram(version): 11.3.0100.18093 ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆ 1 tail(application): M8MulPrc.11.3.0100.1416 tail(purpose): undefined tail(reason): undefined tail(slack_channel_id): undefined tail(fingerprint;issues;ticket): undefined tail(fingerprint;issues;tags): undefined tail(podname): undefined tail(upload_status_DSSErrors.log): excluded tail(production_env): 0
Customer Release Set: 11.3.0 DE199491.zip
If you can reproduce this, maybe you could do it with a manually built Debug driver?
74dd7.zip Hi traceon,
In fact, it is a crash reported from our customer. We have to go back to our customer and see whether they can reproduce this issue. And the driver crash caused our child process crashed.
Also could you help us double check whether the newly uploaded crash mini dump is the same?