I wouldn't expect this segmentation fault to be connected to how Sphinx logs 
things. Either way, this is very much a Sphinx issue, and I'm sure the Sphinx 
team would appreciate knowing about the segmentation fault (and perhaps have 
suggestions on how to work around it).

I'd recommend either logging a bug:
http://sphinxsearch.com/bugs/my_view_page.php

Or asking about the appropriate behaviour on their forum:
http://sphinxsearch.com/forum/

Good luck!

-- 
Pat

On 30/07/2013, at 8:38 PM, [email protected] wrote:

> 
> hello~ I made a test with 10000000 records, and found out the words segmented 
> can't contain the square bracket '[' or ']', or the indexing would be abort.
> 
> here, I have a test wiht mmseg.  
> 
> echo "爱丁堡[湘城]湘城凤阳路"  > sw.txt
> 
> excute the command "/usr/local/sphinx/bin/mmseg -d lib/ sw.txt" 
> 
> the result was "Segmentation fault".
> 
> besides,
> sphinx -> querying -> Prototype: function Query ( $query, $index="*", 
> $comment="" )
> which says :"the contents of $comment are sent to the query log, marked in 
> square brackets, just before the search terms, which can be very useful for 
> debugging."
> 
> is the problem just for that? 
> 
> 
> 
> 
> 
> 在 2013年7月26日星期五UTC+8下午6时34分09秒,Pat Allan写道:
> What's the output you're seeing, even if there's no error message? Given the 
> size of the index files, could it be related to hard drive space on your 
> computer? 
> 
> Also: What Thinking Sphinx is doing is running the following command 
> (adapting for each environment and provided settings accordingly): 
> 
>   indexer --config config/development.sphinx.conf 
> 
> It also adds the --rotate flag if Sphinx is running (so the daemon loads the 
> updated index files). 
> 
> -- 
> Pat 
> 
> On 26/07/2013, at 7:59 PM, [email protected] wrote: 
> 
> > there are two tables in my databases. 
> > table one has 20 million records, and table two has 50million records. 
> > 
> > with the command "INDEX_ONLY=true rake ts:index" , table one's index 
> > successfully was made, the size of index is about 18G. 
> > but,when turn to table two, it abort with part index and no error message. 
> > here, I just list the results in my indices_location 
> > 
> > ---------- 
> > -rw-r--r-- 1 ryang ryang 288M Jul 26 16:08 table_two_core.spa 
> > -rw-r--r-- 1 ryang ryang    0 Jul 26 15:48 table_two_core.spl 
> > -rw-r--r-- 1 ryang ryang 3.1G Jul 26 16:08 table_two_core.spp 
> > -rw-r--r-- 1 ryang ryang    0 Jul 26 15:48 table_two_core.tmp0 
> > -rw-r--r-- 1 ryang ryang    0 Jul 26 15:48 table_two_core.tmp4 
> > -rw-r--r-- 1 ryang ryang    0 Jul 26 15:48 table_two_core.tmp7 
> > 
> > --------- 
> > and "rake ts:index --trace" without more detail infos. 
> > 
> > I don't know, what's wrong with it, and how I can capture the exception. 
> > Is there any arguments with the command "rake ts:index" to debug it? 
> > now, I really go mad~ 
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "Thinking Sphinx" group. 
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to [email protected]. 
> > To post to this group, send email to [email protected]. 
> > Visit this group at http://groups.google.com/group/thinking-sphinx. 
> > For more options, visit https://groups.google.com/groups/opt_out. 
> >   
> >   
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Thinking Sphinx" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/thinking-sphinx.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/thinking-sphinx.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to