No pid file not running

Learn more. Asked 11 years, 2 months ago. Active 2 years, 11 months ago. Viewed 29k times. I am working on ubuntu. I got the error messages while try to restart apache. Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Nikolaidis Fotis Nikolaidis Fotis 2, 11 11 silver badges 13 13 bronze badges. Arenstar Arenstar 3, 2 2 gold badges 24 24 silver badges 34 34 bronze badges. I have tried it but apache2 start shows same errors — user You need to kill what ever is running on port The PID complaint is only because you are trying to stop something that hasnt written a pid..

Or a precompiled version of apache? Log In. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community. It's easy to join and it's free.

Register now while it's still free! Because once a user doesn't have access to the servers and the splunk restart doesn't occur gracefully the services are stopped forever without a manual intervention. Any comment. I imagine the root cause is different but the outcome is similar in that your more frequent stops of the service and resultant forcible stops by splunk itself amplify the PID problem. Have you experienced the PID problem since your recent upgrade to 6.

I am glad splunk forcibly stops itself as a workaround because prior to splunk managing this situation we had to customize our software installation packages for splunk upgrades to include stop, watch and kill after specified time logic so that the software installation upgrade package could complete an upgrade from old splunk to new splunk.

That said, please do create a new thread so that I can close this one and track progress on your question separately! Hi people. I'm using the Splunk version 6. So, I solved this problem just restarting this virtual machine. Stopping splunk helpers Stopped helpers. Removing stale pid file Checking prerequisites Checking http port []: open Checking mgmt port []: open Checking appserver port [ Checking critical directories Done Checking indexes Done Checking conf files for problems Done All preliminary checks passed.

If you get stuck, we're here to help. The misbheavior of 6. This would mean that starting splunk up is not needed, because it is already running, or alternatively it would mean that a splunk shutdown never completed somehow in this case, kill might be appropriate. It seems to be back in Splunk 6. I just had this happen on an Indexer in Prod that was restarted via vmware.

I was able to recreate it in my QA environment. All one needs to do is mock up a pid file with ids from other processes that belong to another user like root.