Member since
07-30-2013
509
Posts
113
Kudos Received
124
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2640 | 07-09-2018 11:54 AM | |
2216 | 05-03-2017 11:03 AM | |
5157 | 03-28-2017 02:27 PM | |
1983 | 03-27-2017 03:17 PM | |
1755 | 03-13-2017 04:30 PM |
12-17-2014
09:05 PM
Sadly I'm out of theories as to why it isn't working as expected = / It's worth noting that the embedded db is not recommended for production. In addition to the normal reasons for not using it (performance, manageability, etc), moving off of the embedded db will definitely make this error go away, as it wouldn't even invoke that code path. You could also try renaming /etc/cloudera-scm-server/db.mgmt.properties so that CM no longer sees it, and restarting CM. This will probably disable the features around automatic database creation (ie you have to create the user and database manually, but CM will still create the tables for you), but will also probably avoid the bug you're seeing.
... View more
12-17-2014
08:02 PM
That's pretty surprising, since the error message clearly said there was a problem logging in to postgresql as cloudera-scm, and CM will always use the password in /var/lib/cloudera-scm-server-db/data/generated_password.txt to connect to this account. Just to confirm, you used the same password in /var/lib/cloudera-scm-server-db/data/generated_password.txt to log in, right? Also, the format of that file should look like: $PASSWORD The password above was generated by $0 (part of the cloudera-manager-server-db package) and is the password for the user 'cloudera-scm' for the database in the current directory. Generated at $NOW. If it was modified, like if something was added to the top of the file, that could cause an issue. I admit this is a long shot.
... View more
12-17-2014
11:40 AM
It sounds like there's a problem connecting to the embedded db. Do you have the embedded postgresql database set up? Does the password in /var/lib/cloudera-scm-server-db/data/generated_password.txt work for the cloudera-scm user? (psql -h localhost -U cloudera-scm -p 7432 ) Is your CM server still configured to use that database? (/etc/cloudera-scm-server/db.properties) Does this file exist? /etc/cloudera-scm-server/db.mgmt.properties
... View more
12-11-2014
01:16 PM
Cloudera Manager's upgrade wizard currently only supports major upgrades, which are generally much more complicated. Since you upgraded from 5.2.0 to 5.2.1, the wizard wasn't applicable. For minor / maintenance upgrades, you need to follow the documentation. Stay tuned though, as we are making improvements here in a future release. For major upgrades, the existing CM upgrade wizard will run the sqoop upgrade command for you. I think that you clicked activate parcel, it prompted you to restart, and you thought that was an upgrade wizard when in fact it was just a simple cluster restart. We're making improvements to this specific experience as well.
... View more
12-11-2014
10:55 AM
Upgrading CDH will upgrade your Sqoop2 binaries since Sqoop2 is part of CDH. Every time you upgrade Sqoop2 binaries you need to run the Sqoop2 upgrade command. Click on your Sqoop2 service and look for the upgrade command in the actions dropdown menu on the right. You have to stop the service first.
... View more
12-11-2014
10:40 AM
Normally you just run the Sqoop2 upgrade command whenever you upgrade Sqoop binaries.
... View more
11-25-2014
10:39 AM
Hi, When you look at your home page what does Cloudera Manager say your CDH version for the cluster is? Is this version correct? Are you using Packages or Parcels?
... View more
11-20-2014
11:33 AM
HMON is the Host Monitor role in the Management service. SMON is the Service Monitor role. That warning about the hostname seems to likely be causing these issues. You could try removing the 2nd line of your /etc/hosts file, but frankly I'm not an expert on how that file works.
... View more
11-19-2014
04:48 PM
Reinstallation is unlikely to fix your issue. It sounds from the log like ServiceMonitor died. Can you answer my previous question about your management roles and whether each of them are running? If not, what happens when you restart them? I wonder if something is weird with your networking, where SMon can't talk to CM server, so it can't do its work and connections to SMon therefore fail. Or maybe you just need to restart them. Is this a the right CM URL when inside your cluster? http://ip-10-0-1-1.eu-west-1.compute.internal:7180 Thanks, Darren
... View more
11-19-2014
11:52 AM
This is a totally different issue, as the error messages are different. What version of Cloudera Manager are you using? This may be a problem with /var/run being a noexec mount by default on your OS, which CM works around in more recent versions.
... View more