-
Notifications
You must be signed in to change notification settings - Fork 263
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
error 409 / Mailbox is locked #3159
Comments
This is OK if you have a very large mailbox. Is that the case for you? Run |
I do have a huge mailbox... Sorry what id ? I'm asking because |
Open the app. Go to the individual INBOX of your account. See the URL. It something like |
Alternatively look into the |
thanks :
|
Okay, that can take a few minutes. But it should eventually finish.You can check the |
ok thanks ! I will try to be more more patient and close this if it works... |
... just to say I'm running into other error messages during the process (and it has still not ended, I doubt it will) :
and also GET requests that meet 409 errors, and seem to concern mail.js :
|
That is not an error. Thus the 4xx status code. There is just more than one process that tries to sync. And to prevent concurrency issues we lock the mailbox during the synchronization. The only case where the MailboxLockedException is an issue is when the original sync process was killed (due to an error) and the mailbox remains locked. But even then, the lock will be released after 5min. Keep an eye on your logs. If there is a sync error then it will show up in nextcloud.log. |
I do have some errors on the server log :
|
That is unrelated to the synchronization, though. |
I would tend to think that 4xx are technically errors (at least on the client side) and I rather not have any... The script is still running 5 hours later and the database doesn't show any progress :
|
when I open the URL retrurning a 409 in a new tab (i.e.
(forbidden access) Do you have any idea what could cause this CSRF issue ? |
Then tell me, what would be the appropriate HTTP status for a request that fails due to locking?
That is how our CSRF protection works in Nextcloud. This is not really an issue as a user would never directly access the API route and the browser code correctly sends the required token. |
ah ok, sorry I hadn't understood the 409 was related to the locking ! still. the inbox never shows up and the database shows no progress... how can I troubleshoot my problem then ? |
You could lower your log level to 0/debug and enable debug mode. Then you trigger the sync from the CLI with Reset log level and debug mode afterwards. |
closing due to lack of feedback |
i'm experiencing the same symptoms as originally reported. then, i ran
i'll dig into this some more, but posting here for visibility |
looks like this error is at the root
not sure when this started or how i got into this state, but i now see in master some updates that address the null exception |
testing this solution now as this seems to be the root cause with my environment (using alpine): docker-library/php#240 (comment) .... confirmed. this works. looks like the base nextcloud fpm alpine images will need this for iconv to work correctly. |
looks like this issue was introduced in 4a9ad43#diff-d58572e8c8a251330835114e6e2731fd6ae84a19658ba3f6b578ab137dbcdf61 there is now a PR to address this here: nextcloud/docker#1300 and the issue filed nextcloud/docker#1299 |
The app used to work but I did a few refactoring on my server (going from native debian lamp to dockerised Apache + PHP FPM with traefik). The issue might be related.
Actual behavior
I can't get to the inbox, endless spinning wheel. Chrome console shows an error 409 :
xhr.js:178 GET https://nextcloud.xxxxxx.net/index.php/apps/mail/api/accounts/3/folders/SU5CT1g%3D/messages 409
And on Firefox :
Content Security Policy: Les paramètres de la page ont empêché le chargement d’une ressource à eval (« script-src »).
then :
[INFO] mail: Mailbox is locked {app: "mail", uid: "kro", error: MailboxLockedError at t.convertAxiosError (https://nextcloud.xxxxxx.net/apps/mail/js/mail.js?v=3808e48f-102:844:291) at https://nextcloud.xxxxxx.net/apps/mail/js/mail.js?v=3808e48f-102:355:86791 at async Promise.all (index 0)}
Mail app
Mail app version: 1.3.5
Mailserver or service: Infomaniak (very good email service)
Server configuration
Operating system: Dockerised LAMP services (not nextcloud image) on debian buster.
Web server: Apache
Database: MariaDB
PHP version: FPM 7.4.6
Nextcloud Version: 18.0.4
Client configuration
Browser: latest stable Chrome or vivaldi or firefox
Operating system: Windows
The text was updated successfully, but these errors were encountered: