|
|
Produce a stack trace, we don't have this issue. |
|
zhb
2020-07-08 12:46
reporter
~0014465
Last edited: 2020-07-08 12:51
|
Following this tutorial: https://sogo.nu/support/faq/how-do-i-debug-sogo.html
Running on CentOS 7:
# su -s /bin/bash sogo
bash-4.2$ gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 20000 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-119.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/sogod...Reading symbols from /usr/sbin/sogod...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install sogo-4.3.2.20200708-1.el7.x86_64
(gdb) r
Starting program: /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 20000 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff54c19cf in GSToUnicode () from /lib64/libgnustep-base.so.1.24
|
|
|
|
Show the full stack trace, not just the last frame. |
|
|
|
That's all i got. let me show you the "full" stack trace:
bash-4.2$ gdb --args /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 20000 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-119.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/sogod...Reading symbols from /usr/sbin/sogod...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install sogo-4.3.2.20200708-1.el7.x86_64
(gdb) r
Starting program: /usr/sbin/sogod -WOUseWatchDog NO -WONoDetach YES -WOPort 20000 -WOWorkersCount 1 -WOLogFile - -WOPidFile /tmp/sogo.pid
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff54c19cf in GSToUnicode () from /lib64/libgnustep-base.so.1.24
(gdb) b [NSException raise]
Breakpoint 1 at 0x7ffff536c930
(gdb) b abort
Breakpoint 2 at 0x7ffff465c930 (2 locations)
(gdb) c
Continuing.
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
|
|
|
|
sogod exits (Segmentation fault) when i typed the first command - "r". |
|
|
|
Type "bt". |
|
|
|
Full stack attached. Thank you very much for helping. :) |
|
|
|
Dear @ludovic,
Could you help take a look at the full trace stack? Thanks. :) |
|
|
|
Looks like a GNUstep issue, not a SOGo issue. Check your sogo.conf for "weird" characters. |
|
|
|
You mean sogo.conf file may contain invalid characters somewhere? |
|
|
|
Yes |
|
|
|
Any recommend tool/command to help check invalid character in sogo.conf? Or have to check line by line manually? |
|
|
|
Byte by byte. |
|
|
|
No idea how to do this. :( |
|
|
|
I copied sogo.conf from a working machine, replaced SQL related values, restart sogod service. In syslog, i got this:
Jul 9 19:38:50 mail kernel: sogod[15385]: segfault at 7ffd7bb86ff8 ip 00007feac7f419eb sp 00007ffd7bb86ff0 error 6 in libgnustep-base.so.1.24.9[7feac7baf000+4dc000]
Jul 9 19:38:50 mail systemd: Can't open PID file /var/run/sogo/sogo.pid (yet?) after start: No such file or directory
Directory /var/run/sogo/ is set to 0777 (for testing purpose), still this error. It also seems not caused by "weird" characters in sogo.conf since same config file works on another CentOS 7 server.
Any idea? |
|
|
|
Then try the same GNUstep version as the other CentOS 7 box. As I said, it's not a SOGo bug. |
|
|
|
Both runs same gnustep version from EPEL repo. |
|
|
|
Eventually got SOGo running, the fix is just removing ~sogo/GNUStep/ directory. |
|
