On Wed, Aug 22, 2012 at 11:22 AM, Nik Hodgkinson wrote:
I just got the chance to restart the cluster (internal customers and all),
but that still didn't fix the problem. I'm getting the exact same error as
before. I've attached a cmf-dump with the config I tried.
On Aug 21, 2012, at 7:33 PM, Harsh J wrote:
Did it end up working Nik?
On Tue, Aug 21, 2012 at 8:19 AM, Nik Hodgkinson wrote:
How strange, I'm on a Mac and I typed it in manually. I'll see what's can
do to strip out the carriage returns and get back to you.
On Aug 20, 2012, at 7:30 PM, Harsh J wrote:
(Or alternatively you can just erase the field and type it in
manually. Browsers don't add \r AFAIK)
Meanwhile, I've also filed for an improvement internally to perhaps
catch and sanitize it automatically. Many thanks for reporting this
On Tue, Aug 21, 2012 at 7:58 AM, Harsh J wrote:
Thanks for the quick update and the attachment Nik,
Looks like windows newline characters are the issue, possibly:
Was this copied from some text? Perhaps you can remove the \r
characters (copy-paste to any text editor, ask editor to strip out the
\rs and copy-paste back) and retry?
On Tue, Aug 21, 2012 at 7:53 AM, Nik Hodgkinson wrote:
There aren't any special characters in the safety value, and the
whitespace is just spaces. I've attached a cmf-dump.
On Aug 20, 2012, at 7:15 PM, Harsh J wrote:
Do you have some special characters in your safety valve? Are those
spaces of indent actually tab characters or space ones, for example?
Can you send across an "export"-ed configuration set as detailed in
the first step here:https://ccp.cloudera.com/display/FREE4DOC/Importing+and+Exporting+Cloudera+Manager+Settings?
On Tue, Aug 21, 2012 at 5:02 AM, Nik Hodgkinson wrote:
I'm trying to set the HDFS Safety Value to disable the dfs.permissions
This is what I've inserted into the field:
The configuration saves fine, but when I try to restart the HDFS service I
get the following error:
Command failed to start:
Unable to generate config file hdfs-site.xml for role with type NAMENODE:
Unable to parse XML safety valve
I can't really find where I'm going wrong. Am I missing something or is
a bug I need to file?