Segmentation fault

jj458

After update to current devel version several segmentation faults occur:
CentOS Linux release 7.4.1708 (Core)
python-2.7.5-58.el7.x86_64
python-libs-2.7.5-58.el7.x86_64
kopano-server-8.6.80.493-50.1.x86_64
kopano-client-8.6.80.493-50.1.x86_64
kopano-utils-8.6.80.493-50.1.x86_64
libmapi1-8.6.80.493-50.1.x86_64
python2-mapi-8.6.80.493-50.1.x86_64

Fri Apr  6 02:09:19 2018: [kopano-ical|T2161] [=======] Starting kopano-ical version 8.6.80.493 (pid 2161)
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] ----------------------------------------------------------------------
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Fatal error detected. Please report all following information.
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Application kopano-ical version: 8.6.80.493
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] OS: Linux, release: 4.15.11-xen, version: #1 SMP Mon Mar 19 19:53:13 CET 2018, hardware: x86_64
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Thread name: ZCalDAV[::ffff:
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Peak RSS: 10800
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Pid 2161 caught SIGABRT (6), out of memory or unhandled exception, traceback:
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Backtrace:
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #0. /lib64/libkcutil.so.0(+0x2ad7e) [0x7f02a717dd7e]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #1. /lib64/libkcutil.so.0(+0x208fd) [0x7f02a71738fd]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #2. /lib64/libkcutil.so.0(_ZN2KC23generic_sigsegv_handlerEPNS_8ECLoggerEPKcS3_iPK9siginfo_tPKv+0x1a3) [0x7f02a7173c03]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #3. /lib64/libpthread.so.0(+0xf5e0) [0x7f02a4ddf5e0]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #4. /lib64/libc.so.6(gsignal+0x37) [0x7f02a28d51f7]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #5. /lib64/libc.so.6(abort+0x148) [0x7f02a28d68e8]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #6. /lib64/libc.so.6(+0x74f47) [0x7f02a2914f47]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #7. /lib64/libc.so.6(+0x7c619) [0x7f02a291c619]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #8. /usr/lib64/kopano/libkcclient.so(+0x55975) [0x7f029a81f975]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #9. /usr/lib64/kopano/libkcclient.so(MSGServiceEntry+0x47a) [0x7f029a8b14aa]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #10. /lib64/libmapi.so.1(+0x23e96) [0x7f02a7618e96]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #11. /lib64/libmapi.so.1(+0x36d28) [0x7f02a762bd28]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #12. /lib64/libmapi.so.1(_ZN2KC15HrOpenECSessionEPP12IMAPISessionPKcS4_PKwS6_S4_jS4_S4_S4_+0xc6) [0x7f02a762c256]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #13. /usr/sbin/kopano-ical() [0x41bea6]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #14. /usr/sbin/kopano-ical() [0x408fb2]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #15. /usr/sbin/kopano-ical() [0x409509]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #16. /lib64/libpthread.so.0(+0x7e25) [0x7f02a4dd7e25]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] #17. /lib64/libc.so.6(clone+0x6d) [0x7f02a299834d]
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Signal errno: Success, signal code: -6
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Sender pid: 2161, sender uid: 991, si_status: 0
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] Signal value: 0, faulting address: 0x3df00000871
Fri Apr  6 05:10:01 2018: [ZCalDAV[::ffff:|T4430] [crit   ] When reporting this traceback, please include Linux distribution name (and version), system architecture and Kopano version.

Similar problem with kopano-backup and kopano-stats

]# kopano-backup
*** Error in `/bin/python2': free(): invalid pointer: 0x00007fa138359400 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7c619)[0x7fa144bad619]
/usr/lib64/kopano/libkcclient.so(+0x55975)[0x7fa137918975]
/usr/lib64/kopano/libkcclient.so(MSGServiceEntry+0x47a)[0x7fa1379aa4aa]
/lib64/libmapi.so.1(+0x23e96)[0x7fa13af3be96]
/usr/lib64/python2.7/site-packages/_MAPICore.so(+0x3cc0c)[0x7fa13b805c0c]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x730a)[0x7fa1458fe0ca]
/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7fa1458ffefd]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x663c)[0x*** Error in `7fa1458fd3fc]
/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7fa1458ffefd]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x663c)[0x7fa1458fd3fc]
/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7fa1458ffefd]
/lib64/libpython2.7.so.1.0(+0x7094d)[0x7fa14588994d]
/lib64/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7fa1458649a3]
/lib64/libpython2.7.so.1.0(+0x5a995)[0x7fa145873995]
/lib64/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7fa1458649a3]
/lib64/libpython2.7.so.1.0(+0xa2947)[0x7fa1458bb947]
/lib64/libpython2.7.so.1.0(+0xa165f)[0x7fa1458ba65f]
/lib64/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7fa1458649a3]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x2336)[0x7fa1458f90f6]
/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7fa1458ffefd]
/lib64/libpython2.7.so.1.0(+0x70858)[0x7fa145889858]
/lib64/libpython2.7.so.1.0(PyObject_Call+0x43)[0x7fa1458649a3]
/lib64/libpython2.7.so.1.0(+0x4ba85)[0x7fa145864a85]
/lib64/libpython2.7.so.1.0(PyObject_CallFunction+0x8e)[0x7fa145864b6e]
/lib64/libpython2.7.so.1.0(+0x579fa)[0x7fa1458709fa]
/lib64/libpython2.7.so.1.0(+0x57a68)[0x7fa145870a68]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x42f0)[0x7fa1458fb0b0]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x7fa1458fd57d]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x7fa1458fd57d]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x7fa1458fd57d]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x7fa1458fd57d]
/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7fa1458ffefd]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x663c)[0x7fa1458fd3fc]
/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x7fa1458fd57d]
/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7fa1458ffefd]
/lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7fa145900002]
/lib64/libpython2.7.so.1.0(+0x10043f)[0x7fa14591943f]
/lib64/libpython2.7.so.1.0(PyRun_FileExFlags+0x7e)[0x7fa14591a5fe]
/lib64/libpython2.7.so.1.0(PyRun_SimpleFileExFlags+0xe9)[0x7fa14591b889]
/lib64/libpython2.7.so.1.0(Py_Main+0xc9f)[0x7fa14592ca3f]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fa144b52c05]
/bin/python2[0x40071e]

Greetings,
Joachim

fbartels

i’d guess this is related to https://forum.kopano.io/topic/1245/webapp-3-4-11-1346-login-problem/2. We already did some investigation in that matter and found https://bugzilla.redhat.com/show_bug.cgi?id=1519073 as the potential issue.

No Jira ticket on our side yet, though.

Edit: still no Jira ticket, but a proposed fix is in pr #1864

byteschubser

@fbartels said in Segmentation fault:

Edit: still no Jira ticket, but a proposed fix is in pr #1864

Please share complete link for proposed fix.

Thanks
Uwe

fbartels

Hi @byteschubser ,

Since prs cannot be seen from anyone external the link would not have helped you.

But meanwhile the change was merged with https://stash.kopano.io/projects/KC/repos/kopanocore/commits/ccac80c186a5364440b058fd47949084242c200a

The (old) Jira ticket mentioned in the merge commit is also referenced by an additional pr that is open for https://stash.kopano.io/users/jengelhardt/repos/kc/commits/16b9108441ab637084282a2c3379a00669b8c2ac

jj458

Hi,
how can i see when the fix is included in the nightly build?

Tested core-8.6.80.502_0+52-RHEL_7-x86_64
Problem still exists.

Tnx
Joachim

fbartels

@fbartels said in webapp-3.4.11.1346 login problem:

That’s always the issue with binary builds. You could compile it yourself to know that it’s included or you could watch the master branch to see when it gets merged and once that is done it should be in the next package update.

not yet merged back to master and therefore not included in the packages of this morning https://stash.kopano.io/projects/KC/repos/kopanocore/commits

byteschubser

same here.
core-8.6.80.502_0+52-RHEL_7-x86_64

CentOS 7.4.1708

The server itself is running fine. CLI tool (kopano-backup or kopano-admin) are not usable.

byteschubser

problem still exists.

package: core-8.6.80.538_0%2B56-RHEL_7_PHP_56-x86_64.tar.gz

@byteschubser

for me to core-8.6.80.538_0%2B56-RHEL_7_PHP_56-x86_64.tar.gz

kopano-spooler
kopono-search

wont run!

byteschubser

@ckruijntjens

I need to be more detailed: I have a multi server setup.

kopano-server is running fine. You’re right, kopano-search running on the same machine as kopano-server ends up in a seg fault during start.

kopano-spooler and kopano-dagent running on different machines and these packages are not updated to the “faulty” version. https connection from these components and z-push as well, are working fine. Mail flow in and out is not affected in my setup.

@byteschubser

Hi i have all on one server except for zpush.

Kopano-server runs
Kopano-search not
Kopano-spooler not
Kopano-dagent not

Happy When the problem is resolved inside the packages!

afassl

Having the same issues. Looks like something is broken in libkcinetmapi or one of the other libraries:
System with no update:

kopano-gateway -V

kopano-gateway 8.6.80.45

kopano-gateway -V

kopano-gateway: symbol lookup error: /lib64/libkcinetmapi.so.0: undefined symbol: _ZSt24__throw_out_of_range_fmtPKcz

kopano-dagent -V

kopano-dagent: symbol lookup error: /lib64/libkcinetmapi.so.0: undefined symbol: _ZSt24__throw_out_of_range_fmtPKcz

byteschubser

For me it is not the same issue.

core-8.6.80.590 -> seg fault is fixed, cli tools and kopano-search are running again

but: kopano-dagent: symbol lookup error: /lib64/libkcinetmapi.so.0: undefined symbol: _ZSt24__throw_out_of_range_fmtPKcz

This might be another issue

fbartels

Hi @byteschubser ,

I’ve just deployed a CentOS 7 test environment with 8.6.80.713-76.1 and don’t see such an error in the dagent.

Do you still have the error message?