Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling signal 11 Crashing searchd #260

Closed
abhijo89-uc opened this issue Aug 13, 2019 · 3 comments
Closed

Handling signal 11 Crashing searchd #260

abhijo89-uc opened this issue Aug 13, 2019 · 3 comments

Comments

@abhijo89-uc
Copy link

This is the log when it crached
[Tue Aug 13 09:37:23.190 2019] [36596] WARNING: wordlist size mismatch (size=18, checkpoints=0)

--- crashed invalid query ---

--- request dump end ---
Manticore 3.1.0 445e806@190716 release
Handling signal 11
-------------- backtrace begins here ---------------
Program compiled with 7
Configured with flags: Configured by CMake with these definitions: -DCMAKE_BUILD_TYPE=RelWithDebInfo -DDISTR_BUILD=bionic -DDL_UNIXODBC=1 -DUNIXODBC_LIB=libodbc.so.2 -DDL_EXPAT=1 -DEXPAT_LIB=libexpat.so.1 -DUSE_LIBICONV=1 -DDL_MYSQL=1 -DMYSQL_LIB=libmysqlclient.so.20 -DDL_PGSQL=1 -DPGSQL_LIB=libpq.so.5 -DLOCALDATADIR=/var/data -DFULL_SHARE_DIR=/usr/share/manticore -DICU_IS_SHARED=1 -DDL_ICU=1 -DICU_LIB=libicuuc.so.60 -DUSE_BISON=ON -DUSE_FLEX=ON -DUSE_SYSLOG=1 -DWITH_EXPAT=1 -DWITH_ICONV=ON -DWITH_MYSQL=1 -DWITH_ODBC=ON -DWITH_PGSQL=1 -DWITH_RE2=1 -DWITH_STEMMER=1 -DWITH_ZLIB=ON -DGALERA_SOVERSION=31 -DSYSCONFDIR=/etc/sphinxsearch
Host OS is Linux runner-ed2dce3a-project-3858465-concurrent-0 4.19.23-coreos-r1 #1 SMP Mon Feb 25 23:40:01 -00 2019 x86_64 x86_64 x86_64 GNU/Linux
Stack bottom = 0x7fc09c36fed7, thread stack size = 0x20000
Trying manual backtrace:
Frame pointer is null, manual backtrace failed (did you build with -fomit-frame-pointer?)
Trying system backtrace:
begin of system symbols:
/usr/bin/searchd(_Z12sphBacktraceib+0xcb)[0x564cfeb4579b]
/usr/bin/searchd(_ZN16SphCrashLogger_c11HandleCrashEi+0x183)[0x564cfe9af403]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fc0f10bf890]
/usr/bin/searchd(_ZN9RtIndex_c13ForceRamFlushEb+0x34)[0x564cfec680f4]
/usr/bin/searchd(+0x276587)[0x564cfea7a587]
/usr/bin/searchd(_ZN10LazyJobs_c15TheadPoolWorkerEPv+0x332)[0x564cfea75462]
/usr/bin/searchd(_Z20sphThreadProcWrapperPv+0x35)[0x564cfeb4bd85]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7fc0f10b46db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fc0efe7988f]
-------------- backtrace ends here ---------------
Please, create a bug report in our bug tracker (https://github.com/manticoresoftware/manticore/issues)
and attach there:
a) searchd log, b) searchd binary, c) searchd symbols.
Look into the chapter 'Reporting bugs' in the documentation
(http://docs.manticoresearch.com/latest/html/reporting_bugs.html)
[Tue Aug 13 09:44:55.554 2019] [36595] watchdog: got USR1, performing dump of child's stack
Will run gdb on /usr/bin/searchd, pid 36596
--- 0 active threads ---
------- CRASH DUMP END -------

@tomatolog
Copy link
Contributor

could you start daemon with --coredump option and also check unlimit -c is unlimited for user that starts daemon.

I'd like to investigate core dump of the crash as BT you provided from searchd.log seems has limited info.

Could you also provide more lines from searchd.log as I'd like to see the crash was on daemon start or daemon started some time ago?

@abhijo89-uc
Copy link
Author

I could not reproduce the issue after this!

@manticoresearch
Copy link
Contributor

Closing as non-reproducible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants