<?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>topic Re: Error cluster launch: Security Daemon Registration in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/error-cluster-launch-security-daemon-registration/m-p/28457#M20253</link>
    <description>&lt;P&gt;Thanks @Sivaprasad C S​&amp;nbsp; It's already working.  The problem was that the AWS STS private link was wrongly associated with the correct subnet. &lt;/P&gt;</description>
    <pubDate>Mon, 10 Oct 2022 18:45:13 GMT</pubDate>
    <dc:creator>FerArribas</dc:creator>
    <dc:date>2022-10-10T18:45:13Z</dc:date>
    <item>
      <title>Error cluster launch: Security Daemon Registration</title>
      <link>https://community.databricks.com/t5/data-engineering/error-cluster-launch-security-daemon-registration/m-p/28454#M20250</link>
      <description>&lt;P&gt;I have created a workspace in AWS with private link. When we launch a cluster we get the following error: "Security Daemon Registration Exception: Failed to set up the spark container due to an error when registering the container to security daemon"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The log (in a cluster workspace instance) stays in a loop at:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[  348.935443] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  348.940183] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  348.946439] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  354.013288] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  354.019590] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  354.025712] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  475.998259] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  476.004062] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  476.009494] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  638.997129] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  639.005763] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;[  639.012236] audit: kauditd hold queue overflow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 13:51:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/error-cluster-launch-security-daemon-registration/m-p/28454#M20250</guid>
      <dc:creator>FerArribas</dc:creator>
      <dc:date>2022-10-07T13:51:00Z</dc:date>
    </item>
    <item>
      <title>Re: Error cluster launch: Security Daemon Registration</title>
      <link>https://community.databricks.com/t5/data-engineering/error-cluster-launch-security-daemon-registration/m-p/28455#M20251</link>
      <description>&lt;P&gt;@Fernando Arribas Jara​&amp;nbsp;: Is it a terraform deployment? Do you see any STS endpoint in it? if yes, could you please delete it and try&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 17:04:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/error-cluster-launch-security-daemon-registration/m-p/28455#M20251</guid>
      <dc:creator>Sivaprasad1</dc:creator>
      <dc:date>2022-10-07T17:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: Error cluster launch: Security Daemon Registration</title>
      <link>https://community.databricks.com/t5/data-engineering/error-cluster-launch-security-daemon-registration/m-p/28457#M20253</link>
      <description>&lt;P&gt;Thanks @Sivaprasad C S​&amp;nbsp; It's already working.  The problem was that the AWS STS private link was wrongly associated with the correct subnet. &lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 18:45:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/error-cluster-launch-security-daemon-registration/m-p/28457#M20253</guid>
      <dc:creator>FerArribas</dc:creator>
      <dc:date>2022-10-10T18:45:13Z</dc:date>
    </item>
  </channel>
</rss>

