title: Issues with running two instances of searchd
body: <p>I have just updated our Sphinx server from 1.10-beta to 2.0.6-release, and now I have run into some issues with <code>searchd</code>. Previously we were able to run two instances of <code>searchd</code> next to each other by specifying two different config-files, i.e:</p>
  
  <pre><code>searchd --config /etc/sphinx/sphinx.conf
  searchd --config /etc/sphinx/sphinx.staging.conf
  </code></pre>
  
  <p>sphinx.conf listens to <code>9306:mysql41</code>, and <code>9312</code>, while sphinx.staging.conf listens to <code>9307:mysql41</code> and <code>9313</code>.</p>
  
  <p>After we updated to 2.0.6 however, a second instance is never started. Or rather.. the output makes it seem like it starts, and a pid-file is created etc. But for some reason only the first searchd instance keeps running, and the second seems to shutdown right away. So while trying to run <code>searchd --config /etc/sphinx/sphinx.conf</code> twice (if that was the first one started) complains that the pid-file is in use, trying to run <code>searchd --config /etc/sphinx/sphinx.staging.conf</code> (if that is the second started instance) "starts" the daemon again and again, only no new process is created..
  Note that if I switch these commands around when first creating the process, then <code>sphinx.conf</code> is the instance not really started.</p>
  
  <p>I have checked, and rechecked, that these ports are only used by <code>searchd</code>.</p>
  
  <p>Does anyone have any idea of what I can do/try next? I've installed it from source on ubuntu 10.04 LTS with:</p>
  
  <pre><code>./configure --prefix /etc/sphinx --with-mysql --enable-id64 --with-libstemmer
  make -j4 install
  </code></pre>