On 17-01-24 07:14 AM, Ludovic Marcotte (lmarco...@inverse.ca) wrote:
On 2017-01-24 1:42 AM, Greg Kunyavsky (gr...@kgbconsulting.ca) wrote:
I am no closer to finding the issue, but I am getting this message
pretty consistently
*** stack smashing detected ***: /usr/sbin/sogod terminated
But no core file.
Try starting SOGo from gdb - so don't reduce the number of workers,
just start it from gdb (ie., the parent process).
I followed the FAQ to install -dbg packages and run GDB. I only had to
change -WOUseWatchDog to YES, otherwise only 1 worker runs instead of
600. Unfortunately the stack trace does not look very useful. Any
suggestions?
(gdb) r
Starting program: /usr/sbin/sogod -WOUseWatchDog YES -WONoDetach YES
-WOPort 20000 -WOWorkersCount 600 -WOLogFile
/var/log/sogo/sogo-crash.log -WOPidFile /tmp/sogo.pid
^CQuit
(gdb) b [NSException raise]
Function "[NSException raise]" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 ([NSException raise]) pending.
(gdb) b abort
Breakpoint 2 at 0x55555555a7e0
(gdb) c
Continuing.
*** stack smashing detected ***: /usr/sbin/sogod terminated
Program received signal SIGABRT, Aborted.
0x00007ffff4448428 in ?? ()
(gdb) bt
#0 0x00007ffff4448428 in ?? ()
#1 0x00007ffff444a02a in ?? ()
#2 0x0000000000000020 in ?? ()
#3 0x0000000000000000 in ?? ()
(gdb) bt full
#0 0x00007ffff4448428 in ?? ()
No symbol table info available.
#1 0x00007ffff444a02a in ?? ()
No symbol table info available.
#2 0x0000000000000020 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)
--
users@sogo.nu
https://inverse.ca/sogo/lists
