Skip to main content
Version: Next

Troubleshooting EDFN is Unavailable

This guide provides troubleshooting steps for resolving the "NFO External Data Feeder EDFN_ID is unavailable" error within the web interface.

Identifying the Issue​

The EDFN (External Data Feeder) is considered unavailable if the following symptoms occur:

  • The web interface displays the error message: NFO External Data Feeder EDFN_ID is unavailable, please restart it or try again in 5 minutes.
  • The EDFN page shows no EDFNs listed.
  • The version listed on the EDFN page is outdated.

Common Causes​

Several factors can cause an EDFN to become unavailable:

  • Reconnection Delay: The NFO controller (Tomcat) was recently restarted, and the EDFN has not yet reconnected. Establishing a new connection typically takes between 1 and 5 minutes.
  • Service Status: The EDFN service was never started.
  • Truststore Mismatch: The Tomcat certificate was updated but not imported into the EDFN truststore.
  • Client Certificate Issues: The EDFN TLS client certificate was changed but not imported into the Tomcat truststore.

Diagnostic Actions​

Follow these steps to check the status of the EDFN and its processes.

  • Check Service and Process Status
    • Verify Service Activity: For Linux, run systemctl status nfi_updd.service.
    • Start Inactive Service: If the service is inactive, start it using systemctl start nfi_updd.service.
    • Verify Running Processes: Run ps aux | grep nfi-updater. You should see two jsvc.exec processes.
    • Restart if Missing: If no processes are running, restart the service using systemctl restart nfi_updd.
  • Log File Analysis
    To view the most recent activity, check the end of the EDFN log file:
    tail /opt/nfi-updater/logs/updater.log

Troubleshooting Log Scenarios​

Successful Startup

If the EDFN has started correctly, the logs will show messages indicating the WebSocket is open:

2026-01-01 12:00:00,000 INFO [ConnectionService] WebSocket opened
2026-01-01 12:00:00,000 DEBUG [ConnectionService] Sending agent statuses: 0

2026-01-01 12:00:00,100 INFO [UpdaterService] Server status: STOPPED

2026-01-01 12:00:00,101 INFO [UpdaterService] Keep Alive started

SSL Handshake Error

  • Error Message: javax.net.ssl.SSLHandshakeException: No trusted certificate found.
  • Cause: This indicates a mismatch between the Tomcat TLS certificate and the certificate stored in the EDFN truststore.
  • Resolution:
    • Remove or back up the truststore file:
      rm /opt/nfi-updater/conf/.updater_truststore.
    • Restart the EDFN service: systemctl restart nfi_updd.service.
    • Verify the fix by checking the latest logs or selecting "Run now" for any agent in the web interface.

Broken Pipe Error

  • Error Message: java.net.SocketException: Broken pipe.
  • Cause: This usually indicates Tomcat does not trust the EDFN client certificate.
  • Resolution: Follow the EDFN Authentication Configuration instructions