Has anyone seen this error? I have a large subnet setup for DHCP /21, hotspot is setup, with 700 max users. Rate limiting of 128kbps up and down for each user. I was using 2.9.22 just yesterday and we wanted the graceful handling of lost DHCP Leases in 2.9.27. So we upgraded to 2.9.27 and now we have lost stability for the hotspot. When these errors occur, new hotspot users cannot log in, but existing users are still able to get out. We didn’t have this in 2.9.22.
12:53:25 hotspot,error,info,debug XUser (10.87.10.50): internal error: login failed: failed to add queue: already have such name (6)
12:53:25 hotspot,info,debug XUser (10.87.14.67): trying to log in by https
12:53:25 hotspot,error,info,debug XUser (10.87.8.82): internal error: login failed: failed to add queue: already have such name (6)
Had to set no rate-limit for the users, then they were able to logon, but this is not preferable.
[admin@MikroTik] ip hotspot user profile> /queue simple print count-only
261
[admin@MikroTik] ip hotspot user profile> .. .. active print count-only
110
Interesting. We aren’t having hardly any issues with 2.9.27 and hotspot. We are running into the problem when someone has lost their lease, but is still logged in, and then can’t login again due to only allowing 1 session per user…it doesn’t happen often, but does happen. Other than that, this has been the best 2.9 version for us yet (for hotspots).
