4.6 - API session user not removed from active user list ...

[pekr]

Hi,

just doing some experiments with API using REBOL language, and found out that each time I log, no matter how do I terminate the session (“/quit” or just closing the TCP port), I can see the list of API (demo) users is growing. I noticed that this bug was fixed in 3.25. But I am doing my tests on 4.6 - I just wonder if the fix did not get it to 4.6 branch, or I am doing something wrong?

Thanks,
Petr

[SurferTim]

Seems like a common problem for the V4.x OS. Another user is having exactly the same problem with V4.7.
http://forum.mikrotik.com/t/php-api-connection/33417/1
I recommend the same for you. Run the script a few times to get a few active users in the list, then make a supout file and email to support (at) mikrotik.com with a short explanation of the problem, and what you have tried.

[pekr]

OK, I can send suppout file, but I think that they know what the bug is about. Taken from 3.25 changelog:

*) api - closed sessions were not removed from the ‘/user active’ list;

From the thread you suggested, it is not clear what version was the user using …

EDIT: btw - this happens from python API wrapper, as well as from my REBOL tests, so I think I am not doing anything wrong with REBOL …

-pekr-

[SurferTim]

I thought it was clear.

@omidkosari

(snip) RouterOS v4.7

This user tried with a couple different languages, with exactly the same result.

[martini]

confirm this bug

[Chupaka]

have you tested previous versions? at least in v4.2 all is still okay

[omidkosari]

Ok . i will follow my other thread http://forum.mikrotik.com/t/php-api-connection/33417/1 here because this board is more popular .

@omidkosari

I am also using http://wiki.mikrotik.com/wiki/API_PHP_class . it worked good but after some hours API returned cannot get challenge and then script could not connect to API anymore .
Another strange thing is , i have seen a lot of sessions in “/user active print” . there are more than 44500 sessions there from user which i used for API connection but i have used $API->disconnect () .
RouterOS v4.7

@omidkosari

@SurferTim

You aren’t following that example literally, are you? It does a login, one command, then logs out. You can log in once, do as many commands as you need to do, then disconnect (logout) once when you are finished for the session.

The script runs each time the specific page hits by a user so it should login , execute the command and then logout . the only way is a persistent connection with something like CURL or pfsockopen which needs customization of API_PHP_Class .

@SurferTim

Maybe a “/quit” command sent just before the disconnect might drop the user from the active list.

Tried but unfortunately not worked

@omidkosari

I have also test with mikrotik official python api client . it has same problem and does not clear the admin from “/user active print” .
even after sending /quit . with /quit it successfully closes the connection and raises “connection closed by remote end” but the admin is still remains alive at “/user active print” .

The problem is not just the growing number of active sessions . the main problem is cannot get challenge after some hours and then unable to connect to API

[omidkosari]

I received a reply from Mikrotik Support

Hello,


Thank you for the report. We are aware of this problem and it will be fixed in
next version. Currently only option to clear active users is to reboot the
router.


Regards,
Maris
\

Just for share

[Chupaka]

anyway, it’s about active users, not challenge…

[omidkosari]

@Chupaka

anyway, it’s about active users, not challenge…

ummmmmmmmm . you mean “cannot get challenge” will not solve ?!

[Chupaka]

I mean, I don’t see any connection between those two things…

[escentrix]

I am still seeing this problem in RouterOS version up to V4.13. Using the newest PHP API, when I open a connection I see the Active Users list increase by 1 with an “unknown” field in the ‘Via’ column. I am using the disconnect() function at the end of the communication, but I do not see the user ever get removed. Eventually this list will get very large with tens of thousands of active users.

I will be resubmitting this bug to the support guys just to make sure they are aware.

@Chupaka
This is when the “cannot get challenge” comes into play. It seems when the API creates enough active users the board will start refusing any more connection attempts. Turning debug on in the API returns this string. The two seem to be linked in this way from my tests.

[dssmiktik]

@escentrix

This is when the “cannot get challenge” comes into play. It seems when the API creates enough active users the board will start refusing any more connection attempts. Turning debug on in the API returns this string. The two seem to be linked in this way from my tests.

Not really. The core issue (api connections not being cleared), should not be related to api challenge. The api challenge problem is only the side effect of multiple api connections (ex. when not cleared out). The underlying issue is that the api connections are not being cleared on disconnect. This is a known problem, and Mikrotik know about it already. They say it will be fixed in v5.x

[Chupaka]

this IS fixed in v5, but it’s still RC…

[ispsoft]

I’m currently using 5.0v and the problems remains… any suggestion ?

[Chupaka]

@ispsoft

I’m currently using 5.0v and the problems remains… any suggestion ?

v5.0rc4 is definitely removes logged-out API connections. what exact version do you use?

[ispsoft]

I’m currently using v5.0rc4 … after 10 or maybe 12 operations the mikrotik returns a message like “.. Already have such name” and the connection made within Users\Active remains there and the via is “unknown”… we are currently modifying queues and this application is working fine in mikrotik up to 4.2 ! … Trying to working around I made some modification to connection software generating different tags in each operation but the problem remains.