Issue with kopano-dagent?
-
When running some email tests on a test server, kopano-dagent keeps crashing with the following showing in the log:
2021-01-26T15:03:13.412087: [kopano-dagent|T11957] [=======] Starting kopano-dagent version 11.0.0 (pid 11957 uid 0) (LMTP mode) 2021-01-26T15:03:13.469601: [kopano-dagent|T11957] [=======] Starting kopano-dagent version 11.0.0 (pid 11957 uid 114) (LMTP mode) 2021-01-26T15:03:56.392567: [kopano-dagent|T12176] [crit ] ---------------------------------------------------------------------- 2021-01-26T15:03:56.392678: [kopano-dagent|T12176] [crit ] Fatal error detected. Please report all following information. 2021-01-26T15:03:56.392733: [kopano-dagent|T12176] [crit ] kopano-dagent 11.0.0 2021-01-26T15:03:56.392798: [kopano-dagent|T12176] [crit ] OS: Ubuntu 20.04.1 LTS (Linux 5.4.0-64-generic x86_64) 2021-01-26T15:03:56.392872: [kopano-dagent|T12176] [crit ] Thread name: kopano-dagent 2021-01-26T15:03:56.392950: [kopano-dagent|T12176] [crit ] Peak RSS: 24796 2021-01-26T15:03:56.393016: [kopano-dagent|T12176] [crit ] Pid 11957 caught SIGABRT (6), out of memory or unhandled exception, traceback: 2021-01-26T15:03:56.393165: [kopano-dagent|T12176] [crit ] Backtrace: 2021-01-26T15:03:56.394025: [kopano-dagent|T12176] [crit ] f0. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(+0x50c14) [0x7f5d01fa6c14] 2021-01-26T15:03:56.394098: [kopano-dagent|T12176] [crit ] f1. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(+0x37216) [0x7f5d01f8d216] 2021-01-26T15:03:56.394151: [kopano-dagent|T12176] [crit ] f2. /usr/lib/x86_64-linux-gnu/libkcutil.so.0(+0x38c54) [0x7f5d01f8ec54] 2021-01-26T15:03:56.394204: [kopano-dagent|T12176] [crit ] f3. /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7f5d01edb3c0] 2021-01-26T15:03:56.394262: [kopano-dagent|T12176] [crit ] f4. /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb) [0x7f5d0193018b] 2021-01-26T15:03:56.394314: [kopano-dagent|T12176] [crit ] f5. /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b) [0x7f5d0190f859] 2021-01-26T15:03:56.394370: [kopano-dagent|T12176] [crit ] f6. /lib/x86_64-linux-gnu/libc.so.6(+0x903ee) [0x7f5d0197a3ee] 2021-01-26T15:03:56.394429: [kopano-dagent|T12176] [crit ] f7. /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a) [0x7f5d01a1cb4a] 2021-01-26T15:03:56.394481: [kopano-dagent|T12176] [crit ] f8. /lib/x86_64-linux-gnu/libc.so.6(+0x1313e6) [0x7f5d01a1b3e6] 2021-01-26T15:03:56.394532: [kopano-dagent|T12176] [crit ] f9. /lib/x86_64-linux-gnu/libc.so.6(__snprintf_chk+0xc5) [0x7f5d01a1aff5] 2021-01-26T15:03:56.394589: [kopano-dagent|T12176] [crit ] f10. /usr/sbin/kopano-dagent(+0x1695e) [0x55dfef8a695e] 2021-01-26T15:03:56.394644: [kopano-dagent|T12176] [crit ] f11. /usr/sbin/kopano-dagent(+0x1853a) [0x55dfef8a853a] 2021-01-26T15:03:56.394702: [kopano-dagent|T12176] [crit ] f12. /usr/sbin/kopano-dagent(+0x1c940) [0x55dfef8ac940] 2021-01-26T15:03:56.394758: [kopano-dagent|T12176] [crit ] f13. /usr/sbin/kopano-dagent(+0x207fc) [0x55dfef8b07fc] 2021-01-26T15:03:56.394815: [kopano-dagent|T12176] [crit ] f14. /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7f5d01ecf609] 2021-01-26T15:03:56.394869: [kopano-dagent|T12176] [crit ] f15. /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f5d01a0c293] 2021-01-26T15:03:56.394941: [kopano-dagent|T12176] [crit ] Signal errno: Success, signal code: -6 2021-01-26T15:03:56.394996: [kopano-dagent|T12176] [crit ] Sender pid: 11957, sender uid: 114, si_status: 0 2021-01-26T15:03:56.395052: [kopano-dagent|T12176] [crit ] Signal value: 0, faulting address: 0x7200002eb5
Is there something I can try?
Am I missing something, or should I wait until the next release?Thank you
-
Updated to today’s version (11.0.0.6) and still happening.
Any advise please?
Thanks
Chris
-
I think this is to do with OOF - i’ve turned it off, and now it seems to be working…
Not a major hassle, as we don’t tend to use OOF, but this is the first time i’ve seen it crash the setup
Thanks
C
-
@chipsuk that was already reported at https://forum.kopano.io/topic/3591/oof-part-of-kopano-dagent-broken/8
-
@chipsuk Yes, this is related to OOF. I’ve fixed it yesterday and it’ll hopefully be merged to master soon. :)
-
Thanks for your help
Will update when able
-
@chipsuk No worries. FYI this fix has just been merged, so it should show up in the next nightly.