Wrapper.log error that I can't resolve

Ignition
1

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.

2

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.