You are likely hitting the issue described in SERVER-6008 - there is a fix coming in the next release (2.4.7) but that has not been released at the time of writing this answer.
The workaround is to manually get, and use, the patched init script in the meantime. You can see that init script here (change is checked into 2.5.2):