-
Notifications
You must be signed in to change notification settings - Fork 403
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
Randomly getting this exception on macOS #295
Comments
Which kind of OS platform is this? Device type/model? |
@dsommers we see this problem only at macOS. Currently got it on Monteray and Ventura. |
Could you provide more logs? No buffer space might be result of a broken connection or of the client trying to send more than the OS side buffers cna accept. |
@schwabe we will try, but in our currently logging implementation there are so many lines with this error that user cannot capture any useful logs above (log file has size limit):
|
Yeah unfortunately with that log, it is just guesswork what is really going on and what the root cause of the problem is. My guess siince the message is repeated over and over is that the socket is not in a working state anymore cause by some external event like loosing network connection or similar. |
@schwabe @dsommers we've successfully captured the start of problem, but unfortunately it seems not very useful:
|
From user's perspective VPN worked like ~15 minutes and suddenly connections breaks. Another logs example:
In those cases user uses the latest Sonoma 14.2.1. |
What else happens in on the host around those timestamps where this issue occurs? That is, out side of the Connect app? |
@dsommers user that persistently has this bug (around 15-20 minutes after connection) does his usual job -- coding and using VPN to discover internal resources. Tunnelblick and any other openvpn2-based solutions work perfectly in his case. But I will to get more information. Relatively rare other users also get this issue, but like one time in a month. |
But that does not help us understand what happens ... we have quite some OpenVPN Connect users out there, and this is, afaik, the only report on such behaviour. But OpenVPN Connect issues will also be better handled via the proper OpenVPN support channel ... https://openvpn.net/support/ OpenVPN 3 Core library (this project) is just the underlying protocol library which OpenVPN Connect implements. |
@dsommers I understand! I will try to obtain more information, I just shared with what I have on the hands for now. In our case it is not OpenVPN Connect, we are using our own solution based on OpenVPN3 and currently deploying it for thousands of employees. So I created issue here. |
@L11r It is hard for us to guess what your own solution does. Is the source code of that solution available? |
Currently it's not available, but we use it as a high level library. Our code is calling Connect() which blocks a thread until subsequent Disconnect() call or some error returns and releases the thread. We don't reinvent the wheel and just following the docs I hope. Logs from OpenVPN3 are not truncated, we log everyone it sends us. I guess the main difference from OpenVPN Connect is that we are calling it from Go using SWIG. To be clear: I don't wait any magic solution, especially because realistically we are using blackbox from yours perspective. I am just sharing my current observations, because it could be useful for you and someone else. |
Also getting this one, macOS Sonoma 14.2.1.
|
@schwabe @dsommers I can confirm that we are able to reproduce it. You need to use UDP server, allocate as much memory as you can (e.g. using command like this I believe it's because BSD |
The question is if apart from the log message and the log message being shown too often, anything else is broken. If there are coming packets faster in from the tun interface than OpenVPN can send out via UDP, at some point it needs to drop packets. |
@schwabe it breaks the connection at some point. But doesn't reproduce stably, we are working it currently. |
UDP send exception: send: No buffer space available
We are using 3.8.3 with
ovpnagent
, without any special patches. Problem occurs relatively rarely on both Intel and Apple Silicon based machines. We are not getting anything else suspicious in log files except this line and subsequent connection crash. Could try to provide addition details but for know that's all we observe.The text was updated successfully, but these errors were encountered: