# Wrapper Logs Filling Up Quickly with "shouldBeEnabled" messages **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [March 16, 2023, 11:38pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199 "2023-03-16T23:38:48Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![rbachman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rbachman/32/43718_2.png) [@rbachman](https://forum.inductiveautomation.com/u/rbachman)\ **Post date:** [March 16, 2023, 11:38pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/1 "2023-03-16T23:38:48Z")
Our wrapper logs are being inundated with messages related to something with the tags that **shouldBeEnabled**. I plan to restart the Gateway to try to fix it when we have a break in production, but does anyone know what might be causing this? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/8/88aa2cb60f504021bd34c577aff5d178e449ecda.png) ---
**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:** [March 17, 2023, 12:39am UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/2 "2023-03-17T00:39:09Z")
There is probably a StackOverflowError at the head of each batch of lines - this looks like a classic recursive function call. What version of Ignition is this? (This is unambiguously an Ignition bug, but it's possible we've already fixed it). ---
**Author:** ![rbachman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rbachman/32/43718_2.png) [@rbachman](https://forum.inductiveautomation.com/u/rbachman)\ **Post date:** [March 17, 2023, 12:41am UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/3 "2023-03-17T00:41:45Z")
We're running 8.1.24. Also, eventually the logs did load on the gateway, and all of them said, "Uncaught exception executing batch context." ---
**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:** [March 17, 2023, 12:44am UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/4 "2023-03-17T00:44:38Z")
I'd send your logs in to support. Like I said, definitely a bug in Ignition, and the nature of it should be clear enough from the logs. There may or may not be a known workaround. ---
**Author:** ![rbachman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rbachman/32/43718_2.png) [@rbachman](https://forum.inductiveautomation.com/u/rbachman)\ **Post date:** [March 17, 2023, 3:46am UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/5 "2023-03-17T03:46:39Z")
I'll try to get the logs for you tomorrow. Just as an FYI, I rebooted the server, and the issue started happening right away again. I then reinstalled 8.1.24 on the server, and it is still happening. However, it is not happening on the backup server, so I'm wondering if there is some issue with the server. Also, we are running 8.1.24 on 7 other gateways without any issues. We run all of our Ignition servers on Ubuntu. ---
**Author:** ![Andy\_Guias](https://avatars.discourse-cdn.com/v4/letter/a/b3f665/32.png) [@Andy\_Guias](https://forum.inductiveautomation.com/u/Andy_Guias)\ **Post date:** [August 4, 2023, 1:17pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/6 "2023-08-04T13:17:22Z")
Have you found what was causing these messages? We are experiencing the exact same issue. ```auto INFO | jvm 1 | 2023/08/04 08:46:55 | E [t.e.batchoperations] [12:46:55]: Uncaught exception executing batch context. INFO | jvm 1 | 2023/08/04 08:46:55 | java.lang.StackOverflowError: null INFO | jvm 1 | 2023/08/04 08:46:55 | at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:362) INFO | jvm 1 | 2023/08/04 08:46:55 | at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482) ``` ---
**Author:** ![rbachman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rbachman/32/43718_2.png) [@rbachman](https://forum.inductiveautomation.com/u/rbachman)\ **Post date:** [August 9, 2023, 8:00pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/7 "2023-08-09T20:00:02Z")
No, I don't think we discovered the root cause, and I'm almost certain the issue stopped on its own at some point. ---
**Author:** ![ahernandez](https://avatars.discourse-cdn.com/v4/letter/a/e68b1a/32.png) [@ahernandez](https://forum.inductiveautomation.com/u/ahernandez)\ **Post date:** [September 28, 2023, 3:04pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/8 "2023-09-28T15:04:23Z")
Did anyone get a fix on this? The message I am getting is the following: Uncaught exception executing batch context. I am currently experiencing this and logs and wrapper logs are filling up so quickly I can't even troubleshoot other problems. I'm currently on version 8.1.17. Should I maybe upgrade? ![WRAPPER LOG faults](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/5/859ffc497ee9035b86afbb77c08871c73dcb6404.png) ---
**Author:** ![rbachman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rbachman/32/43718_2.png) [@rbachman](https://forum.inductiveautomation.com/u/rbachman)\ **Post date:** [September 28, 2023, 8:28pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/9 "2023-09-28T20:28:52Z")
I haven't seen this happen since the last posts, and we are now running 8.1.28. I don't know if the issue is actually resolved in newer versions. ---
**Author:** ![apmalone1983](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@apmalone1983](https://forum.inductiveautomation.com/u/apmalone1983)\ **Post date:** [November 28, 2023, 9:33pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/10 "2023-11-28T21:33:01Z")
I assume this issue isn't resolved I am seeing this same problem on 8.1.32. Is there any word on this matter. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 28, 2023, 9:35pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/11 "2023-11-28T21:35:12Z")
Infinite recursion (in java, not jython) is always a bug worthy of reporting to support. (This forum is not support.) ---
**Author:** ![Michael\_Cramer](https://avatars.discourse-cdn.com/v4/letter/m/e274bd/32.png) [@Michael\_Cramer](https://forum.inductiveautomation.com/u/Michael_Cramer)\ **Post date:** [May 15, 2024, 8:17pm UTC](https://forum.inductiveautomation.com/t/wrapper-logs-filling-up-quickly-with-shouldbeenabled-messages/71199/12 "2024-05-15T20:17:26Z")
Just had this occur with 8.1.33. Same log messages; we restarted the gateway to resolve those issues (this problem used a fair amount of i/o, writing 200-300mb/s), but then the logs were corrupted (system log idb) on gateway restart. Next, while the gateway was shut down, I moved the log file (and journal) to a different folder and then started the gateway. It recreated the log files for me, and the system returned to normal operation with logging. I'll mention that I worked with support to resolve this. Also, that this has been happening more frequently in the last few months, and they're looking for examples of system behavior like this so they can recreate the bug and fix it.