| NFO Updater: Java heap space too small | java.lang.OutOfMemoryError | Edit -Xmx param in NFI Updater environment: bin/daemon.sh or overwrite JAVA_OPTS="-Xms128m -Xmx3g" in the bin/setenv.sh file. |
| Java call stack failure (for ex. WL not loaded) | java.lang.StackOverflowError | Send logs to support |
| NFO Updater not started | ERROR [UpdaterContext] | See message description, check NFO updater configuration file: conf/updater.properties or maybe NFI Controller is unavailable, check firewall |
| NFO Updater not started or started incorrectly due to websocket can’t be opened or NFO Controller rejects Updater | ERROR [ConnectionService] | See message description, check updater configuration (conf/updater.properties), check NFO Controller status logs (GUI) or nf2sl.log, check firewall, check that tomcat certificate is in the ${nfi_upd}/cont/.updater_truststore and updater’s certificate is in the ${nfi_home}tomcat/conf/.truststore |
| Connection between NFO Controller and NFO Updater is lost due to Controller becomes unavailable | WARN [ConnectionService] Controller unavailable | Check NFO Controller status logs or nf2sl.log, restart tomcat and updater if required |
| NFO Updater Agent works incorrectly (WL not loaded) | WARN [AgentTask] | Check error messages on GUI (Status page), check Agent input data format |
| Connection between NFO Controller and NFO Updater is lost and can’t be restored | WARN [UpdaterService] Controller | Check NFI Controller status, nf2sl.log and firewall |
| Updater or Agents configuration failed; some agents can work incorrectly. | [ERROR] | See message details, reconfigure agent |
| Agent execution failed, proxy connection failed and etc. | [WARNING] | See message details, check agent configuration, URL availability, check proxy settings, firewall configuration |