searchd的异常日志，跟现有索引文件有关

每次searchd接收到索引的rotate信号后，都会出现这段异常。这个异常很规律，都是跟在这个索引之后。其实“ '/usr/local/mmseg3/etc/wordforms.txt' differs from the original” 没有关系的，应该是加载test 这个索引的时候出现问题的。最终重新索引了test，发现没有这个异常日志了。

[Sat Jun 15 18:40:12.164 2013] [10180] WARNING: rotating index: test: '/usr/local/mmseg3/etc/wordforms.txt' differs from the original

------- FATAL: CRASH DUMP -------

[Sat Jun 15 18:40:12.035 2013] [10180]

--- crashed SphinxAPI request dump ---

--- request dump end ---

Sphinx 2.0.4-id64-dev (r1575)

-------------- backtrace begins here ---------------

Program compiled with gcc 4.4.6

Host OS is Linux sphinx52.quanzhi.com 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

Stack bottom = 0x7fff2bf24bcf, thread stack size = 0x14000

begin of manual backtrace:

Something wrong with thread stack, backtrace may be incorrect (fp=7fff2bf24bcf)

Stack looks OK, attempting backtrace.

0

begin of system backtrace:

begin of system symbols:

/usr/local/coreseek/bin/searchd(_Z12sphBacktraceib+0x95)[0x590b15]

/usr/local/coreseek/bin/searchd(_ZN16SphCrashLogger_c11HandleCrashEi+0x18c)[0x47257c]

/lib64/libpthread.so.0[0x300580f4a0]

/usr/local/coreseek/bin/searchd(_ZN13CSphIndex_VLN7PrereadEv+0x427)[0x4e3e07]

/usr/local/coreseek/bin/searchd(_Z26SeamlessTryToForkPrereaderv+0x540)[0x495bd0]

/usr/local/coreseek/bin/searchd(_Z21SeamlessForkPrereaderv+0x4d)[0x495d7d]

/usr/local/coreseek/bin/searchd(_Z11CheckRotatev+0x6ed)[0x49ef8d]

/usr/local/coreseek/bin/searchd(_Z8TickHeadP22CSphProcessSharedMutex+0x7a)[0x4b1cea]

/usr/local/coreseek/bin/searchd(_Z11ServiceMainiPPc+0x186c)[0x4b3b1c]

/usr/local/coreseek/bin/searchd(main+0x54)[0x4b56d4]

/lib64/libc.so.6(__libc_start_main+0xfd)[0x300541ecdd]

/usr/local/coreseek/bin/searchd[0x46f839]

Backtrace looks OK. Now you have to do following steps:

  1. Run the command over the crashed binary (for example, 'indexer'):

     nm -n indexer > indexer.sym

  2. Attach the binary, generated .sym and the text of backtrace (see above) to the bug report.

Also you can read the section about resolving backtraces in the documentation.

-------------- backtrace ends here ---------------

------- CRASH DUMP END -------