-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with the embedded db? #26
Comments
The CM server tries to find all three supported database classes. I have never sen a problem with it before. What OS version are you running? |
Paying closer attention to your message, it is EL6. Is it CentOS or RHEL? |
It is CentOS : But I tried with Ubuntu and I had the same problem |
Not sure, but in cm5/server.pp line 191, if the db_type is 'embedded', $file_content is not initialized? |
Correct. The file's content is not managed if using the embedded database. What version of Puppet are you using? |
Puppet v3.7.4 I have pushed my vagant environment in https://github.com/ssejourne/ClouderaVagrantPuppet if you want to have a look (and if you have time 😊 ). thx |
Mike, it's related to http://community.cloudera.com/t5/Cloudera-Manager-Installation/Cloudera-Manager-Installation-Path-B-Step-5-sudo-service/td-p/7816 I fixed the problem by deleting I continue my investigations to find why it happens... |
Sébastien, Otherwise, the only thing I can see in your Puppet code is your use of |
Mike, Thanks to point me out the Here is the puppet debug output :
As you can see, it's look like the /etc/cloudera-scm-server/db.properties file is managed and I think that's not expected with the embedded db... thanks for your help and time |
Mike, PR #28 fix the problem for me. |
(@ssejourne Sorry, it seems that I did not submit this comment before taking my holiday.) Correct. The /etc/cloudera-scm-server/db.properties file is managed, however, the |
Ok. My guess : as db.properties is now owned by root, the script used to initialized the embedded db has not the right anymore to modify it... That's why my first PR (#27) was working, but was not passing travis tests as it did not manage the db.properties anymore if the db_type is embedded. |
I try a very simple setup :
And the server fail with an exception :
I do not understand why do it try to use the mysql jdbc driver when the embedded db is Postgesql...
fyi :
Thanks
The text was updated successfully, but these errors were encountered: