Recurring bug with docker container: failed to get user: interrupted (9) #3922
Comments
|
What type of resources (attachments) are you viewing? Images? |
|
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. |
|
I was wondering if the new thumbnail feature was causing this, but if it happens before 0.22.5 then it's something else |
|
0.22.2 also has this problem |
|
I've not been able to reproduce this, if I had to take a stab in the dark it would be something to do with your browser telling the server to close the connection (context), the server being mid db activity and not unlocking the db and the subsequent db requests not being allowed due to the lock e.g. getting the user. but the code looks like its handling the connection closure so not sure and also not sure why your browser would tell the server to close the connection
Are you viewing large images? |
|
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! |
|
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. |
|
@ozls do you always have the same successful web request before the first |
|
Any progress? You may need to upload several images (100~ kb or 2 MB+) to reproduce this problem. I tried several versions and the problem remains. |
|
@RoccoSmit The bug did not happen since I stopped removing and restarting the container on a regular basis so I'm confident I found the trigger. Nevertheless I made it happen once more to try to answer your question. I had to click "load more" a few times, and then the the memo with three pictures made it crash again. Here is the complete log from container start to crash: |
|
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 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: |
|
also get the same error |
And when I get this error, I need to log in again. |
|
I tried, but could not reproduce the issue on my end for debugging |
you are welcomed to use my instance for debugging. |
|
do we have any update on this? |
|
I have no evidence but I suspect it may be connected to the 'explore' page. I noticed the other day that loading it crashed the instance. However, I've been getting almost no crashes recently. Perhaps the issue mostly fixes itself after some time? |
make sense. it look all fine until I click the explore page. |
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: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
The text was updated successfully, but these errors were encountered: