-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kernel locking up cpu - reboot of openvpn-server proces fixes it #75
Comments
Thanks for your report.
indicates that the RX queue is full and no more packets can be appended. Is this something easy to trigger? |
This is happening more and more frequent, there is no actual way to trigger it but currently it happens about daily and most of the time a few times after each other. We have now disabled dco to see if we are able to get it stable like that. Is there specific logging I could enable to further debug this? |
Unfortunately there is no easy way, especially because we don't know what is failing. How many clients do you have connected when the problem starts? |
We have 15-20 clients connected, at the time of the issue we see about 10mbit/s in and out (about 4kp/s). |
Hello,
We are seeing an issue for a while now where our server will lockup, CPU will go to 100% usage (by kernel usage reported by netdata). Then memory usage goes up, starts swapping until everything is full and a hard reboot is required. It seems that clients start reconnecting constantly when cpu starts rising as well (not sure if because of the issue or that is causing the issue).
At the time I see a lot of the following messages in the dmesg:
A bit further there seems to be a kernel dump:
Openvpn version: (same issue existed with dco 20231117 and with openvpn 2.6.12)
Kernel version: (it has been giving issues for a longer time already, before this specific kernel release)
Config:
/etc/openvpn/server/uav-server.conf
/etc/openvpn/server/ccd/uav1
Screenshots:
Journalctl logs at that time: after 10:46:13 all clients are reconnecting, the same logs are spammed every second
The text was updated successfully, but these errors were encountered: