memos: Recurring bug with docker container: failed to get user: interrupted (9)
Describe the bug
Hello, I’m selfhosting memos (with sqlite db) and I have a recurring bug that I don’t know how to solve. From time to time, I will get a popup saying failed to get user: interrupted (9) on the web interface. After this, the interface displays a blank page. In the logs of the docker container I get those lines:
2024/09/13 16:44:59 ERROR server error method=/memos.api.v1.ResourceService/GetResourceBinary error="rpc error: code = Internal desc = failed to get resource: context canceled"
2024/09/13 16:44:59 ERROR server error method=/memos.api.v1.ResourceService/GetResourceBinary error="failed to get user: interrupted (9)"
2024/09/13 16:44:59 ERROR server error method=/memos.api.v1.MemoService/ListMemoProperties error="failed to get user: interrupted (9)"
2024/09/13 16:45:00 ERROR server error method=/memos.api.v1.MemoService/ListMemos error="failed to get user: interrupted (9)"
2024/09/13 16:45:00 ERROR server error method=/memos.api.v1.MemoService/ListMemoTags error="failed to get user: interrupted (9)"
2024/09/13 16:45:07 ERROR server error method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile error="failed to get user: interrupted (9)"
2024/09/13 16:45:07 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)"
Most of the time it is solved by restarting the container, but it can be very inconvenient if I’m not home. I have no clue what triggers it.
Any idea what is the problem is? Can I do anything more to help find the root cause?
Steps to reproduce
I have no clue
The version of Memos you’re using.
v0.22.5
Screenshots or additional context
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 4
- Comments: 23 (11 by maintainers)
In this case I have just one resource in the latest memos, a screenshot. I only ever attach photos or screenshots. It had been displayed before without issue, I don’t know what changed. It definitely happened before 0.22.5.
Not being able to reproduce is not a valid reason to close an issue imo, as the issue is still here. But your project, your rules! I want to clarify that in my case memory is no issue, and also want to highlight that just restarting never made anything crash for me. What made it crash was, as I understand it: restarting + super fast loading of memos with pictures in my browser. Just as an additional test, I tried the proven “scroll super fast and load everything” method again, with the container already running for a long time, and nothing crashed.
Why closing it? It is an important bug!
make sense. it look all fine until I click the explore page.
I have the same problem. For me it seems to be triggered right after posting a memo but I’m not completely sure, as I haven’t tested it enough yet. I only restart my container when this issue happens and I never move it so I don’t think that that’s the trigger for me.
I also get the blank page when memos stops working, the
failed to get user: interrupted (9), and whenever I try to log in after this bug happens it saysFailed to find user by userame <my-username>.I’ve also installed Memos through Docker, and the problem persists until I restart the Docker container, and quickly returns. I’m using v0.22.5. Here are my logs when the error happens:
I share the same problem (complete overlap, in my opinion), running the container version of Memos (v.0.22.5) on Coolify v.4.0.0-beta.325. I have two separate instances on two subdomains, both on SQLite, one runs fine, while the other doesn’t. The problems occurred when I added another user I since deleted. Since deletion didn’t resolve the problem, I suspect another issue.
I had this issue with both my laptop (Firefox) and my phone (Vanadium, a Chromium fork) so I don’t think it comes from the browser. My images are all below 3MB.
But now that I think about it, it might have something to do with the way the container gets stopped. I run watchtower every night for updates, and before 0.22.5 I had memos on the stable tag, which means it got restarted frequently. Indeed memos has been running without issue for a few days, but I just managed to make it crash:
I managed to view a few images without issue, but one specific memos with three pictures made it crash. The images never appeared, no more memos could be loaded, the same log lines appeared and a blank screen was displayed on refresh.
Just after this I stopped, removed and started the container once more. I just waited a little bit, and then I was able to browse memos without any crash. I hope this helps!
0.22.2 also has this problem