Hi David,
David T. Lewis pravi:
Janko Miv??ek wrote:
This image is running now for months, that's why its restart could help here. But finding the real cause of this trouble, well, this would be just perfect! Anyone has an idea what can be a problem?
Socket leak? Keep an eye on the contents of /proc/<squeakpid>/fd/ and see if open file descriptors are accumulating. If so, you will reach a limit (usually 1024) after which no new connections will be possible.
Yep, that's it, I just counted it: 1024 and dropped to 764 after Swazoo restart.
So, first question: how to close those remaining 764 open sockets without restarting the image,
second: how to avoid opening so many unclosed sockets (some kind of attack?),
third: how to raise the 1024 limit?
Janko