Prisma Cloud Compute: Failed to handle filesystem event....tmp: no such file or directory

Prisma Cloud Compute: Failed to handle filesystem event....tmp: no such file or directory

2104
Created On 04/24/23 15:26 PM - Last Modified 12/26/24 18:25 PM


Symptom


  • After upgrading the defenders running on Kubernetes clusters but customer may observer this type of errors on some worker nodes if not all. Even after trying to remove the defenders completely and installing again using both kubectl and helm but with similar results.  
[ERRO 2023-04-12T22:12:36.838 controller_filesystem.go:340 [0m Failed to handle filesystem event &{Source:0 Proc:{Pid:30297 Tid:0 Path:/usr/java/openjdk-17/bin/java Cmd:/usr/java/openjdk-17/bin/java /openjdk-17/bin/java -Dorg.gradle.internal.worker.tmpdir=/builds/sinch/sinch-projects/enterprise-and-messaging/rich-messaging/conv/internal-adapter... Args:/openjdk-17/bin/java -.... No such file or directory

Environment


  • Prisma Cloud SaaS
  • Prims Cloud Compute Edition
  • AWS EKS

Cause


  • No impact, however huge number of errors on the logs

Resolution


  • This is an event-handled, post-container deletion gracefully.
To rephrase: This error is for a file system closed event. The defender was still processing a file system event and the container no longer existed. So the error is handled gracefully & logged. You need not worry about this.
  • Is there any impact on Defender?
No
  • Is there any way to stop this logging? Our log monitoring system is saturated with these logs and it is affecting our monitoring.
We cannot do anything on our end. As the read events could be after container exit/termination. And these are logs, which defenders are handling gracefully.
Other users also viewed:
Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000kHjpCAE&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language