Skip to content
This repository has been archived by the owner on Aug 22, 2021. It is now read-only.

[udpgw] "BConnection_Init failed" keeps spamming over and over #76

Open
PANCHO7532 opened this issue May 17, 2019 · 4 comments
Open

[udpgw] "BConnection_Init failed" keeps spamming over and over #76

PANCHO7532 opened this issue May 17, 2019 · 4 comments

Comments

@PANCHO7532
Copy link

PANCHO7532 commented May 17, 2019

Well, i'm using BadVPN (only the udpgw module) in an VPS with too many connections over the udpgw app (the server is using Ubuntu Server 18.04.2 LTS, 1.0GB RAM) and after a while handling the incoming connections, starts spamming the following lines over and over:

ERROR(udpgw): BConnection_Init failed
ERROR(BConnection): accept failed

The problem gets "solved" when i close the app and i reopen it, but after a while starts spamming again these messages, and refuses any new connection. And this error consumes the 100% of CPU when it happens.

I execute the app with the following arguments:
badvpn-udpgw --listen-addr 127.0.0.1:7300 --max-clients 1000000 --max-connections-for-client 100000 --client-socket-sndbuf 10000000

I don't know if this is an issue or i'm executing the app in a wrong way (or would be an server resources problem)

@4-FLOSS-Free-Libre-Open-Source-Software

@PANCHO7532
Copy link
Author

At least 45 connections
What do you mean with "ulimit"?

@4-FLOSS-Free-Libre-Open-Source-Software

@PANCHO7532
Copy link
Author

PANCHO7532 commented May 17, 2019

This throws me when i execute ulimit -a in console:

root@p7com-serv1:$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 3695
max locked memory (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 3695
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
root@p7com-serv1:
#

And with the "-n" argument throws 1024, and now, if i guess, that number means how many connections/sockets can handle per system user, but i still don't see any logic there, if only i have at least 45/50 connections per day...
...Or i am misunderstanding something in this

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants