SOLVED: Can't "parse/scrape" all music into library

[alike]

I will try to rebuild the whole mp3 database. Just remove the library from Jellyfin and then add it back and see how things go. Its quite big, but that's the way it has to be I guess.

I noticed the library is still present and playable even after I removed it from the library gui. Tried to restart the server and it did some automatic cleanup of playlists. The result is the same however. I have noticed this before as well when removing libraries. The folder is removed from C:\ProgramData\Jellyfin\Server\root\default when I check. Perhaps this just take some time? I've waited for 10 minutes. Or is this a symptom of the bad library database?

[alike]

This is the log when I try updating the library in question:
https://privatebin.net/?10263f369893368e...4GZhnX1jV4

I then tried

But the new.db is 0 bytes. Something it does when there are errors in the sql, I am told.

I tried understanding what this error message relates to. I have the database in sql format in plaintext in front of me. It looks ok to the eye but its almost a million lines of data. Any idea how I can get SQLite to give me the lines that it thinks I need to fix or fix this automatically itself? I've googled a lot on this but looks like one need to find a error message in a log that says which lines are bad and then fix or remove them.

This didn't help enough. It doesn't say whats wrong as you see.

If I create a new DB for library, will all the users watched lists and so still be kept and connected to the new DB? Its the user and history data that is most important for me.

[alike]

I tried something else. I had in the SQL file I had dumped to dump.sql, a line that said "ROLLBACK; -- due to errors" at the end of the file. I changed this to "COMMIT;" and then dumped the dump.sql to .db using command "SQLite3 library.db" and then ".read dump.sql"

Now the former bad library is working at 85% syncing the changes since... a along time ago. I don't know if I actually fixed the database, but at least I am allowed to search for changes on it for now. Very excited! I'll share the jellyfin server log later when its finished.

[TheDreadPirate]

I'm not sure which DB watch status is stored in. Assuming watch status saved in jellyfin.db, removing library.db and re-adding libraries would likely result in watch status reset anyway.

[alike]

Since the db was not syncing while I tried to remove and re-add it, everything stayed the same before I repaired the the database file. So when it was working again and started updating the DB, it actually didn't ruin my watched/listened list. And it looks like most if not all my music got scraped fully or partly, with most of them having pictures and correct track-lists and so on from what I could check in the short time I spent doing it.

There was a lot of activity in the log as the update of the DB was working. I started scraping the repaired library around 17.30 or so.
Warning, the log is huge.
https://privatebin.net/?94f92bb24e0bf315...dscFTr7Xu1

Entirely different issue: I seem to have some issues with my webhook plugin, not sure what but will have to look at it when I have time.

All in all very happy and proud that I managed to repair the DB.

[TheDreadPirate]

Can't help with webhook. Never used it.