About jehalter

jehalter · ‎02-22-2017

I installed my cluster (CDH 5.10.0) using packages. I would like to try Spark2, but noticed it is currently only available as a parcel. I can't find any instructions for my situation. So my question is: is it possible to install the Spark2 parcel on my cluster, even though my cluster was originally installed by using packages?

jehalter · ‎02-09-2017

OK. So this is where I am at. I must keep the Bind Hue Server to Wildcard Address setting checked, because our Hue server is multi-homed; users accesses Hue from our "public" network, while the CM agent checks Hue on the "private" network. Even with "allowed_hosts=*" in the [desktop] section of the Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini, I still observe the issue that the CM agent is not able to communicate with the role's web server. (I don't know why I still observe the issue, yet you do not). Following the "Alternative" steps in your previous post, I 1) start Hue (observe the bad health), 2) cd to the active Hue server directory under /var/run/cloudera-scm-agent/..., 3) edit the cloudera-monitor.properties, replacing the value for http_host (0.0.0.0) with the actual hostname (bsl-ib-c4.uncc.edu), and 4) restart cloudera-scm-agent. The makes issue goes away, well, until the files get rewritten. The only other way I have been able to make the issue go away is to uncheck the Bind Hue Server to Wildcard Address setting, but that is not an option in our current configuration. Thank you for all of your help on this matter, @bgooley and @mbigelow.

jehalter · ‎02-08-2017

No, actually that is *not* the case. My screenshots are from when the "Bind Hue Server to Wildcard Address" was still checked. The reason my http_host in Hue shows the actual server name is because of a setting I had from @mbigelow's first message: "In the same safety valve, Hue Server Advanced Configuration Snippet (Safety Valve) for hue_safety_valve_server.ini, added http_host under the desktop section.." So I still had the above change in my Hue Server Advanced Configuration Snippet (Safety Valve) for hue_safety_valve_server.ini file, which made my screenshot look the way it did. If I was not supposed to have that setting still set, I apologize. One thing I noticed when I unchecked the Wildcard setting is that there were 2 files that shows differences: hue.ini and cloudera-monitor.properties (well 3 if you count the binary file, creds.localjceks): I suspect the update to cloudera-monitor.properties is affecting the way the CM agent is comminucating with Hue's web server, because when defined the host in the hue_safety_valve_server.ini, CM still exhibited the error, even though according to Hue, my http_host was bsl-ib-c4.uncc.edu. But when I uncheck the Bind to Wildcard setting, http_host was changed for both Hue and CM.

jehalter · ‎02-08-2017

Interesting that you should mention "Bind Hue Server to Wildcard Address". I unchecked that in my Hue configuration, restarted, and the problem went away. I waited a while; well past the point in which the error would typically occur, and figured that it was not going to surface. Just as a test, I re-checked "Bind Hue Server to Wildcard Address", restarted Hue, and the problem came back. Just thought I'd add this info to the thread.

jehalter · ‎02-08-2017

I checked Hue's in-memory values of "http_host" and "allowed_hosts", and they are as follows:

jehalter · ‎02-08-2017

@bgooleyand @mbigelow -- thanks for you help on this! Here is the fqdn, as given by the python command: $ python -c 'import socket;print socket.getfqdn()' bsl-ib-c4.uncc.edu Which matches the hostname in the hosts tab in CM: The CM Host Inspector is happy with all hosts, including this one. Would it be worth moving Hue to another machine in the cluster, to see if that changes anything? Btw this is a test cluster that I am using to try out 5.10.0 before rolling it into production, so I have the luxury of trying just about anything without affecting any users.

jehalter · ‎02-08-2017

After upgrading from CDH 5.7.5 to 5.10.0, Cloudera Manager gives a couple of warnings about "Max Message Size for Hive Metastore": Hive: Max Message Size for Hive MetaStore The value of Max Message Size for Hive MetaStore (104857600) should be at least 10% of the value of Java Heap Size of Hive Metastore Server in Bytes (858993459). Hive Metastore Server (bsl-ib-c3): Max Message Size for Hive MetaStore The value of Max Message Size for Hive MetaStore (104857600) should be at least 10% of the value of Java Heap Size of Hive Metastore Server in Bytes (858993459). These are just warnings, but the default 100MB is over 12% of the value of Java Heap Size..., which should satisfy the criteria of being "at least 10%". Am I missing something obvious?

jehalter · ‎02-08-2017

Yes, most definitely added the header. This is what my "Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini" looks like: [desktop] allowed_hosts=* [hbase] hbase_conf_dir={{HBASE_CONF_DIR}} [beeswax] use_get_log_api=true Thanks, Jonathan

jehalter · ‎02-08-2017

Ben-- Thanks for the info on the increased security in 5.10; it's good to know. I tried your suggestions, both"allowed_hosts=<hostname>" and "allowed_hosts=*" in the "Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini" , restarted Hue, and neither helped. Just FYI, my client is currently the Hue server, so I'm running Firefox on the same machine that the Hue server is on. I want to reiterate: I am not having trouble connecting to Hue with my client; the CM agent is having trouble communicating with Hue's web server. To answer your followup question, our distribution is not SLES; we're running RHEL 7.2. Thanks, Jonathan

jehalter · ‎02-07-2017

After upgrading from CDH 5.7.5 to 5.10.0, Hue's Webserver Status gives error message: "Bad : The Cloudera Manager Agent is not able to communicate with this role's web server." Hue is up-and-running, I just think that the CM agent is unable to see it. I found this in /var/log/cloudera-scm-agent/cloudera-scm-agent.log on the Hue server: [07/Feb/2017 15:42:09 +0000] 3747 Monitor-GenericMonitor throttling_logger ERROR (59 skipped) Error calling is alive at 'https://0.0.0.0:8888/desktop/debug/is_alive' Traceback (most recent call last): File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/monitor/generic/hue_adapters.py", line 39, in collect_and_parse self._call_is_alive(self._metrics_uri) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/monitor/generic/hue_adapters.py", line 76, in _call_is_alive head_request_with_timeout(is_alive_url, timeout=timeout) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/url_util.py", line 94, in head_request_with_timeout max_cert_depth) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/url_util.py", line 67, in urlopen_with_timeout return opener.open(url, data, timeout) File "/usr/lib64/python2.7/urllib2.py", line 437, in open response = meth(req, response) File "/usr/lib64/python2.7/urllib2.py", line 550, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib64/python2.7/urllib2.py", line 475, in error return self._call_chain(*args) File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain result = func(*args) File "/usr/lib64/cmf/agent/build/env/lib/python2.7/site-packages/cmf-5.10.0-py2.7.egg/cmf/https.py", line 205, in http_error_default raise e HTTPError: HTTP Error 400: BAD REQUEST Any help would be most appreciated. Thanks, -jon

Online	Offline
Last Visited	‎03-15-2018 12:42 PM

Member Since	‎06-25-2014 12:42 PM
Last Visited	‎03-15-2018 12:42 PM
Posts	16
Kudos received	1

Cloudera Community

Re: Can I upgrade Apache Spark when I'm using pack...

Re: Hue: The Cloudera Manager Agent is not able to...

Re: Hue: The Cloudera Manager Agent is not able to...

Re: Hue: The Cloudera Manager Agent is not able to...

Re: Hue: The Cloudera Manager Agent is not able to...

Re: Hue: The Cloudera Manager Agent is not able to...

Cloudera Manager warning about Max Message Size fo...

Re: Hue: The Cloudera Manager Agent is not able to...

Re: Hue: The Cloudera Manager Agent is not able to...

Hue: The Cloudera Manager Agent is not able to com...