Ignition Container Keeps Logging "Syntax error Couldn't repair and continue parse" and I don't know why

Ignition
,
1

My team is using ignition in a docker container with a bind volume mount type for the data folder. We did it this way for tracking file changes using git. Today I ran into an issue after merging branches. The ignition instance is infinitely logging the following messages:

ignition  | jvm 1    | 2026/02/19 23:04:33 | Syntax error
ignition  | jvm 1    | 2026/02/19 23:04:33 | Couldn't repair and continue parse

The container starts successfully then it prints:

ignition  | jvm 1    | 2026/02/19 23:04:31 | I [c.i.i.g.o.s.IgnitionOpcUaServer$OpcUaRedundancyListener] [23:04:31.802]: redundancyStateChanged: Role=Independent, Activity level=Active, Project state=Good, History level=Full

and after that it prints the syntax error message over and over again. I cannot find the root cause of the error. So far ignition works just fine without resolving it.

The other errors that print during startup are the following:

frontend-gw  | jvm 1    | 2026/02/19 23:03:45 | E [c.i.i.g.c.m.MigrationLog      ] [23:03:45.126]: Error migrating table 'WSQUEUE_OVERRIDES' 

frontend-gw  | jvm 1    | 2026/02/19 23:03:45 | com.inductiveautomation.ignition.common.resourcecollection.PushConflictException: CREATE illegal, 'ResourceId{resourcePath=ignition/gateway-network-queue-settings, collectionName=core}' already exists.

frontend-gw  | jvm 1    | 2026/02/19 23:03:45 | E [c.i.i.g.c.m.MigrationLog      ] [23:03:45.134]: Error migrating table 'WS_PROXYRULES' 
frontend-gw  | jvm 1    | 2026/02/19 23:03:45 | com.inductiveautomation.ignition.common.resourcecollection.PushConflictException: CREATE illegal, 'ResourceId{resourcePath=ignition/gateway-network-proxy-rules, collectionName=core}' already exists.

frontend-gw  | jvm 1    | 2026/02/19 23:03:45 | E [c.i.i.g.c.m.MigrationLog      ] [23:03:45.139]: Error migrating table 'STARTERSTEPS' 
frontend-gw  | jvm 1    | 2026/02/19 23:03:45 | com.inductiveautomation.ignition.common.resourcecollection.PushConflictException: CREATE illegal, 'ResourceId{resourcePath=ignition/quickstart, collectionName=core}' already exists.
2

Have you looked at the diff of the last commit(s)? Bad merge on some file maybe?

3

I have only done a diff –name-status to do brief overview of the files. I didn’t go one by one because there were a lot of files. It is definitely related to a bad merge on a file. I do not know which one. I reset the branch to before the commit, then tried the clone and merge process on my local machine and the error continued to popup. When merging there are some files were git says there are merge conflicts that need to be resolved, but I don’t see any conflicts marked in the file when looking at the file in VS Code or notepad. I’m wondering if that could be causing the problem.