Getting "dead but pid file exists" while starting the server

[#1]

Hello ,

When i check the status using  Service cloudera-scm-server status 
-> cloudera-scm-server dead but pid file exists

 the maximum number of allowed acquisition attempts (5). Last acquisition attempt exception:
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception😕

I checked the above in the log file.

i have copied the jdbc driver as mentioned in the below link .

http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Instal...

but still i get error . Please help

[#2]

This is solved

[#3]

Hi, how can you address it ? please help me.

[#4]

Which database are you using ? ...
Check whether SELINUX is disabled too

[#5 · Accepted solution]

When using Cloudera Manager, you should start and stop services via the CM
API (by adding a service for your component, etc.) not via the Linux
service commands.

[#6]

Hi,

May I know how it got resolved. I'm also getting the same for Rundeck Server.

[#7]

@Gayathri68,

You need to remove the pid file most likely.

You'll need to find out where the pid file is stored.

Use "strace" to see where it is finding the file if you are on a system where strace can be run

Rundeck is no a Cloudera product, though, so you might check here:

https://rundeck.org/help.html