Flow Collector Service Issues

Problem

The flowcoll service is not running or is reporting errors after configuration changes.

Solution

Check the service logs.

1. Connect to the Apstra Flow server via SSH.

2. View the Flow collector logs.

Review the log output for error messages. Common issues include misconfigured SNMP settings (mismatched community strings), network connectivity problems between the Flow server and devices, or incorrect sFlow port configurations. Correct the issue and restart the service using sudo systemctl restart flowcoll.

Follow the table below to identify the likely cause and their solution.

Symptom	Likely Cause	Resolution
flowcoll service shows failed or inactive status.	A syntax error in flowcoll.yml, or the service was not restarted after configuration changes.	Verify the YAML syntax in /etc/juniper/flowcoll.yml — YAML is indentation-sensitive and comments must start with # at the correct indent level. Restart the service: sudo systemctl restart flowcoll. Review logs for startup errors: sudo journalctl -u flowcoll -n 100
flowcoll service has started but SNMP enrichment is not working.	The enrichment settings were uncommented incorrectly, or the service was restarted before the file was saved.	Open /etc/juniper/flowcoll.yml and confirm both EF_PROCESSOR_ENRICH_NETIF_SNMP_COMMUNITIES and EF_PROCESSOR_ENRICH_NETIF_SNMP_ENABLE: "true" are uncommented and correctly formatted. Save the file and restart the service.