You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Description:
In versions 2.0.0 to v2.0.3 of the EFS CSI Driver, there is an bug where efs-proxy processes are not properly cleaned after EFS volumes are unmounted. This leads to an accumulation of zombie processes that eventually use up all ports in the designated range ([20049, 20449]), causing port exhaustion and blocking the mounting of new EFS volumes.
Error Message: Output: Failed to locate an available port in the range [20049, 20449]. Try specifying a different port range in /etc/amazon/efs/efs-utils.conf.
Workaround:
The current reaper code primarily focuses on cleaning up Stunnel PIDs post-unmount. A potential solution is to update the reaper.go file to extend its functionality to include the cleanup of efs-proxy PIDs as well. This ensures all associated efs-proxy processes are properly terminated, thereby freeing up ports for new mounts.
This issue is being created for visibility even though it has been resolved by PR.
The text was updated successfully, but these errors were encountered:
Issue Description:
In versions 2.0.0 to v2.0.3 of the EFS CSI Driver, there is an bug where efs-proxy processes are not properly cleaned after EFS volumes are unmounted. This leads to an accumulation of zombie processes that eventually use up all ports in the designated range ([20049, 20449]), causing port exhaustion and blocking the mounting of new EFS volumes.
Error Message:
Output: Failed to locate an available port in the range [20049, 20449]. Try specifying a different port range in /etc/amazon/efs/efs-utils.conf.
Workaround:
The current reaper code primarily focuses on cleaning up Stunnel PIDs post-unmount. A potential solution is to update the reaper.go file to extend its functionality to include the cleanup of efs-proxy PIDs as well. This ensures all associated efs-proxy processes are properly terminated, thereby freeing up ports for new mounts.
This issue is being created for visibility even though it has been resolved by PR.
The text was updated successfully, but these errors were encountered: