Collector can't be selected for agent

Forum|Forum|7 months ago
February 8, 2026
3 replies
279 views

Hi FSM admins

I have 3 collectors all healthy and working fine as syslog collectors.

However when I try select the collector for Windows/Linux collector agent, only 2 are shown in the list.

What can be the cause?

Best answer by AEK

Hello

TAC support detected an anomaly on the collector record in the DB (probably occurred during initial collector registration) and they provided a solution just by deleting the collector on the supervisor (menu Admin > Setup > Collector) then adding & registering it again.

Secusaurus

Contributor III

Hi @AEK,

Are you using a multi-tenant or enterprise deployment here?

Are these two shown one just "random" or do they have something in common the third one doesn't share? (e.g. different network zones, different EPS limits, different hardware configurations, etc.)

Best,

Christian

NSE8 | Fortinet Advanced MSSP Partner

AEKAuthor

SuperUser

Hi Secusaurus

It is enterprise deployment.

The collectors are VMs that have been deployed exactly in the same manner, and all have https access to the supervisor.

Searched for any difference but didn't find any, except that the problematic collector is on the same network segment as the supervisor, but this should not be a problem because there is no firewall between this col and sup.

AEK

AEKAuthorAnswer

SuperUser

Hello

TAC support detected an anomaly on the collector record in the DB (probably occurred during initial collector registration) and they provided a solution just by deleting the collector on the supervisor (menu Admin > Setup > Collector) then adding & registering it again.

AEK

Sign up

Login with SSO

Login to the community

Login with SSO