mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-27 01:45:58 +03:00
[GH-ISSUE #543] Internal Server Error/Duplicate entry: when try to update an mailbox #519
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#519
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Apr 3, 2014).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/543
Hi,
From the super admin panel, when I try to update an mailbox (change the quota or anything) and the domain contains more than one account, I get the following error:
http://pastie.org/private/pynb5box1agvpgsykdla
On the other hand, when I try to update an mailbox that have only one account per domain, then everything is updated fine.
My setup is the same as posted here (actually, it's the same server): https://github.com/tonioo/modoboa/issues/185#issuecomment-39299680
Thanks in advance for any help you are able to provide.
@tonioo commented on GitHub (Apr 3, 2014):
Hi,
can you take a look at the admin_quota table? (You should see records with empty 'mailbox_id' fields, which is not expected)
@ghost commented on GitHub (Apr 3, 2014):
Yes, some mbox_id is NULL.
@tonioo commented on GitHub (Apr 3, 2014):
Ok, so it means dovecot created those records before modoboa, which is embarassing. This error only occurs when MySQL in in use... you can fix it by filling empty mbox_id fields with the appropriate values (the ID of the corresponding mailbox).
In the future, I'll have to find a way to avoid this issue.
@ghost commented on GitHub (Apr 3, 2014):
I changed manually one of mbox_id with the same id from admin_mailbox table. It worked! =D
Thank you, everything is fine now!