Community discussions

MikroTik App
 
td32
Member Candidate
Member Candidate
Topic Author
Posts: 111
Joined: Fri Nov 18, 2016 5:55 am

User manager "Total time left" bug?

Sat Jan 14, 2017 4:33 am

Hi
I have user manager running with hotspot on a rb1100ahx2 on latest bugfix 6.36.4
In the Users window in user manger, timing values for each user are not displayed at all.
For all user profiles 'Starts' is set to 'At first Logon'

As you can see in the attached screenshot

Users with Time left = Unknown - have never logged in yet.
X1 and Y1 are expired users, Start time is set to Unknown and "Total time left" is empty when it should be 0
The users with End time different from Unknown are logged in and are still valid, and for this too "Total time left" is empty when it should be like xx hours.

Image

Is this all normal or are this known bugs?
 
Wolfgang
just joined
Posts: 15
Joined: Thu Jan 28, 2016 12:33 pm

Re: User manager "Total time left" bug?

Tue Jan 17, 2017 3:40 pm

Hi,

I have the same issue (http://forum.mikrotik.com/viewtopic.php ... 1&p=576251). As nobody answered, I opened a ticket for it.

Regards,

Wolfgang
 
td32
Member Candidate
Member Candidate
Topic Author
Posts: 111
Joined: Fri Nov 18, 2016 5:55 am

Re: User manager "Total time left" bug?

Tue Jan 17, 2017 9:22 pm

Hi,

I have the same issue (http://forum.mikrotik.com/viewtopic.php ... 1&p=576251). As nobody answered, I opened a ticket for it.

Regards,

Wolfgang
what ros version are you using?

Searching though the changelogs i found this on 6.37.1
*) userman - always re-fetch table data when switching between different menus;
i dont have the possibility to update the ros now, but you can try it.

I also noticed that if you rebuild the database under maintenance the total time remaining is shown correctly, but still it shows nothing for the expired accounts.
And that is a big problem when you want to delete the expired ones
 
Wolfgang
just joined
Posts: 15
Joined: Thu Jan 28, 2016 12:33 pm

Re: User manager "Total time left" bug?

Wed Feb 22, 2017 3:22 pm

Hi,

support found a software related crash on the device which most likely is cause of this. They suggested an upgrade to v6.38.1, which solved the problem.

Regards,

Wolfgang

Who is online

Users browsing this forum: akakua, Amazon [Bot], f008600 and 65 guests