linuxdcpp-team team mailing list archive

[eMTee <1088638@xxxxxxxxxxxxxxxxxx>]

https://answers.launchpad.net/adchpp/+question/690223 brought up this report again. Sorry if this wasn't handled the time when reported.
The patch itself was probably ignored back then because in case of the said error the obvious action is to decrease the number of users by disconnecting some with a parameter that tells those client that they cannot reconnect immediately. If it'd do otherwise then it would periodically overstrain the hub (server's bandwith) and so the error would most probably periodically reoccour.
So what the code does seems legit - IF the problem that produces this error is really a lack of bandwidth and not something else, like a weird behaving network, ISP, etc...
I can add that I've never seen this error running an ADCH++ hub and I have been doing so for 10+ years.
>From what I see in the code this error can happen if the socket buffer is getting overflown for a significant number of online users. Using a value from a formula the code decuces that there's too much users' socket buffer is owerflown for a certain amount of time so it must be an out of bandwith issue, hence disconnects the clients of those users.
At the same time the code uses configurable base parameters so modifying those might result this error situation going away.
Namely they're the OverflowTimeout and BufferSize parameters, configurable in the adchpp.xml file. I'd recommend to raise those values by 1,5x...2x steps and see the effect.
As the comments in the config file say, larger BufferSize value would result more memory usage for ADCH++ but I don't think today's computers' available memory would be a barrier to do a even a significant rise of buffer sizes.
A larger OverflowTimeout value would certainly result slow or improperly disconnecting users' removal from online state being slower than before but that could be a reasonable tradeoff in the reported situation.
Please carefully, but do experiment with those values. This bug report can possibily be investigated further if the real cause (lack of bandwith) is out of question and config parameter changes cannot solve the issue.

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/1088638

Title:
  Not enough bandwidth available, please try again later

Status in ADCH++:
  New

Bug description:
  The error "Not enough bandwidth available, please try again later" in
  ClientManager::verifyOverflow shouldn't be sent with the "TL -1"
  param, as quite a few users receive that error after the hub has been
  restarted.

  Because of that it takes a long time to get all users back in the hub
  as their clients won't reconnect automatically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/1088638/+subscriptions