# Wrapper.log error that I can't resolve **URL:** \ **Category:** Ignition\ **Created:** [January 10, 2019, 6:37pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-error-that-i-cant-resolve/21793 "2019-01-10T18:37:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![mbufarini](https://avatars.discourse-cdn.com/v4/letter/m/958977/32.png) [@mbufarini](https://forum.inductiveautomation.com/u/mbufarini)\ **Post date:** [January 10, 2019, 6:37pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-error-that-i-cant-resolve/21793/1 "2019-01-10T18:37:42Z")
About a couple of month ago (perhaps after a modification in some of the 6 project that run in the Gateway) I start to see an event like this in the wrapper.log: INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse INFO | jvm 1 | 2019/01/09 16:22:21 | Syntax error INFO | jvm 1 | 2019/01/09 16:22:21 | Couldn’t repair and continue parse It consists of 35 events at the same time that are repeated continuously between 10 seconds. I tried disabling projects, tags, scripts, but without success, the error continues and the strangest thing I noticed is that those events do not appear in the Status page of the Ignition Gateway, in the Diagnosis - Log section. This error causes a memory leak. The memory slowly increase until hit hit the maximum allowed. Then the gateway become very slow and unusable. Someone have any suggestion or some experience with that? Any help to isolate the problem would be very appreciated. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 10, 2019, 6:54pm UTC](https://forum.inductiveautomation.com/t/wrapper-log-error-that-i-cant-resolve/21793/2 "2019-01-10T18:54:10Z")
It’s an error with a modbus or siemens tag configuration. I would recommend getting on contact with support so they can go through your tag structure and find out the culprit.