HSNM Forum

New error coming in tonight,

internal error: login failed: failed to add queue: already have such name (6)

Error reporting is 559153@DOMAIN (10.1.92.144): internal error: login failed: failed to add queue: already have such name (6)

Had this 3 times for one site, not sure what the issue is.

After I remove the client from the queue they can login. Maybe the queue hasn't removed the user on disconnect and it's stuck.? We do 5 simul users and this occurs even with only 1 or 2 queues active.

Hi Spike
Where did you see that error? Not on HSNM? I think you saw it on Mikrotik GW.
Probably when the user has been disconnected the queue has not been automatically removed and so then you had that error.

I haven't any other idea

Best regards

So we're getting quite a few more of these now. Over a couple of sites. Going to check Mikrotik Forums too, but thought I'd reply and nudge on this side too..

Hi Team,

Cross Posting. https://forum.mikrotik.com/viewtopic.ph ... 84#p830784

It died down over a few months (probably COVID) but now that we're cranking back up for xmas it's starting up again. It appears as if dynamically created Queues from RADIUS Auth are not flushing post logout. I have 8 Active Hotspot clients but 235 Queues. Posting on both forums to see if anyone has some insight.

Dear Spike,
can you please config us which version of ROS are you using?
Have you tried to upgrade your Mikrotik ROS to see if it fixes your issue?
Have a nice day

Hi Team,

ROS 6.45.9
ROS 6.44.6 x 2

Maybe do you have some custom Ros script?
I can only suggest upgrading your ROS version to the latest available.
Please note that this is not an HSNM problem but a Mikrotik one.

hi spike,

have you ever sorted this problem? also getting the same issue ROS 7.2.3

tx
chris

Funny, This issue seemed to go away for a couple of years and I forgot about it. Now it's back again for one site.

Mikrotik 7.13.4
Script can't remove dynamic object.

The only way to flush is to reboot the router. Currently doing another round of digging to find out the nuances of it all. Looking back at my historical post, this was also present in 6.4x but we didn't see it for a while so interested to hear in anyone else that has encountered and resolved.
It does look like the HSNM script is not flushing out the Dynamic Queue any more, but I thought this was a post 7.4.x Mikrotik update.. weirdness.

Hello Spike,
we have opened a ticket with Mikrotik support to urge them to investigate the issue or to give us the option of removing the old dynamic queues for users, so that we can use a script that removes them in the event of an error.
S.T.