Support Questions

Find answers, ask questions, and share your expertise

host acquiring installation lock forever

avatar
New Contributor

Hello, all the masters here!

 
am facing the problem of acquiring installation lock when installing cloudera manager for the first time, i did some googling but nothing works for me 😞
 
i have four computers, etc/hosts like:
 
127.0.0.1 localhost.localdomain localhost


172.16.34.143 cluster2.test.com cluster2
172.16.34.140 cluster3.test.com cluster3
172.16.34.139 cluster4.test.com cluster4
172.16.34.141 cluster5.test.com cluster5
 
and etc/sysconfig/network is set accordingly, i managed to have a host installation done which is the cluster2 of ip 172.16.34.143.
 
and the rest three hosts are all stuck in Acquiring installation lock procedure, for like hours!
 
the detail output is like:
 
 
/tmp/scm_prepare_node.bulkkxpo
using SSH_CLIENT to get the SCM hostname: 172.16.34.143 33121 22
opening logging file desciptor
 
Starting installation script...
 
Acquiring installation lock...
 
BEGIN flock 4
 
Can anyone help me with this problem?
Help would be highly appreciated! Thanks in advance!
2 ACCEPTED SOLUTIONS

avatar
Mentor
Leftover /tmp/scm* directories from earlier attempts may cause this issue. Look for such files on your hanging hosts and remove them and then retry the installation from the UI.

View solution in original post

avatar
New Contributor

you can remove /tmp/.scm_prepare_node.lock

View solution in original post

11 REPLIES 11

avatar
Mentor
Leftover /tmp/scm* directories from earlier attempts may cause this issue. Look for such files on your hanging hosts and remove them and then retry the installation from the UI.

avatar
New Contributor
Thanks for the reply, the problem is resolved through installation restart.

avatar
New Contributor

you can remove /tmp/.scm_prepare_node.lock

avatar
New Contributor
This worked for me. Thanks alot.

avatar
Explorer

Sometime just deleting lock file doesnt work. Need to restart cloudera-server service. Thanks

avatar
This is a known defect and we are working to fix it, thanks for your patience thus far.
Regards,
Gautam Gopalakrishnan

avatar
New Contributor

If removing lock file doesn't help and if you are stuck on cloudera manager, do "Abort installation" and then retry on failed hosts.

avatar
Contributor

Hi,

 

Following has been done to get rid of the issue:

 

1) Aborted installation.

2) Logged in to each failed host and removed files in /tmp and retried installation on each failed host.

 

Below is the example:

rm -rf scm_prepare_node.VqVHCy66 scm_prepare_node.WjYHxBu2 scm_prepare_node.0Hk6W9O1 .scm_prepare_node.lock

 

avatar
Contributor

Removed any hidden files too under /tmp directory on the failed host.

Use ls -al command to view hidden files

Example:

.scm_prepare_node.lock