+- 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 - wyrtz - 2024-07-16
Created an account just to post this.
After fixing the out of disk space issue, jellyfin was producing the errors as described in this thread. Inspired from reading this thread, I was able to recover quite simply however:
-Stopped jellyfin container
-Deleted (empty) migrations.xml file
-Edited system.xml: changed <IsStartupWizardCompleted> from true to false.
-Stared up jellyfin container, all worked as before (no startup wizard or anything)
Note that I am simply listing the steps I took, I cannot fully explain why it works. From looking in the logs, it seems like setting startup wizard to not completed made jellyfin treat this as a fresh install:
Code:
[13:02:23] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["CreateNetworkConfiguration", "MigrateMusicBrainzTimeout", "MigrateNetworkConfiguration"]
[13:02:25] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["DisableTranscodingThrottling", "CreateLoggingConfigHeirarchy", "MigrateActivityLogDatabase", "RemoveDuplicateExtras", "MigrateUserDatabase", "MigrateDisplayPreferencesDatabase", "RemoveDownloadImagesInAdvance", "MigrateAuthenticationDatabase", "FixPlaylistOwner", "MigrateRatingLevels", "FixAudioData"]I haven't noticed any negative effects by changing this. After successful run of jellyfin, I shut down the container, changed it back to true and started jellyfin up again.
Hope this will help anyone with the same issue out there. I really feared setting it all up again and wasting a time on that.
RE: xml document error after upgrade - JesusSanjuan - 2024-08-13
(2024-07-16, 01:11 PM)wyrtz Wrote: Created an account just to post this.
After fixing the out of disk space issue, jellyfin was producing the errors as described in this thread. Inspired from reading this thread, I was able to recover quite simply however:
-Stopped jellyfin container
-Deleted (empty) migrations.xml file
-Edited system.xml: changed <IsStartupWizardCompleted> from true to false.
-Stared up jellyfin container, all worked as before (no startup wizard or anything)
Note that I am simply listing the steps I took, I cannot fully explain why it works. From looking in the logs, it seems like setting startup wizard to not completed made jellyfin treat this as a fresh install:
Code:[13:02:23] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["CreateNetworkConfiguration", "MigrateMusicBrainzTimeout", "MigrateNetworkConfiguration"]
[13:02:25] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["DisableTranscodingThrottling", "CreateLoggingConfigHeirarchy", "MigrateActivityLogDatabase", "RemoveDuplicateExtras", "MigrateUserDatabase", "MigrateDisplayPreferencesDatabase", "RemoveDownloadImagesInAdvance", "MigrateAuthenticationDatabase", "FixPlaylistOwner", "MigrateRatingLevels", "FixAudioData"]
I haven't noticed any negative effects by changing this. After successful run of jellyfin, I shut down the container, changed it back to true and started jellyfin up again.
Hope this will help anyone with the same issue out there. I really feared setting it all up again and wasting a time on that.
Me funciono sin ningun problema,
RE: xml document error after upgrade - RoyBarina - 2024-08-26
(2024-07-16, 01:11 PM)wyrtz Wrote: Created an account just to post this.
After fixing the out of disk space issue, jellyfin was producing the errors as described in this thread. Inspired from reading this thread, I was able to recover quite simply however:
-Stopped jellyfin container
-Deleted (empty) migrations.xml file
-Edited system.xml: changed <IsStartupWizardCompleted> from true to false.
-Stared up jellyfin container, all worked as before (no startup wizard or anything)
Note that I am simply listing the steps I took, I cannot fully explain why it works. From looking in the logs, it seems like setting startup wizard to not completed made jellyfin treat this as a fresh install:
Code:[13:02:23] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["CreateNetworkConfiguration", "MigrateMusicBrainzTimeout", "MigrateNetworkConfiguration"]
[13:02:25] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["DisableTranscodingThrottling", "CreateLoggingConfigHeirarchy", "MigrateActivityLogDatabase", "RemoveDuplicateExtras", "MigrateUserDatabase", "MigrateDisplayPreferencesDatabase", "RemoveDownloadImagesInAdvance", "MigrateAuthenticationDatabase", "FixPlaylistOwner", "MigrateRatingLevels", "FixAudioData"]
I haven't noticed any negative effects by changing this. After successful run of jellyfin, I shut down the container, changed it back to true and started jellyfin up again.
Hope this will help anyone with the same issue out there. I really feared setting it all up again and wasting a time on that.
Created an account just to say thank you!
RE: xml document error after upgrade - rafny2 - 2024-08-28
(2024-07-16, 01:11 PM)wyrtz Wrote: Created an account just to post this.
After fixing the out of disk space issue, jellyfin was producing the errors as described in this thread. Inspired from reading this thread, I was able to recover quite simply however:
-Stopped jellyfin container
-Deleted (empty) migrations.xml file
-Edited system.xml: changed <IsStartupWizardCompleted> from true to false.
-Stared up jellyfin container, all worked as before (no startup wizard or anything)
Note that I am simply listing the steps I took, I cannot fully explain why it works. From looking in the logs, it seems like setting startup wizard to not completed made jellyfin treat this as a fresh install:
Code:[13:02:23] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["CreateNetworkConfiguration", "MigrateMusicBrainzTimeout", "MigrateNetworkConfiguration"]
[13:02:25] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["DisableTranscodingThrottling", "CreateLoggingConfigHeirarchy", "MigrateActivityLogDatabase", "RemoveDuplicateExtras", "MigrateUserDatabase", "MigrateDisplayPreferencesDatabase", "RemoveDownloadImagesInAdvance", "MigrateAuthenticationDatabase", "FixPlaylistOwner", "MigrateRatingLevels", "FixAudioData"]
I haven't noticed any negative effects by changing this. After successful run of jellyfin, I shut down the container, changed it back to true and started jellyfin up again.
Hope this will help anyone with the same issue out there. I really feared setting it all up again and wasting a time on that.
Thank you! This worked perfectly!!
Now I just need to figure out some HLS errors on this post -> https://forum.jellyfin.org/t-a-fatal-error-was-encountered-in-the-hls-stream?pid=34509#pid34509
RE: xml document error after upgrade - trawzified - 2024-10-14
(2024-07-16, 01:11 PM)wyrtz Wrote: Created an account just to post this.
After fixing the out of disk space issue, jellyfin was producing the errors as described in this thread. Inspired from reading this thread, I was able to recover quite simply however:
-Stopped jellyfin container
-Deleted (empty) migrations.xml file
-Edited system.xml: changed <IsStartupWizardCompleted> from true to false.
-Stared up jellyfin container, all worked as before (no startup wizard or anything)
Note that I am simply listing the steps I took, I cannot fully explain why it works. From looking in the logs, it seems like setting startup wizard to not completed made jellyfin treat this as a fresh install:
Code:[13:02:23] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["CreateNetworkConfiguration", "MigrateMusicBrainzTimeout", "MigrateNetworkConfiguration"]
[13:02:25] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["DisableTranscodingThrottling", "CreateLoggingConfigHeirarchy", "MigrateActivityLogDatabase", "RemoveDuplicateExtras", "MigrateUserDatabase", "MigrateDisplayPreferencesDatabase", "RemoveDownloadImagesInAdvance", "MigrateAuthenticationDatabase", "FixPlaylistOwner", "MigrateRatingLevels", "FixAudioData"]
I haven't noticed any negative effects by changing this. After successful run of jellyfin, I shut down the container, changed it back to true and started jellyfin up again.
Hope this will help anyone with the same issue out there. I really feared setting it all up again and wasting a time on that.
Pfew, thanks so much! I don't know what happened exactly but Jellyfin decided to generate 35GB of logs today and filled up my entire disk. After that the migrations xml got corrupted, but this fixed it!
RE: xml document error after upgrade - Ordnael - 2025-01-08
(2024-07-16, 01:11 PM)wyrtz Wrote: Created an account just to post this.
After fixing the out of disk space issue, jellyfin was producing the errors as described in this thread. Inspired from reading this thread, I was able to recover quite simply however:
-Stopped jellyfin container
-Deleted (empty) migrations.xml file
-Edited system.xml: changed <IsStartupWizardCompleted> from true to false.
-Stared up jellyfin container, all worked as before (no startup wizard or anything)
Note that I am simply listing the steps I took, I cannot fully explain why it works. From looking in the logs, it seems like setting startup wizard to not completed made jellyfin treat this as a fresh install:
Code:[13:02:23] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["CreateNetworkConfiguration", "MigrateMusicBrainzTimeout", "MigrateNetworkConfiguration"]
[13:02:25] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["DisableTranscodingThrottling", "CreateLoggingConfigHeirarchy", "MigrateActivityLogDatabase", "RemoveDuplicateExtras", "MigrateUserDatabase", "MigrateDisplayPreferencesDatabase", "RemoveDownloadImagesInAdvance", "MigrateAuthenticationDatabase", "FixPlaylistOwner", "MigrateRatingLevels", "FixAudioData"]
I haven't noticed any negative effects by changing this. After successful run of jellyfin, I shut down the container, changed it back to true and started jellyfin up again.
Hope this will help anyone with the same issue out there. I really feared setting it all up again and wasting a time on that.
I created an account only to reply to this post and say: THANK YOU!
RE: xml document error after upgrade - deekarma - 2025-02-11
(2024-07-16, 01:11 PM)wyrtz Wrote: Created an account just to post this.
After fixing the out of disk space issue, jellyfin was producing the errors as described in this thread. Inspired from reading this thread, I was able to recover quite simply however:
-Stopped jellyfin container
-Deleted (empty) migrations.xml file
-Edited system.xml: changed <IsStartupWizardCompleted> from true to false.
-Stared up jellyfin container, all worked as before (no startup wizard or anything)
Note that I am simply listing the steps I took, I cannot fully explain why it works. From looking in the logs, it seems like setting startup wizard to not completed made jellyfin treat this as a fresh install:
Code:[13:02:23] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["CreateNetworkConfiguration", "MigrateMusicBrainzTimeout", "MigrateNetworkConfiguration"]
[13:02:25] [INF] [1] Jellyfin.Server.Migrations.MigrationRunner: Marking following migrations as applied because this is a fresh install: ["DisableTranscodingThrottling", "CreateLoggingConfigHeirarchy", "MigrateActivityLogDatabase", "RemoveDuplicateExtras", "MigrateUserDatabase", "MigrateDisplayPreferencesDatabase", "RemoveDownloadImagesInAdvance", "MigrateAuthenticationDatabase", "FixPlaylistOwner", "MigrateRatingLevels", "FixAudioData"]
I haven't noticed any negative effects by changing this. After successful run of jellyfin, I shut down the container, changed it back to true and started jellyfin up again.
Hope this will help anyone with the same issue out there. I really feared setting it all up again and wasting a time on that.
You got me out of a mess. Thank you!