mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #523] [Bug]: Queue not loading unless filter is applied. WAL file causes malformed schema on startup #336
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#336
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 @Percy2Live on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/523
Originally assigned to: @maziggy on GitHub.
Bug Description
Hi,
after updating to the latest version, I ran into an issue where the print queue does not load correctly. I observed this behavior before, hence it's likely not related to the update but due to a corruption of the database when the container is restarted.
Symptoms
The queue page appears empty after a restart of the container.
As soon as I apply any filter, entries suddenly appear. Restarting the container did not help.
Deleting the bambuddy.db files did fix the issue, but then of course the data is gone
Root Cause (identified)
The problem turned out to be related to SQLite WAL mode. The following files are present:
bambuddy.db
bambuddy.db-wal
bambuddy.db-shm
The issue persisted until I stopped the container and deleted the -wal and -shm files (keeping the .db)
After removing the application started normally and the queue worked again.
This strongly suggests that: The WAL file contained inconsistent or corrupted schema data or the application does not properly checkpoint/clean WAL during updates/restarts, or schema migrations are not WAL-safe
Environment
Installation method: Docker via Docker Compose
Database: SQLite (default configuration, WAL mode enabled)
Issue appeared after updating Bambuddy to v0.2.1b3
Attached
I am attaching the original files which caused the issue:
bambuddy.db
bambuddy.db-wal
bambuddy.db-shm
If required I can also share the newly generated wal and shm files for comparison
The issue should be reproducible with these files.
Thanks for your work on Bambuddy 👍
Expected Behavior
Queue should be displayed normally even with no filters applied
Steps to Reproduce
not 100%. Happens sometimes after updates and restarts of the container:
Printer Model
P1S
Bambuddy Version
0.2.1b3
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Docker
Relevant Logs / Support Package
db.zip
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 25, 2026):
Need a support package please.
@Percy2Live commented on GitHub (Feb 25, 2026):
Put in the broken files and created a loading package:
bambuddy-support-20260225-154500.zip
Queue looks like this:
@maziggy commented on GitHub (Feb 25, 2026):
There's something wrong with your setup. Bambuddy cannot connect to your printer via FTPS and MQTT connection is stale.
Do you really have devdeloper mode enabled on the printer?
@Percy2Live commented on GitHub (Feb 26, 2026):
Yes, verified it - it's enabled
Beside the reported bug everything runs fine
@maziggy commented on GitHub (Feb 26, 2026):
Very weird. Did you reboot the printers after enabling developer mode?
@maziggy commented on GitHub (Feb 26, 2026):
Ah wait, never asked before: iptables rules are there?
@Percy2Live commented on GitHub (Feb 26, 2026):
Printer rebooted, yes. iptable rules are applied, and you verified that at another bug report.
This is a new support package:
bambuddy-support-20260227-004643.zip
How does this look? The only difference is I deleted the WAL and SHM (same db) and started the container again
@maziggy commented on GitHub (Feb 27, 2026):
Fixed in branch 0.2.1. Please let me know if it works now for you.
@Percy2Live commented on GitHub (Feb 27, 2026):
I'll test, unfortunately this takes time as the issue appears random and cannot be triggered.
After updating to 0.2.1 I noticed the certificate handshake wasn't working anymore, had to use new certificates in bambu studio to connect to bambuddy again. Took me some time to figure this out. Don't know what caused this, just so you know in case you receive more reports after people upgraded to 0.2.1. For now this can be closed, in case the db bug appears again I'll reopen it.
Thanks for fixing!
@maziggy commented on GitHub (Feb 27, 2026):
@Percy2Live commented on GitHub (Feb 27, 2026):
I am aware of this. But I have persistent certificates through the volume, did not change hosts or update the slicer (at least not knowingly)
@maziggy commented on GitHub (Feb 27, 2026):
When you reinstall Bambuddy it creates new certs.