Opened 5 years ago

Closed 5 years ago

#1181 closed Bug / Defect (wontfix)

'status' via management socket show nothing when openvpn accept wave of connections.

Reported by: black_angel Owned by: jamesyonan
Priority: minor Milestone:
Component: Management Version: OpenVPN 2.4.7 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

Openvpn server have a ~15 connected users
If I try to connect 50+ to it, monitoring via socket return empty string, until this clients not finished all steps of establish the connection.

echo 'status' | socat - UNIX-CONNECT:/var/run/openvpn-server/tcp-1194.sock

Note: used external scripts for
up
tls-verify
client-connect
client-disconnect

Change History (1)

comment:1 Changed 5 years ago by Gert Döring

Resolution: wontfix
Status: newclosed

That's just the way OpenVPN works - if it's busy negotiating with new clients, it will not do anything else (especially when waiting synchronously to the external scripts).

Reduce the amount of work the external scripts do, and it will come back sooner - for client-connect, you can use the (upcoming) async-client-connect mode.

Closing this ticket anyway, as it's a "this is the way it is and it is not possible to change this easily within the 2.x design". Sorry.

Note: See TracTickets for help on using tickets.