I've installed OpsCenter free edition on a test single-node cluster running on CentOS 6. I've gotten OpsCenter up and running but when I try to install the agent I always get "Error during agent install ([Errno 13] Permission denied: '/root/.ssh/known_hosts').". I can SSH to localhost from the command line as well as SSH to the IP bound to eth0. Root uses a private key to authenticate and to see if that was an issue I created another user with sudo ability but I get the same exact error.
In an effort to consolidate free help offered for our products we have decided to move these forums to a more widely used forum. Please use one of the following queries (or any combination):
- Cassandra: tag search or plain text search
- DataStax Enterprise: tag search or plain text search
- DataStax OpsCenter: tag search or plain text search
Permission denied for known_hosts(6 posts) (2 voices)
Well I figured out the permission denied issue. When running OpsCenter via the init script it'll try to run as the opscenter user instead of root if the opscenter user exists. This will always be the case if installed from the RPM. The opscenter user doesn't have sudo/root permissions because it isn't given this upon install. I edited the init script and commented out the lines that run it as opscenter so I can get a step further.
Are you starting opscenterd with 'sudo /sbin/service opscenterd start', or are you calling the init.d script directly?
I was calling "sudo /etc/init.d/opscenterd start". I got it up and running successfully now, I'm just using root as the user that runs the process in the init script.
Okay, I believe that explains the problem. The documentation used to pretty clearly state that you should use
serviceto start opscenterd, but the current documentation doesn't do a good job of conveying that. I'll get that fixed.
The issue has to do with the inherited
$HOMEenvironment variable when executing the init.d script directly;
serviceclears this (and other) environment variables when before executing the init.d script.
By the way, the underlying issue here has already been fixed for the next release.