net-misc/openvpn-2.4_rc1-r1 is using 100% CPU, while tunnel is established and running. Counterpart is an older OpenVPN installation (2.2.1-8ubuntu1.4 on Ubuntu 12.04.5). Please mask this version as it causes nondesired behaviour.
I faced this wrong behavior connecting to openvpn 2.3.12 server. best regards, luigi
Is it this problem? https://community.openvpn.net/openvpn/ticket/681 There are many claims about 100% CPU usage.
Same here, downgrading to 2.3.13 solves high CPU usage.
so, this 2.4_rc1-r1 have to be masked until it's workarounded or fixed anyhow.
(In reply to Jonas Stein from comment #2) > Is it this problem? > https://community.openvpn.net/openvpn/ticket/681 > > There are many claims about 100% CPU usage. no. I'm not using the control console. ciao luigi
I also see 100% CPU usage with net-misc/openvpn-2.4_rc1-r1 when connecting to Ipvanish, eg. with any of the configs at [1]. Downgrading to net-misc/openvpn-2.3.13 resolves the issue. (In reply to Jonas Stein from comment #2) > Is it this problem? > https://community.openvpn.net/openvpn/ticket/681 > > There are many claims about 100% CPU usage. No, this upstream ticket is about a defect in a version of openvpn that is not affected by the issue described in this bug. 1: https://www.ipvanish.com/software/configs/
Saw this issue with 2.4_rc1-r1 too. This appears to be the relevant upstream bug (marked fixed): https://community.openvpn.net/openvpn/ticket/786
Dear package maintainer, please mask the obviously broken package asap. Or do you need more than hundred "me too" and "CC" messages? You are very fast to unleash a release candidate, but you show no reaction on user complaints. A strange behaviour.
(In reply to Per Pomsel from comment #8) > Dear package maintainer, please mask the obviously broken package asap. Or > do you need more than hundred "me too" and "CC" messages? You are very fast > to unleash a release candidate, but you show no reaction on user complaints. > A strange behaviour. Dear Per Pomsel, I haven't received anything like logs or further debugging efforts from your side, which is what I would expect, because sometimes it's hard to reproduce openvpn bugs that might be caused by the specific configuration of the VPN itself. If you rely on stable software, please use the stabilized version of openvpn. If you still want to use bleeding edge and don't want to spend time on investigating bugs, make sure to mask stuff on your own. We push release candidates to the tree to catch errors like this in an early stage,before it hits the release or even gets stabilized. When I have access to a gentoo box again, I'll try to apply the mentioned patches in the bug report of Max Parmer to a new revision.
Fixed in openvpn-2.4_rc1-r2 with upstream patches
