flowcoll exits with "license key contains invalid Claims" on customer system, but works in my lab

ElastiFlow Community
1

Hi all,
I’m facing an issue with flowcoll on a customer system that I can’t reproduce in my own lab environment.

Here’s what I did:

  • Installed flowcoll on my own Ubuntu VM (version 7.7.2).

  • Created a minimal /etc/elastiflow/flowcoll.yml with EF_ACCOUNT_ID, EF_FLOW_LICENSE_KEY, and EF_LICENSE_ACCEPTED.

  • Started the service → everything works fine, the collector runs and doesn’t exit.

On the customer’s system (version 7.5.0), using the same YAML content (account ID and license key are correct), the service fails to start and logs this:

{"level":"fatal","logger":"flowcoll","caller":"flowcoll/main.go:81","msg":"exiting because of a license error","code":"license/error","reason":"license key contains invalid Claims"}

It looks like the YAML is being read correctly, because the error only happens after the license check.

Has anyone seen this behavior before?
Could it be related to the collector version (7.5.0 vs 7.7.2), or something in the way the service is configured (systemd, permissions)?
What would you recommend checking next?

Thanks!

2

Not sure why I’m just now seeing this post.

The licensing changed in version 7.6.0. You likely need to change EF_FLOW_LICENSE_KEY to EF_LICENSE_KEY. See the changelog: