Hmm, the conf file should not lie (I've never seen it do so), so that searchd
instance should be on port 9313, and we explicitly requested the dev conf file
before, which failed on port 9312.
I guess one thing to check is to stop this running searchd instance, and try
the dev one again, and see if that works. Otherwise, some other process has
9312.
--
Pat
On 19/05/2010, at 1:02 PM, Gordon Yeong wrote:
> 1001 3314 0.0 0.0 29468 768 ? S 12:37 0:00 searchd
> --pidfile --config /home/prod/projects/myApp/config/production.sphinx.conf
> anex 26016 0.0 0.0 7328 868 pts/0 S+ 12:59 0:00 grep
> --color=auto searchd
>
>
> that's really odd because I set port 9313 for the production instance of
> sphinx in the
> "/home/prod/projects/myApp/config/production.sphinx.conf" file.
>
> --------- /home/prod/projects/myApp/config/production.sphinx.conf
>
> searchd
> {
> listen = 127.0.0.1:9313
> log = /home/prod/projects/myApp/log/searchd.log
> query_log = /home/prod/projects/myApp/log/searchd.query.log
> pid_file = /home/prod/projects/myApp/log/searchd.production.pid
> }
>
>
>
>
> On 19 May 2010 12:09, Pat Allan <[email protected]> wrote:
> Looks like there's already something on port 9312 - and I'm guessing it's
> Sphinx. What's the output of:
> ps aux | grep searchd
>
>
> --
> 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.
--
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.
