mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-07 19:06:05 +03:00
Several Books are inaccessible. #1707
Closed
opened 2026-02-05 01:40:23 +03:00 by OVERLORD
·
6 comments
No Branch/Tag Specified
development
l10n_development
further_theme_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
pull-request
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#1707
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking 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 @mattstanyon-tall on GitHub (May 4, 2020).
Describe the bug
A number of books are inaccessible. While they still appear in their shelves from the Shelves view, when a book is directly selected, it errors Lost Books.txt, or if you drill down into a shelf the book no longer appears.
The data within the books seems to be accessible from the search.
When running the php artisan bookstack:copy-shelf-permissions --all --no-interaction command, we see errors in the laravel.log KB_copy-shelf-permiss.txt.
Looking into MySQL, we see the auto_increment value of the joint_permissions table is 4294967295, which seems to correspond to the following:
https://stackoverflow.com/questions/17690926/failed-to-read-auto-increment-value-from-storage-engine-error-number-1467/17690982
Interestingly, we see a huge jump in the value for the joint_permission id column (no idea if this is a problem, or expected, etc.). joint_permissions_ai_gaps.txt
Expected behavior
Books should not disappear!
Your Configuration (please complete the following information):
Additional context
Add any other context about the problem here.
@mattstanyon-tall commented on GitHub (May 4, 2020):
We ran the following commands which seems to have resolved the issues:
Although, we suspect it will come back. In addition, the following command is run hourly, which does seem to increase the auto_increment value on each run:
@ssddanbrown commented on GitHub (May 4, 2020):
Hi @mattstanyon-tall,
Thanks for extensive detail and investigation you've done so far.
I've wondered when we'd first come up against a 32bit integer id issue. At a rough guess the
php artisan bookstack:copy-shelf-permissions --allcommand will effectively delete and insert:Can increase very quickly if the number of entities or roles is high in your instance, Then coupled with running that every hour.
Still, 4 billion is a big number. I wonder if the way the batch operations cause MySQL to jump the id much further than expected.
I've assigned this to be looked at for the next release. I'll check if the id value is really needed or look at changing the permission generation process & column type if it is needed.
@Cidwill commented on GitHub (Jul 21, 2020):
Hi, has there been any news on this issue? We've recently had to add this command to our hourly Cron as we found that permissions were not copying shelves when books were made from within the shelf with the new book button.
@ssddanbrown commented on GitHub (Jul 21, 2020):
Hi @Cidwill ,
That's a bit of a different issue (expecting permissions to copy down on child book creation) whereas this issue is focused to reaching database limits in the permission system.
@Cidwill commented on GitHub (Jul 21, 2020):
You're absolutely correct. Consider that detail off topic (by attempting to add detail I put the horse before the cart).
I mentioned it because we are using the function mentioned as a workaround, and running it hourly also as the original poster was doing.
@ssddanbrown commented on GitHub (Aug 4, 2020):
I've now pushed up a change to remove the old auto-incrementing primary key since it was not used. This will be part of v0.30.