<?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: cdsw containers crashing in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/cdsw-containers-crashing/m-p/277702#M207645</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/28572"&gt;@SrJay&lt;/a&gt;&amp;nbsp;it looks like you are running CDSW 1.6 on VMWare host which has ipv6 disabled. Can you please confirm by reviewing the dmesg for words&amp;nbsp;&lt;U&gt;cmdline&lt;/U&gt; and &lt;U&gt;segfaults?&lt;/U&gt;&amp;nbsp; If you see segmentation faults for node process and if the Cmdline shows ipv6.disabled=1, then you are likely hitting a known issue which is seen with a combination of node.js version 10.x, grpc, and ipv6&amp;nbsp; The workaround for this is to enable ipv6 on all the hosts running CDSW using the following RedHat article&amp;nbsp;&lt;A href="https://access.redhat.com/solutions/8709#rhel7enable" target="_blank" rel="nofollow noopener"&gt;https://access.redhat.com/solutions/8709#rhel7enable&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2019 16:49:40 GMT</pubDate>
    <dc:creator>AutoIN</dc:creator>
    <dc:date>2019-09-18T16:49:40Z</dc:date>
    <item>
      <title>cdsw containers crashing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/cdsw-containers-crashing/m-p/270072#M207268</link>
      <description>&lt;P&gt;I have installed cdsw trail version before purchasing the product but stuck with errors.&lt;/P&gt;
&lt;P&gt;500 gig block device&amp;nbsp; and using default /var/lib/ for application.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;CDSW disks provisioned via ESX/VMware.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;CDSW starts fine in CM but failed to launch containers. Here is the status.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Failed events are below for web-5dddb59597-pclf2&amp;nbsp; (redacted host name for security reasons).&lt;/P&gt;
&lt;P&gt;Not sure why&amp;nbsp;tcp-ingress-controller-7d65df6d8f-qqxzn&amp;nbsp; is starting , i am not using TLS for CDSW&lt;/P&gt;
&lt;P&gt;Any help is highly appreciated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;NAME READY STATUS RESTARTS AGE&lt;BR /&gt;cdsw-compute-pod-evaluator-566f7664df-rqm2j 1/1 Running 0 9m38s&lt;BR /&gt;cron-6dd99c7b78-kh4rw 1/1 Running 0 9m40s&lt;BR /&gt;db-86bbb69b54-nxz4z 1/1 Running 0 9m40s&lt;BR /&gt;db-migrate-46715e4-nf5dh 0/1 Completed 0 9m40s&lt;BR /&gt;ds-cdh-client-578fc69b9-hcqv7 1/1 Running 0 9m38s&lt;BR /&gt;ds-operator-66ff9c4b78-r6bk7 1/1 Running 0 9m38s&lt;BR /&gt;ds-reconciler-64bccdd574-vhhpz 0/1 CrashLoopBackOff 4 9m38s&lt;BR /&gt;ds-vfs-648f9bddf-7n6hg 1/1 Running 0 9m38s&lt;BR /&gt;image-puller-xwbcs 1/1 Running 0 9m39s&lt;BR /&gt;ingress-controller-7c8bb7898b-2k4zk 1/1 Running 0 9m40s&lt;BR /&gt;livelog-65f9846677-5j8js 1/1 Running 0 9m40s&lt;BR /&gt;livelog-publisher-8c89k 1/1 Running 2 9m39s&lt;BR /&gt;s2i-builder-b775b49c4-62t56 1/1 Running 0 9m37s&lt;BR /&gt;s2i-builder-b775b49c4-vzmwb 1/1 Running 0 9m37s&lt;BR /&gt;s2i-builder-b775b49c4-w7hck 1/1 Running 0 9m37s&lt;BR /&gt;s2i-client-5658cd7456-8shrb 1/1 Running 0 9m37s&lt;BR /&gt;s2i-git-server-6d7d8ccdd8-k4srm 1/1 Running 0 9m40s&lt;BR /&gt;s2i-queue-6c699c5f9b-csxns 1/1 Running 0 9m40s&lt;BR /&gt;s2i-registry-5db6db6859-rjlkz 1/1 Running 0 9m40s&lt;BR /&gt;s2i-registry-auth-76cb9bf597-gmbxp 1/1 Running 0 9m40s&lt;BR /&gt;s2i-server-58db56cf6-7t5fb 1/1 Running 0 9m40s&lt;BR /&gt;secret-generator-7ffbcd8fcb-wn58c 1/1 Running 0 9m39s&lt;BR /&gt;spark-port-forwarder-bfvdm 1/1 Running 0 9m39s&lt;BR /&gt;tcp-ingress-controller-7d65df6d8f-qqxzn 0/1 CrashLoopBackOff 5 9m39s&lt;BR /&gt;web-5dddb59597-b7sp5 1/1 Running 1 9m39s&lt;BR /&gt;web-5dddb59597-m88qn 1/1 Running 1 9m39s&lt;BR /&gt;web-5dddb59597-pclf2 0/1 Error 6 9m39s&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Events:&lt;BR /&gt;Type Reason Age From Message&lt;BR /&gt;---- ------ ---- ---- -------&lt;/P&gt;
&lt;P class="p1"&gt;Normal Scheduled 12m default-scheduler Successfully assigned default/web-5dddb59597-pclf2 to xyz.copration&lt;/P&gt;
&lt;P class="p1"&gt;Warning FailedMount 11m (x3 over 12m) kubelet, xyz.copration MountVolume.SetUp failed for volume "ds-operator-crt" : secrets "ds-operator-tls" not found&lt;/P&gt;
&lt;P class="p1"&gt;Warning FailedMount 11m (x3 over 12m) kubelet, xyz.copration MountVolume.SetUp failed for volume "tcp-ingress-controller-crt" : secrets "tcp-ingress-controller-tls" not found&lt;/P&gt;
&lt;P class="p1"&gt;Warning FailedMount 11m (x4 over 12m) kubelet, xyz.copration MountVolume.SetUp failed for volume "s2i-server-crt" : secrets "s2i-server-tls" not found&lt;/P&gt;
&lt;P class="p1"&gt;Warning FailedMount 11m (x4 over 12m) kubelet, xyz.copration MountVolume.SetUp failed for volume "s2i-client-crt" : secrets "s2i-client-tls" not found&lt;/P&gt;
&lt;P class="p1"&gt;Warning FailedMount 11m (x4 over 12m) kubelet, xyz.copration MountVolume.SetUp failed for volume "ds-vfs-crt" : secrets "ds-vfs-tls" not found&lt;/P&gt;
&lt;P class="p1"&gt;Warning FailedMount 11m (x3 over 12m) kubelet, xyz.copration MountVolume.SetUp failed for volume "web-tls" : secrets "web-tls" not found&lt;/P&gt;
&lt;P class="p1"&gt;Warning FailedMount 11m (x4 over 12m) kubelet, xyz.copration MountVolume.SetUp failed for volume "ds-cdh-client-crt" : secrets "ds-cdh-client-tls" not found&lt;/P&gt;
&lt;P class="p1"&gt;Normal Pulled 7m19s (x5 over 9m24s) kubelet, xyz.copration Container image "docker-registry.infra.cloudera.com/cdsw/web:46715e4" already present on machine&lt;/P&gt;
&lt;P class="p1"&gt;Warning BackOff 2m23s (x33 over 9m2s) kubelet, xyz.copration Back-off restarting failed container&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 11:36:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/cdsw-containers-crashing/m-p/270072#M207268</guid>
      <dc:creator>SrJay</dc:creator>
      <dc:date>2026-04-21T11:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: cdsw containers crashing</title>
      <link>https://community.cloudera.com/t5/Support-Questions/cdsw-containers-crashing/m-p/277702#M207645</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/28572"&gt;@SrJay&lt;/a&gt;&amp;nbsp;it looks like you are running CDSW 1.6 on VMWare host which has ipv6 disabled. Can you please confirm by reviewing the dmesg for words&amp;nbsp;&lt;U&gt;cmdline&lt;/U&gt; and &lt;U&gt;segfaults?&lt;/U&gt;&amp;nbsp; If you see segmentation faults for node process and if the Cmdline shows ipv6.disabled=1, then you are likely hitting a known issue which is seen with a combination of node.js version 10.x, grpc, and ipv6&amp;nbsp; The workaround for this is to enable ipv6 on all the hosts running CDSW using the following RedHat article&amp;nbsp;&lt;A href="https://access.redhat.com/solutions/8709#rhel7enable" target="_blank" rel="nofollow noopener"&gt;https://access.redhat.com/solutions/8709#rhel7enable&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2019 16:49:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/cdsw-containers-crashing/m-p/277702#M207645</guid>
      <dc:creator>AutoIN</dc:creator>
      <dc:date>2019-09-18T16:49:40Z</dc:date>
    </item>
  </channel>
</rss>

