Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently upgrade a VM to Redhat 5 and moved Sphinx Search to that server. For some reason when I try to start Sphinx, the startup script fails to push the searchd process to the background. I created a test script with a minimal version of the startup call, which is as follows:

. /etc/rc.d/init.d/functions
daemon /usr/local/sphinx/bin/searchd --config

The searchd process starts and I get output that indicates it is listening on the correct IP:port, but the process never returns.

The process that is hanging is in the daemon call, and ps shows it as:

/bin/bash -c ulimit -S -c 0 >/dev/null 2>&1 ; /usr/local/sphinx/bin/searchd --config

Any ideas on what might be causing this or how to troubleshoot? We use the same process on about a dozen other servers running Redhat 4 which work fine (although the process created by daemon uses initlog, so it is different).

share|improve this question

Turns out that there was nothing wrong with the init script, but that sphinx searchd was taking a very long time to start. Insufficient memory was allocated on the VM, so it was having problems starting up with the large indexes. Increased the memory allocation and works fine now.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.