-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Marzban didn't calculate node/users usage for 10 hours (second time this is happening for me) #1199
Comments
I have to say: The first time my nodes were connected without rest, I don't know if nodes supported rest that time or not But the second time which is today, all nodes were connected using "rest" protocol I don't know if this information helps you in any way to find the reason of this issue |
I had the same issue last week. im using Mrazban v0.4.9 (dev) |
Thank you for your report. This issue will be investigated. |
Hi there!
This has been the second time that Marzban doesn't record node usage & users' usage for 10 hours until I noticed all users have been offline for 10 hours and I knew something was wrong, so I restarted Marban and looks like it's all fine now.
This has happened 2 times to me and 1 time for my friend @real_kia and both times I haven't even been awake, I was asleep 10 hours ago from the time panel shows so I don't think I have done anything that caused it, besides I am very careful with Marzban and I haven't once switched to other versions like "dev" or something and I am using Marzban v0.5.2
First time it happened I remember it was on 4th version, not sure which one exactly
Second time, today, v0.5.2
Both times the issue was solved by restarting Marzban, it solved the issue for my friend @real_kia too and unfortunately we didn't check the logs at the time that this happened so all we know is that there's a problem but not exactly sure what's wrong.
Please see if you have any ideas,
Also, I ask anyone who has experienced this to comment possible reason here
The text was updated successfully, but these errors were encountered: