- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2022 06:51 AM
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"
The log (in a cluster workspace instance) stays in a loop at:
[ 348.935443] audit: kauditd hold queue overflow
[ 348.940183] audit: kauditd hold queue overflow
[ 348.946439] audit: kauditd hold queue overflow
[ 354.013288] audit: kauditd hold queue overflow
[ 354.019590] audit: kauditd hold queue overflow
[ 354.025712] audit: kauditd hold queue overflow
[ 475.998259] audit: kauditd hold queue overflow
[ 476.004062] audit: kauditd hold queue overflow
[ 476.009494] audit: kauditd hold queue overflow
[ 638.997129] audit: kauditd hold queue overflow
[ 639.005763] audit: kauditd hold queue overflow
[ 639.012236] audit: kauditd hold queue overflow
Thanks,
- Labels:
-
Cluster
-
Private Link
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2022 10:04 AM
@Fernando Arribas Jara : Is it a terraform deployment? Do you see any STS endpoint in it? if yes, could you please delete it and try
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2022 11:45 AM
Thanks @Sivaprasad C S It's already working. The problem was that the AWS STS private link was wrongly associated with the correct subnet.