This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 52%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
I have deployed Nifi-cronjob in AKS and having issues. Need guidance to fix it
Events:
Type Reason Age From Message
Warning FailedAttachVolume 3m19s (x19 over 61m) attachdetach-controller AttachVolume.Attach failed for volume "iic-blob-pv" : timed out waiting fo
r external-attacher of blob.csi.azure.com CSI driver to attach volume iicdevnifiblobst_epresentment
Thanks Mounika for providing the solution. I enabled the CSI driver on the AKS cluster which resolved the issue but now I am getting a new error. I checked the deployment file and it seems it is not available Type Reason Age From Message
Warning BackOff 4m35s (x781 over 174m) kubelet Back-off restarting failed container nifi-cronjob in pod nifi-cronjob-58b7b7fcb8-j48fs_iic-nifi-dev
(aed3ecc0-d631-4fa0-b54a-134d05a9204d)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 47%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Hi Reddy Chakri,
Thank you for taking time to share that the first issue is resolved.
From the logs it is going to Crashloopback state with exit Code : 1
Reason: CrashLoopBackOff
Last State: Terminated Reason
Error Exit Code: 1
CrashLoopBackOff means the pod has failed/exited unexpectedly/has an error code that is not zero. The error message indicates that the kubelet is backoff-restarting the failed container nifi-cronjob in the pod nifi-cronjob-58b7b7fcb8-j48fs_iic-nifi-dev.This means that the container has failed to start or has crashed, and the kubelet is trying to restart it.
There are a couple of ways to check this. I would recommend going through below links and get the logs for the pod using kubectl logs.
Debug Pods and ReplicationControllers
Determine the Reason for Pod Failure
Check the NiFi configuration files: Verify that your NiFi configuration files are correct and properly configured. Check for any typos, incorrect settings, or missing properties.
Verify dependencies: Ensure that all required dependencies are installed and available to NiFi. You can check the NiFi documentation for the required dependencies.
Hi Reddy Chakri,
Just checking in to see if you had a chance to see my response to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.
If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.
Hi Reddy Chakri,
Just checking in to see if you had a chance to see my response to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.
If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 24%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Hello Reddy Chakri,
Thanks for your question.
This seems related to a volume attachment failure with the CSI driver. Try the solution here.
You can mark it 'Accept Answer' and 'Upvote' if this helped you
Regards,
Abiola
Hi Reddy Chakri,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
As akinbade abiola suggested, the issue might be related to the disk and node hosting the pod being in different zones. Have you checked the zone configuration for your AKS cluster and Azure storage account?
Additionally, you can follow the below troubleshooting steps:
1.Check if the Azure Blob CSI driver is installed in your AKS cluster by running the following command:
kubectl get deployments -n kube-system | grep azure-blob-csi
2.Verify that the CSI driver is running by checking the pod status:
kubectl get pods -n kube-system | grep azure-blob-csi
This command should return a pod named azure-blob-csi-controller-xxxxx or similar, with a status of Running.
3.Check the CSI driver logs for any error messages using the command kubectl logs -f -n kube-system azure-blob-csi-controller-xxxxx.
4.Verify that the Azure storage account and container are correctly configured and accessible from the AKS cluster.
For more information on CSI : https://video2.skills-academy.com/en-us/azure/aks/csi-storage-drivers
https://video2.skills-academy.com/en-us/azure/aks/azure-blob-csi?tabs=NFS
If you have any further queries, do let us know.
If the answer is helpful, please click "Accept Answer" and "Upvote it."