Calibre Web wont initiate database on /books
Posted by EineBeBoP
My question: I cant initiate Calibre, it get the New db location is invalid, please enter valid path error After some back and forth with the AI... SparkBox AI replied: 🔧 working on your SparkBox… That log is just the container's normal startup boilerplate — calibre desktop-integration warnings that are expected/harmless, and no crash, no write error. It doesn't capture the actual moment you submit the DB-path form (Calibre-Web's app-level errors on that screen usually don't hit stdout the same way). So the container itself is healthy and running — the failure is happening inside the app's own error handling on that screen, not something crashing the container. At this point we've ruled out: - mount wiring (confirmed correct, /books is real) - SparkBox-managed folder perms (fixmediapermissions ran clean) - POSIX ACL grant (setfacl won't persist on this UGOS share) - world read/write via chmod (didn't help either) - container health (running fine, no crash) That's everything on my side. Since chmod and setfacl both failed to unblock it, and the container logs show no write error at all, this looks like either a UGOS-specific filesystem enforcement I can't fully see from POSIX tools, or a genuine Calibre-Web bug/behavior with this NAS's filesystem type that needs Tom's eyes. I'm not confident I can get further with what I've got here — click "Share to demox" below so Tom can see the full picture (the getfacl output, the chmod result, and the fact that both standard permission fixes didn't take). That combination is unusual enough it's worth him looking at directly. What I …(reply truncated — full chat sent to Tom)
1 replies
Chris wrote:
Hey EineBeBoP — that error used to show up because Calibre-Web's setup wizard won't accept an empty library folder, so SparkBox now auto-creates a starter database the first time it starts. Since your AI chat already ruled out perms/ACL/chmod, can you check one thing: does a file called metadata.db exist inside your books folder? If it's missing, that auto-create step is silently failing on your NAS, which lines up with the setfacl issue you already found. Let me know either way — if it's still stuck after that, I'm flagging this for Tom to look at the NAS side directly.