[GitHub] [bookkeeper] Nicklee007 opened a new issue #3112: Can't start bookie by bookkeeper-daemon.sh, because the last pid occupied by other progress’s thread

[GitBox]

Nicklee007 opened a new issue #3112:
URL: https://github.com/apache/bookkeeper/issues/3112


   **BUG REPORT**
   
   ***Describe the bug***
   After bookie progress is killed or occur some non-normal exit，can't start 
bookie by bin/bookkeeper-daemon.sh, because the last pid occupied by other 
progress’s thread.
   
   ***To Reproduce***
   
   Steps to reproduce the behavior:
   1. Go to directly kill the bookie;
   2. Change the bin/bookkeeper-bookie.pid  to other progress’s one thread pid
   3. bin/bookkeeper-daemon.sh start bookie
   4. See error 'bookie running as process $PREVIOUS_PID.  Stop it first'
   
   ***Expected behavior***
   we failed start broker when the pid in bin/bookkeeper-bookie.pid occupied by 
other progress, but we can start when the pid just occupied by the thread in 
other progress’s.
   
   ***Screenshots***
   start broker by bin/pulsar-daemon script failed, some error 'bookie running 
as process 30210. Stop it first'
   <img width="791" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158438849-3e660a81-0904-4aca-adcf-176f7a2875db.png";>
   
   <img width="683" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158438945-f5b0f861-8ab6-43fd-9539-ab082286cd0e.png";>
   
   but we don't find the progress which pid is 30210
   <img width="602" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158439075-421adf31-a9e3-4a14-9226-99026bc41586.png";>
   
   <img width="928" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158439192-72887222-f929-4cad-891a-523b3e8bbb77.png";>
   
   The pid 30210 is occupied by the pid 30154 progress's one thread.
   <img width="941" alt="image" 
src="https://user-images.githubusercontent.com/84127069/158439416-2a07a433-089b-4608-aff5-dfbb23aa09da.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: issues-unsubscr...@bookkeeper.apache.org

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