OK. I think I've found what's wrong.
After I commented out the config.threadsafe! line in production.rb
everything seems to work fine now.
I have no idea what's going on under the hood, but since it works and
I really don't need threading in my app, I'm pretty happy with just
that.

If there's anyone with some kind of explanation of why the above
mentioned setting causes this kind of problem I'd like to hear it.
Pat, thanks for your guidance.

Milan

On Jul 8, 5:42 pm, Milan Novota <[email protected]> wrote:
> Commenting out the observers doesn't help.
> Everything seems to work just fine in the dev environment. That's
> interesting.
> I can't see any meaningful explanation for this so far.
>
> -- Milan
>
> On 8 July 2010 17:13, Pat Allan <[email protected]> wrote:
>
> > What happens if you comment out the observers line in production.rb? And
> > does the issue happen in the dev environment as well?
>
> > --
> > Pat
>
> > On 08/07/2010, at 6:06 PM, milan wrote:
>
> > > Pat,
>
> > > I tried 1.3.17 but with the same result as with 1.3.18 (i.e. almost
> > > empty config file is generated).
> > > Here is my environment.rb file:
> >https://gist.github.com/5fd3260816e0771ece66
> > > and my production.rb file here:
> >https://gist.github.com/00fda09b20184495e672
> > > I don't think there's anything interesting there, though.
>
> > > Thanks.
>
> > > On Jul 7, 5:13 pm, Pat Allan <[email protected]> wrote:
> > >> Right, nothing out of the ordinary there. Can you try 1.3.17? I think
> > there was a bug in earlier versions before that with models being invoked
> > twice and thus indexes being duplicated. Which is the complete opposite to
> > your current problem with 1.3.18, but I wonder if it's a similar cause...
> > ie: something with how models are being loaded...
>
> > >> Can you share your environment.rb and production.rb files? Perhaps in a
> > gist?
>
> > >> (I'm not going to be so prompt with my next response - it's past 1am
> > here, time for sleep ;)
>
> > >> --
> > >> Pat
>
> > >> On 08/07/2010, at 1:10 AM, milan wrote:
>
> > >>> Here we go:
>
> > >>>  define_index do
> > >>>    indexes subject, :sortable => true
> > >>>    indexes [contact.last_name, contact.first_name], :as
> > >>> => :contact_full_name, :sortable => true
> > >>>    indexes [owner.last_name, owner.first_name], :as
> > >>> => :owner_full_name, :sortable => true
> > >>>    indexes start_date
> > >>>    indexes start_time
> > >>>    indexes status
> > >>>    indexes description
> > >>>    indexes actable.name, :as => :actable_name
> > >>>    indexes result
> > >>>    indexes owner_id
> > >>>    has owner_id, actable_id
> > >>>    set_property :field_weights => {"subject" => 100,
> > >>> "contact_full_name" => 90, "description" => 80 }
> > >>>    set_property :delta => true
> > >>>  end
>
> > >>> My previous version was 1.1.6
>
> > >>> On Jul 7, 4:59 pm, Pat Allan <[email protected]> wrote:
> > >>>> Hmm... let's take a look at your Activity define_index block. Also:
> > which version of TS have you dropped back to? 1.3.17? Or something earlier?
>
> > >>>> --
> > >>>> Pat
>
> > >>>> On 08/07/2010, at 12:15 AM, milan wrote:
>
> > >>>>> Hi Pat,
>
> > >>>>> thanks for the hint Pat, I tried to run the task on an older branch
> > >>>>> and what I'm getting now is this: the configuration runs OK, but then
> > >>>>> when I'm trying to run the rake:index task I'm getting this:
>
> > >>>>> ERROR: section 'activity_delta_0' (type='source') already exists in /
> > >>>>> Users/milan/Projects/honeybee/config/production.sphinx.conf line 231
> > >>>>> col 25.
> > >>>>> FATAL: failed to parse config file '/Users/milan/Projects/honeybee/
> > >>>>> config/production.sphinx.conf'
>
> > >>>>> I don't think there's anything special about my indexes (they used to
> > >>>>> work smoothly - I don't remember changing anything). The only special
> > >>>>> thing about this particular model is that it's a STI model.
>
> > >>>>> Thanks,
> > >>>>> Milan
>
> > >>>>> On Jul 7, 3:42 pm, Pat Allan <[email protected]> wrote:
> > >>>>>> Hi Milan
>
> > >>>>>> What version were you running previously? If it wasn't 1.3.17, can
> > you try dropping down to that and see if the problem still occurs?
>
> > >>>>>> Also: what version of Rails are you running? Do you have anything
> > particularly complex happening in your indexes, or in the server setup? Are
> > you doing anything out of the ordinary with model loading?
>
> > >>>>>> Cheers
>
> > >>>>>> --
> > >>>>>> Pat
>
> > >>>>>> On 07/07/2010, at 11:05 PM, milan wrote:
>
> > >>>>>>> Hey everyone,
>
> > >>>>>>> I just upgraded to version 1.3.18 (using gem) and the configuration
> > >>>>>>> rake task doesn't seem to work properly. After I run rake ts:conf
> > all
> > >>>>>>> I get is this (in config/production.sphinx.conf):
>
> > >>>>>>> indexer
> > >>>>>>> {
> > >>>>>>> }
>
> > >>>>>>> searchd
> > >>>>>>> {
> > >>>>>>>  listen = 127.0.0.1:9312
> > >>>>>>>  log = /Users/milan/Projects/honeybee/log/searchd.log
> > >>>>>>>  query_log = /Users/milan/Projects/honeybee/log/searchd.query.log
> > >>>>>>>  pid_file = /home/honeybee/production/shared/pids/searchd.pid
> > >>>>>>> }
>
> > >>>>>>> Obviously, there's something missing here.
> > >>>>>>> Any ideas what might've gone wrong?
> > >>>>>>> (I'm using Sphinx 0.9.9-release (r2117)
>
> > >>>>>>> Thanks!
> > >>>>>>> Milan
>
> > >>>>>>> --
> > >>>>>>> You received this message because you are subscribed to the Google
> > Groups "Thinking Sphinx" group.
> > >>>>>>> To post to this group, send email to
> > [email protected].
> > >>>>>>> To unsubscribe from this group, send email to
> > [email protected]<thinking-sphinx%[email protected]>
> > .
> > >>>>>>> For more options, visit this group athttp://
> > groups.google.com/group/thinking-sphinx?hl=en.
>
> > >>>>> --
> > >>>>> You received this message because you are subscribed to the Google
> > Groups "Thinking Sphinx" group.
> > >>>>> To post to this group, send email to
> > [email protected].
> > >>>>> To unsubscribe from this group, send email to
> > [email protected]<thinking-sphinx%[email protected]>
> > .
> > >>>>> For more options, visit this group athttp://
> > groups.google.com/group/thinking-sphinx?hl=en.
>
> > >>> --
> > >>> You received this message because you are subscribed to the Google
> > Groups "Thinking Sphinx" group.
> > >>> To post to this group, send email to [email protected].
> > >>> To unsubscribe from this group, send email to
> > [email protected]<thinking-sphinx%[email protected]>
> > .
> > >>> For more options, visit this group athttp://
> > groups.google.com/group/thinking-sphinx?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > "Thinking Sphinx" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to
> > [email protected]<thinking-sphinx%[email protected]>
> > .
> > > For more options, visit this group at
> >http://groups.google.com/group/thinking-sphinx?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Thinking Sphinx" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<thinking-sphinx%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/thinking-sphinx?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en.

Reply via email to