Hi, came across an old posting today, by chance - cc'ing openvpn-devel, because that's really more of a -devel question...
On Thu, May 18, 2017 at 02:47:37PM -0700, Yury Shefer wrote:
> Here is what I noticed:
> 1) when I hit max-sessions and the daemon no longer accepts new
> connections (by logging "new incoming connection would exceed maximum
> number of clients (16200)"), the memory usage by the process
> continuously increases (by ~30 MB per minute). For 16K connections
> OpenVPN will consume around 3-3.2Gb of RAM and then, in a period of
> ~2-3 hours, it will consume the rest of VM RAM (8 GB total) and gets
> killed by the kernel.
This looks like we do not properly clean up memory when refusing a
new session (every new session needs memory, which is expected, but
if we do not actually accept the session, memory needs to be returned).
I guess that you see quite a number of incoming connections on top of
the allowed limit, and thus the "continuous increase".
[..]
> 2) run the process with valgrind (valgrind --leak-check=yes) but it
> reported no errors. Logging with verb 9 with such amount of sessions
> is a bit unrealistic.
Valgrind might not notice because our memory management is... quite
a bit advanced...
Can you reproduce this with a much lower limit, like "max-sessions 5"?
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
