mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 03:09:39 +03:00
Integrity constraint violation: 1062 Duplicate entry '1-book-535' for key 'PRIMARY' #5337
Reference in New Issue
Block a user
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 @prohtex on GitHub (Jun 30, 2025).
Describe the Bug
I was recently editing a book with a colleague. This book has many pages and chapters. I started to add a page to a chapter (let's call this chapter "Dogs"), and left the "New Page" window open for some time. My colleague continued to add pages during this time.
When I returned to my open window, and saved the page, I was directed to an "Unexpected Error" page. When I returned to the Book, the "Dogs" chapter was missing, and all the pages that were previously sorted under "Dogs" appeared in the root of the book.
What was especially weird is that navigating to the individual page that was previously sorted under "Dogs" still showed the "Dogs" chapter in the navigation, yet clicking on it yielded a Page Not Found.
I then recreated the "Dogs" chapter, and all the pages magically reappeared under the original "Dogs" chapter, which also appeared again.
This is very odd behavior, and I'm trying to determine what caused it, as the integrity of the book data is very important to us.
Here's a sample from the laravel logs:
Steps to Reproduce
Concurrent creation of pages by multiple users
Expected Behaviour
Pages are created
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
BookStack v25.05.1
@ssddanbrown commented on GitHub (Jul 1, 2025):
Hi @prohtex,
This is essentially the same as #4838, I've just updated the title there to be a little clearer and specific to the issue.
This is down to race conditions in the permission generation as parallel processes can both be attempting to generation permissions for the same content.
Need to spend some time to add proper transaction handling/table-locking, but there needs to be consideration around that to ensure the logic is fail-safe since it relates to permissions (which the current error currently results as, albeit in an inconvenient manner).
This should not impact the integrity of the book data itself, this just relates specifically to permission generation.
If ever needed, these permissions can be regenerated via a command: https://www.bookstackapp.com/docs/admin/commands/#regenerate-access-permissions.
I'm going to close this off since this is already covered by #4838.
@prohtex commented on GitHub (Jul 1, 2025):
Hi @ssddanbrown thanks for your reply. I regenerated perms and we have not noted additional issues. Is the takeaway that two users shouldn't be creating pages at the same time until this is resolved? I haven't done anything specific with permissions since initial install.
@ssddanbrown commented on GitHub (Jul 1, 2025):
This can specifically occur if multiple users perform a permission change action (creation, permission update, role addition/change) when someone else is also making a change within that relevant context. The chance should be very minimal (hence there's been few reports of the scenario) but it can be exacerbated depending on use, system performance and BookStack usage (especially role count). It shouldn't be something you'd have to actively worry about unless it's frequent in your context for some reason.