[BUG] There is an error in XML document (0, 0)

[alx-xlx]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I am getting this weird error in the jellyfin and its on an infinite loop

System.InvalidOperationException: There is an error in XML document (0, 0).
 ---> System.Xml.XmlException: Root element is missing.

full log is below

Expected Behavior

I am getting the below logs and jellyfin has stopped working.

Everything was working fine two days ago. I think maybe the power went down when the docker container for jellyfin was starting thats the best possible guess I can make.

Steps To Reproduce

running the following causes the error
docker compose up -d

Environment

- OS: RaspberryOS
- How docker service was installed: `curl -sSL https://get.docker.com | sh`

CPU architecture

arm64

Docker creation

---
services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=1000
      # - JELLYFIN_PublishedServerUrl=192.168.0.5 #optional
    volumes:
      - ./jellyfin:/config
      - ./Music:/data/music
    ports:
      - 7601:8096
      - 7602:8920 #optional
      - 7603:7359/udp #optional
      - 7604:1900/udp #optional
    # restart: unless-stopped

Container logs

[23:40:30] [INF] [1] Main: Jellyfin version: 10.10.7
[23:40:30] [INF] [1] Main: Environment Variables: ["[JELLYFIN_DATA_DIR, /config/data]", "[JELLYFIN_CONFIG_DIR, /config]", "[JELLYFIN_CACHE_DIR, /config/cache]", "[JELLYFIN_LOG_DIR, /config/log]", "[JELLYFIN_WEB_DIR, /usr/share/jellyfin/web]"]
[23:40:30] [INF] [1] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll", "--ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg"]
[23:40:30] [INF] [1] Main: Operating system: Ubuntu 24.04.2 LTS
[23:40:30] [INF] [1] Main: Architecture: Arm64
[23:40:30] [INF] [1] Main: 64-Bit Process: True
[23:40:30] [INF] [1] Main: User Interactive: True
[23:40:30] [INF] [1] Main: Processor count: 4
[23:40:30] [INF] [1] Main: Program data path: /config/data
[23:40:30] [INF] [1] Main: Log directory path: /config/log
[23:40:30] [INF] [1] Main: Config directory path: /config
[23:40:30] [INF] [1] Main: Cache path: /config/cache
[23:40:30] [INF] [1] Main: Temp directory path: /tmp/jellyfin
[23:40:30] [INF] [1] Main: Web resources path: /usr/share/jellyfin/web
[23:40:30] [INF] [1] Main: Application directory: /usr/lib/jellyfin/bin/
[23:40:30] [FTL] [1] Main: Unhandled Exception
System.InvalidOperationException: There is an error in XML document (0, 0).
 ---> System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlReader.MoveToContent()
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderMigrationOptions.Read4_MigrationOptions()
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader)
   at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromStream(Type type, Stream stream)
   at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromFile(Type type, String file)
   at Jellyfin.Server.Migrations.MigrationRunner.RunPreStartup(ServerApplicationPaths appPaths, ILoggerFactory loggerFactory)
   at Jellyfin.Server.Program.StartApp(StartupOptions options)
   at Jellyfin.Server.Program.<Main>(String[] args)
Unhandled exception. System.InvalidOperationException: There is an error in XML document (0, 0).
 ---> System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlReader.MoveToContent()
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderMigrationOptions.Read4_MigrationOptions()
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader)
   at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromStream(Type type, Stream stream)
   at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromFile(Type type, String file)
   at Jellyfin.Server.Migrations.MigrationRunner.RunPreStartup(ServerApplicationPaths appPaths, ILoggerFactory loggerFactory)
   at Jellyfin.Server.Program.StartApp(StartupOptions options)
   at Jellyfin.Server.Program.<Main>(String[] args)

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

Usually happens when the file gets corrupted. You'll need to restore it from a backup.

[alx-xlx]

oh boy, I have no backup :(
I think its time for a proper backup strategy I gues

[j0nnymoe]

You might get away with deleting that specific file and letting it regenerate. Think it's the configuration.xml

[alx-xlx]

I have these xml files as shown below
migrations.xml is empty, rest of them have few data

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.