Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

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

avatar
Rising Star

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

 

 

Thanks
Bala
1 ACCEPTED SOLUTION

avatar
Expert Contributor
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.

View solution in original post

6 REPLIES 6

avatar
Rising Star
This is solved
Thanks
Bala

avatar
Explorer

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

avatar
Rising Star
Which database are you using ? ...
Check whether SELINUX is disabled too
Thanks
Bala

avatar
Expert Contributor
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.

avatar
New Contributor

Hi,

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

 

avatar
Master Guru

@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