Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on
07-17-2014
09:18 AM
- last edited on
08-24-2019
12:10 PM
by
ask_bill_brooks
Hello, all the masters here!
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
Created 07-20-2014 08:35 AM
Created 12-23-2014 12:57 PM
you can remove /tmp/.scm_prepare_node.lock
Created 08-23-2019 02:55 AM
removing hidden files worked for me. thanks a lot
Created 12-29-2018 09:38 PM
I ran into the same issue with CM 5.16.1.
Try the following:
killall -9 scm_prepare_node.sh # this interrupts the annoying progress Acquiring installation lock... rm -rf /tmp/scm_prepare_node* rm /tmp/.scm_prepare_node.lock