[GitHub] [pulsar] Nicklee007 opened a new issue #14700: Can't start broker by pulsar-daemon script, because the last PID occupied by other progress’s thread

[GitBox]

Nicklee007 opened a new issue #14700:
URL: https://github.com/apache/pulsar/issues/14700


   **Describe the bug**
   After broker progress is killed or occur some non-normal exit，can't start 
broker by bin/pulsar-daemon script, because the last pid occupied by other 
progress’s thread.
   
   **Expected behavior**
   we failed start broker when the pid in bin/pulsar-broker.pid occupied by 
other progress, but we can start when the pid just occupied by other progress’s 
thread.
   
   **Screenshots**
   start broker by bin/pulsar-daemon script failed, some error 'broker running 
as process 8751. Stop it first.'
   <img width="909" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158420768-e020e5bc-795e-4f5d-b411-3eef784601e4.png";>
   
   but we don't find the process which pid is 8751
   <img width="665" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158421323-7145d400-1f96-44b3-ae5a-6a40aaccb68b.png";>
   
   <img width="554" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158421522-62ec167d-3e61-4dac-b5a0-9b7465f202b4.png";>
   
   The pid 8751 is occupied by the pid 8745 progress's one thread.
   <img width="858" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158421842-f0d912f7-2fbf-4d75-8a93-4a0f78a3b2de.png";>
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org