Comment 0 for bug 1420057

While investigating a customer OpenStack deployment managed by Juju I noticed that many unit and machine agents were failing due to file handle exhaustion ("too many open files") after many failed connections to the (broken) Juju state servers. These agents weren't able to reconnect until they were manually restarted.

My guess is that a failed API connection attempt is leaks file handles, possibly a socket (but this is just a guess at this stage). It looks like it took about 2 days of failed connection attempts before file handles were exhausted.

The issue was seen with Juju 1.20.9 but it is likely that it's still there in more recent versions.