# Ignition Container Keeps Logging "Syntax error Couldn't repair and continue parse" and I don't know why **URL:** \ **Category:** Ignition\ **Tags:** docker, ignition83\ **Created:** [February 19, 2026, 11:32pm UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082 "2026-02-19T23:32:30Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![derek.delizo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/derek.delizo/32/84136_2.png) [@derek.delizo](https://forum.inductiveautomation.com/u/derek.delizo)\ **Post date:** [February 19, 2026, 11:32pm UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082/1 "2026-02-19T23:32:30Z")
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: ```python 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: ```python 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: ```bash 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. ``` ```bash 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. ``` ```bash 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. ``` ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 19, 2026, 11:37pm UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082/2 "2026-02-19T23:37:57Z")
Have you looked at the diff of the last commit(s)? Bad merge on some file maybe? ---
**Author:** ![derek.delizo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/derek.delizo/32/84136_2.png) [@derek.delizo](https://forum.inductiveautomation.com/u/derek.delizo)\ **Post date:** [February 20, 2026, 6:40pm UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082/3 "2026-02-20T18:40:56Z")
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. ---
**Author:** ![strinidad](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/strinidad/32/10275_2.png) [@strinidad](https://forum.inductiveautomation.com/u/strinidad)\ **Post date:** [April 21, 2026, 8:40am UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082/4 "2026-04-21T08:40:23Z")
Hello, I have the same problem, any solution ? ---
**Author:** ![derek.delizo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/derek.delizo/32/84136_2.png) [@derek.delizo](https://forum.inductiveautomation.com/u/derek.delizo)\ **Post date:** [May 7, 2026, 2:11pm UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082/5 "2026-05-07T14:11:46Z")
Have not found a solution yet. If i do find one, i will record it here ---
**Author:** ![jay\_collosi](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@jay\_collosi](https://forum.inductiveautomation.com/u/jay_collosi)\ **Post date:** [July 16, 2026, 3:48pm UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082/6 "2026-07-16T15:48:24Z")
Hi Derke, I'm having the same issue, any finding on your error? ---
**Author:** ![derek.delizo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/derek.delizo/32/84136_2.png) [@derek.delizo](https://forum.inductiveautomation.com/u/derek.delizo)\ **Post date:** [July 17, 2026, 1:35pm UTC](https://forum.inductiveautomation.com/t/ignition-container-keeps-logging-syntax-error-couldnt-repair-and-continue-parse-and-i-dont-know-why/114082/7 "2026-07-17T13:35:24Z")
The error isn't popping up anymore for me. Didn't find a direct solution. I believe it was related to merge tags in the json that weren't detected by git because they were nested. I would recommend using vscode to search for \>\>\>\>\> or \<\<\<\<\< that helped find some of the files. It will also catch some of the jython files though. Another thing we had to resolve were linux permissions on the bind-mounted files.