-
Notifications
You must be signed in to change notification settings - Fork 76
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
ShokoServer gets "stuck" and needs to be restarted #1227
Comments
Yes, I want it. Can you make a torrent and DM me the torrent file on discord? That's just the most obvious way I can think of. At 200MB, you can upload it in shoko's discord with our nitro tier, as well |
Update: I never bothered to check if non queue related API calls still function normally, while the queue is stuck. Note the timestamp of 18:45 (6:45 pm) and as of writing it is 20:55 (8:55 pm) I can still navigate through the web ui, just fine. Therefor I want to clarify only the queue is stuck. Just in case here the logs from today. The Clear All function only clears the non-running item, and the running item blocks any incoming item. Btw, when I said "restart" shokoserver - I meant I need to kill the process, using tray icon to shut it down keeps the process running in the background. |
I probably just pushed the fixed |
@Rand-Random can you verify (keep an eye on it and report back) that this is fixed? |
@da3dsoul |
Got the error again, but not daily as I used to. Currently running shoko from within visual studio code, when I figured out what is going on I will report back, for now feel free to ignore the issue. |
We have someone else reporting a similar issue, but he's so all over the place that I don't even know if it's an issue or the setup. Keep me posted! |
It happened to me yesterday but i forgot to do a trace dump (like i promised). |
I do believe it is related to the changes of those commits
06d923d
5c5b5b1
and that this line simply calls .Result and there for also blocks
ShokoServer/Shoko.Server/Providers/AniDB/UDP/Connection/RequestLogin.cs
Line 53 in 2896517
The time frame of the commit seem to match when I noticed the issue at first, though I couldn't say it for sure.
I could offer a memory dump for further analysis, but it is ~3 GBs in size, zipped still ~600 MBs, 7zip manages to lower it to 200 MBs, but still to big to attach it here. If you need/want it, you would need to tell me how I could share it.
The text was updated successfully, but these errors were encountered: