Unable to stop bitbucket instance getting the error No process was found for PID

[mail2sebastianpeter]

Hi there,

I am unable to stop my bitbucket instance: while i try to stop the bitbucket instance its showing below error: 

[****user@****Linux bin]$ ./stop-bitbucket.sh
Stopping Atlassian Bitbucket as the current user
No process was found for PID 123781, or the current user cannot signal it

No PID file was found for bundled Elasticsearch

Its a test Environment and no external database are configured.

Could you please suggest a way to stop the instance.

Thanks,

Sebastian 

[mail2sebastianpeter · Accepted solution]

Hi,

I have resolved this issue by executing the command lsof -i:7990 for finding the Bitbucket process id and then kill the bitbucket process by executing the command kill -9 <process id>

[Jimmy Seddon]

I'm glad you were able to figure out how to resolve your issue.

[sara]

I believe its a permission issue.Can you switch to sudo and do this?

[mail2sebastianpeter]

Hi @sara 

I tried with Sudo also but again the same message is coming.

[kamrulhussain]

I'm also coming across the same issue. 

ps -ef | grep Elasticsearch
svc_scm+ 42724 35758 0 10:20 pts/0 00:00:00 grep --color=auto Elasticsearch
svc_scm+ 87181 1 0 Aug29 ?

kill -9 35758
Killed

./stop-bitbucket.sh
Stopping Atlassian Bitbucket as the current user
No process was found for PID 110517, or the current user cannot signal it

[Jimmy Seddon]

Hi @mail2sebastianpeter,

Since it's complaining about Elasticsearch and as you have said this is a test server, I'd recommend:

ps -ef | grep Elasticsearch

to get the process id that Elasticsearch is running as, then kill -9 against that process id to get it to terminate the search process.  Then try running the ./stop-bitbucket.sh again.

If you run into a simialar error with the bitbucket server proces repeat the same steps again for the bitbucket server process and that should shut things down.

I hope that helps!

-James

[mail2sebastianpeter]

Hi @Jimmy Seddon 

As you suggested I have run ps -ef | grep Elasticsearch and the output is given below but when I terminate the process 36297 then the putty will terminate. Do I need to kill the process 81292 instead of 36297?

[build***@**TestLinux bin]$ ps -ef | grep Elasticsearch

build**+  36520  36297  0 10:50 pts/0    00:00:00 grep --color=auto Elasticsearch

build***+  81292      1  0  2018 ?        06:15:02 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0 

Thanks,

Sebastian

[Jimmy Seddon]

Hi @mail2sebastianpeter,

Yes looking at the output it looks like 36297 was the pid of the process that was running when you ran grep looking for Elasticsearch.

81292 looks like an instance of Java which is more likely to be something that Atlassian is running.

Try killing that and see if that helps.

-James

[mail2sebastianpeter]

Hi @Jimmy Seddon 

I have tried kill as you suggested but that wont help below are the result after kill

[root@**TestLinux bin]# ./stop-bitbucket.sh
Stopping Atlassian Bitbucket as the current user
No process was found for PID 123781, or the current user cannot signal it

No PID file was found for bundled Elasticsearch
[root@**TestLinux bin]# ps -ef | grep Elasticsearch
root 72298 59155 0 15:32 pts/0 00:00:00 grep --color=auto Elasticsearch