<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Cloudera namenode not starting due to ulimit error in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Cloudera-namenode-not-starting-due-to-ulimit-error/m-p/59737#M27637</link>
    <description>&lt;P&gt;I did not see the reply. It was my problem. I was looking in to .out file instead of .log. Its solved.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/16544"&gt;@csguna&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;not sure if you are still looking for the solution i am kind of late though .&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 09 Sep 2017 15:19:21 GMT</pubDate>
    <dc:creator>sandy05</dc:creator>
    <dc:date>2017-09-09T15:19:21Z</dc:date>
    <item>
      <title>Cloudera namenode not starting due to ulimit error</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudera-namenode-not-starting-due-to-ulimit-error/m-p/57936#M27635</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am trying to start the namenode using the cloudera package, but it fails. Checking the log, I found it is failing on ulimit. Can anyone tell what this error is exactly. I gave permissions 777 also for the /data directories but still did not work. I am trying to have single node cluster on CentOS 7 using google cloud Iaas.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class="messageContent"&gt;&lt;BLOCKQUOTE&gt;&lt;DIV class="bbCodeBlock bbCodeCode"&gt;&lt;PRE&gt;root@hadoop admin]# sudo service hadoop-hdfs-namenode start
starting namenode, logging to /var/log/hadoop-hdfs/hadoop-hdfs-namenode-hadoop.out
Failed to start Hadoop namenode. Return value: 1           [FAILED]


[root@hadoop admin]# cat /var/log/hadoop-hdfs/hadoop-hdfs-namenode-hadoop.out
ulimit -a for user hdfs
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 14103
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 32768
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 65536
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited&lt;/PRE&gt;&lt;/DIV&gt;&lt;DIV class="messageTextEndMarker"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;/DIV&gt;&lt;DIV class="messageMeta ToggleTriggerAnchor"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Fri, 16 Sep 2022 11:58:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudera-namenode-not-starting-due-to-ulimit-error/m-p/57936#M27635</guid>
      <dc:creator>sandy05</dc:creator>
      <dc:date>2022-09-16T11:58:36Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudera namenode not starting due to ulimit error</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudera-namenode-not-starting-due-to-ulimit-error/m-p/59353#M27636</link>
      <description>&lt;P&gt;not sure if you are still looking for the solution i am kind of late though .&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2017 05:38:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudera-namenode-not-starting-due-to-ulimit-error/m-p/59353#M27636</guid>
      <dc:creator>csguna</dc:creator>
      <dc:date>2017-08-29T05:38:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudera namenode not starting due to ulimit error</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Cloudera-namenode-not-starting-due-to-ulimit-error/m-p/59737#M27637</link>
      <description>&lt;P&gt;I did not see the reply. It was my problem. I was looking in to .out file instead of .log. Its solved.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/16544"&gt;@csguna&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;not sure if you are still looking for the solution i am kind of late though .&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Sep 2017 15:19:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Cloudera-namenode-not-starting-due-to-ulimit-error/m-p/59737#M27637</guid>
      <dc:creator>sandy05</dc:creator>
      <dc:date>2017-09-09T15:19:21Z</dc:date>
    </item>
  </channel>
</rss>

