+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: xml document error after upgrade (/t-xml-document-error-after-upgrade)
RE: xml document error after upgrade - kinghat - 2024-05-13
(2024-05-13, 01:49 PM)TheDreadPirate Wrote: Did you also delete library.db?
yep ive tried removing both jellyfin.db and library.db. also tried going back to 10.8.13 and seeing if that would work. still get the activity log db error when i start the container.
might have to start totally fresh here? is there a way i can start over but use my previous server settings and users?
RE: xml document error after upgrade - TheDreadPirate - 2024-05-13
Your user accounts are in jellyfin.db. The settings were in the XML files that were corrupt on null. You probably need to start from scratch.
RE: xml document error after upgrade - kinghat - 2024-05-13
(2024-05-13, 04:34 PM)TheDreadPirate Wrote: Your user accounts are in jellyfin.db. The settings were in the XML files that were corrupt on null. You probably need to start from scratch.
my user accounts dirs are still there, does that matter at all? also, the only xml file that was empty/ruined, as far as i can tell, was the migrations.xml.
EDIT:
so i just stumbled upon a backup i took and most of the DBs have a modified date of late last year(though i think that was the date the data was moved because im missing users in the user dir that were added way before that date). i tried to open its jellyfin.db and got the same disk io error as trying to open my current jellyfin.db so maybe my jellyfin dbs are fine? the error in DB Browser:
Quote:Could not open database file.
Reason: disk I/O error
RE: xml document error after upgrade - kinghat - 2024-05-15
(2024-05-13, 04:36 PM)kinghat Wrote: so i just stumbled upon a backup i took and most of the DBs have a modified date of late last year(though i think that was the date the data was moved because im missing users in the user dir that were added way before that date). i tried to open its jellyfin.db and got the same disk io error as trying to open my current jellyfin.db so maybe my jellyfin dbs are fine? the error in DB Browser:
Quote:Could not open database file.
Reason: disk I/O error
i copied over the jellyfin.db with the activitylog error when running the container and it opens fine locally and contains all the data. i dont think my dbs are corrupt.
RE: xml document error after upgrade - TheDreadPirate - 2024-05-15
Are your disks full? Where is /config located on the host and what is the output of "df -h"?
RE: xml document error after upgrade - kinghat - 2024-05-15
(2024-05-15, 05:16 PM)TheDreadPirate Wrote: Are your disks full? Where is /config located on the host and what is the output of "df -h"?
the config is located in the data dir where all of my other containers data are: ~/containers/data/jellyfin/config
the disk isnt full:
Code:
$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 791M 2.4M 789M 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 107G 89G 14G 87% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 2.0G 253M 1.6G 14% /boot
/dev/sda1 1.1G 6.1M 1.1G 1% /boot/efi
tmpfs 791M 4.0K 791M 1% /run/user/1000RE: xml document error after upgrade - TheDreadPirate - 2024-05-15
Stop the jellyfin container and run this command as root.
docker system prune -a
Start the jellyfin container after.
RE: xml document error after upgrade - kinghat - 2024-05-15
(2024-05-15, 05:29 PM)TheDreadPirate Wrote: Stop the jellyfin container and run this command as root.
docker system prune -a
Start the jellyfin container after.
this system is completely pruned. thats what i did after it ran out of space the first time when i got into this mess. ive run it after ive tried switch back to previous version of jf and back as well.
RE: xml document error after upgrade - kinghat - 2024-05-18
for anyone in the future whom might end up in this situation i seem to have fixed it by simple pulling the migrations xml that i had from a few months ago and replaced it with my current(empty) one instead of letting it be rebuilt by removing it before starting. thanks for your help @TheDreadPirate 🙏
RE: xml document error after upgrade - Sergij A. - 2024-07-05
Hi, and thanks for the post! 🙂
For everyone who doesn't have backup and has this problem:
I was able to fix this problem by deleting migrations.xml (it was empty), and then I deleted system.xml (I made a backup of them).
After that it should start working, but the configuration will be reset, so first create the SAME admin account that you had before. It will error out!
After that empty out the fields and create a new account (not the same username as before), and then complete the setup.
After completing the initial setup, you should be able to log in with your OLD admin account. Then go to the admin dashboard, and delete the NEW account that you made.
And that's it! You actually need to create the other users too, because for me they were deleted, and configure JellyFin again.
I hope that this helps 😀, and is clear!
Bye and have a nice day! 👋