Member since
07-30-2013
509
Posts
113
Kudos Received
123
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3003 | 07-09-2018 11:54 AM | |
2510 | 05-03-2017 11:03 AM | |
6125 | 03-28-2017 02:27 PM | |
2341 | 03-27-2017 03:17 PM | |
2053 | 03-13-2017 04:30 PM |
03-19-2014
09:13 AM
Also, be sure that you remove /etc/cloudera-scm-server/db.mgmt.properties if it exists. It should only be used with the embedded postgresql db.
... View more
03-19-2014
09:12 AM
Hi Nishan, Did /var/log/cloudera-scm-server/cloudera-scm-server.log include the a line with "Started Jetty Server" with a time stamp matching when you tried to start the server? Is there anything in /var/log/cloudera-scm-server/cloudera-scm-server.out? Sometimes fatal errors are reported here rather than in the .log file. Thanks, Darren
... View more
03-19-2014
09:06 AM
Hi, Usually when the database test is missing the server name, that's because there was a problem detecting the server name when your embedded postgresql database was first started (ie hostname returned an error / empty string). We've seen this happen especially when using a VPN on AWS machines. The fix is to modify /etc/cloudera-scm-server/db.mgmt.properties to add your fully qualified domain name before :7432 wherever it appears in that file. Then, restart the CM server (sudo service cloudera-scm-server restart). Thanks, Darren
... View more
03-18-2014
02:25 PM
1 Kudo
The relevant error is already displayed. It looks like your Oracle TNS listener doesn't know the Oracle SID "ENTLOG". Is that the right TNS name? " [ main] DbCommandExecutor INFO Able to connect to db server on host '10.7.123.21:1530' but not able to find database 'ENTLOG'. [ main] DbCommandExecutor ERROR Error when connecting to database. java.sql.SQLException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor " Does the following work from the machine where you are trying to run CM server? This is basically what the scm script is trying to do. (replace with real user and password) sqlplus user/pwrd@10.7.123.21:1530/ENTLOG You also probably don't need to specify --scm-host, though I don't think that would cause this error.
... View more
03-18-2014
10:26 AM
It sounds like the user doesn't exist in your oracle database. Did you already create the user in your Oracle database? What's the command-line invocation that you used?
... View more
03-16-2014
10:09 AM
If you can get to the web UI, then you can modify this setting under Administration > Settings > Ports and Addresses. If you can't, then run a curl command to update it via the API, while ssh'd in to the host (so your firewall doesn't get in the way): curl -X PUT -u "admin:admin" -i \ -H "content-type:application/json" \ -d '{ "items": [ { "name": "HTTP_PORT", "value": 8080 } ] }' \ http://<cm_host>:7180/api/v3/cm/config
... View more
03-14-2014
10:56 AM
Hi cor, Thanks for letting us know. This issue has since been fixed. Thanks, Darren
... View more
03-13-2014
08:41 AM
"ts" stands for Time Series. This is where the Service Monitor role in the Management Service stores data for Time Series information. You can configure retention policies in the configuraiton of your Service Monitor role. There's also a page to help you understand the disk usage in detail, as described below: Time-Series Storage firehose_time_series_storage_bytes 10 GiB The approximate amount of disk space dedicated to storing time series and health data. Once the store has reached its maximum size older data will be deleted to make room for newer data. The disk usage is approximate because we only begin deleting data once we've reached the limit. Note that Cloudera Manager stores time-series data at a number of different data granularities, and these granularities have different effective retention periods. Specifically, Cloudera Manager stores metric data as both raw data points and ten-minutely, hourly, six-hourly, daily, and weekly summary data points. Raw data consumes the bulk of the allocated storage space, weekly summaries the least. As such, raw data is retained for the shortest amount of time, while weekly summary points are unlikely to ever be deleted. See the "Disk Usage" tab on the Service Monitor page for more information on how space is consumed within the Service Monitor. This tab also shows information about the amount of data retained and time window covered by each data granularity.
... View more
03-12-2014
12:29 PM
I'm not saying that this is the reason why it was killed. I don't really know anything about nesus or why it might kill a process. It just sounds like you are doing security audits, and if so you should know that HBase Thrift server is a security hole that should fail any comprehensive security audit. In general, regardless of nesus, if you care about security in your cluster, you should not use this role. Thanks, Darren
... View more
03-12-2014
09:55 AM
Hi Ranks, HBase Thrift Server does not authenticate requests, so it should not be used if you care about security until this issue is fixed. Thanks, Darren
... View more