Ignition Gateway Logs are being flooded with following message(s)

Ignition
1

Good morning,

I am working with a customer and their gateway logs are being flooded with the following message(s). They are running version 8.1.35.


|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.BasicTagDefinition.shouldBeEnabled(BasicTagDefinition.java:363)|
|INFO   | jvm 1    | 2024/09/05 15:44:53 | |at com.inductiveautomation.ignition.gateway.tags.runtime.nodes.FolderNode.shouldBeEnabled(FolderNode.java:482)|
  1. How do I stop the flooding of messages?
  2. How do I identify and fix the root issue?
  3. Is there a version where the issue is fixed?

Existing topics suggest rebooting the gateway should help but I'd like to be certain that is the case before suggesting that to the customer.

2

It looks like the root logger may be called *.batchoperations, so if you can find that and set the level to OFF it might stop the log spam.

I found a ticket that looks like it might be this and it indicates it's fixed for 8.3 but not in 8.1.x. It seems the root cause is a lack of validation preventing a user from drag and dropping a folder onto itself.

2 Likes
3

I did have the 2 items listed under *.batchoperations turned off but it didn't stop the spam. If I turn the 2 items listed under *.batchoperations off and then restart the gateway should that be sufficient to fix the issue or do I also need to delete any log files?

4

Just restarting the gateway should be enough if this is the same issue. Changes to loggers made in the gateway UI do not persist across restarts, but it shouldn't matter.

5

I will pass on the details to the customer and update this topic later.