Hi guys,
I changed the ip of the supervisor by entering configFSM.sh and it changed successfully. I entered the register command to register the collector to the new sup ip, but I get an error like this. Does anyone know the reason?
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi,
If your Supervisor node is also a ClickHouse node then you also need to update the IP in the ClickHouse config files as per the documentation below
If your Supervisor node is the data upload destination for the collectors then you'll need to update the IP Admin > Settings > Cluster Config > Event Upload Workers
If neither of these fixes the problem then please open a FortiCare ticket.
Thanks
First of all, thanks for your feedback and information sharing. In my test environment, I added keeper and data, query as supervisor. I did the first step, keeper node, but in step 2, config.d directory is empty. I need to do the other steps. I kindly ask for your support.
In Addtional, When I tested the clickhouse, got below error.
I think I overcame the clickhouse test problem, but the collector is still not collecting logs. I would appreciate comments from anyone who has an idea about this issue.
Hi Adem,
I tested the process outlined in the documentation and it works OK for me. Unfortunately I can't give you any more system specific troubleshooting advice here. You can open a FortiCare ticket if your system is under support.
Thanks.
hi @BenBrit
I don't get an error on the clickhouse side anymore, my current problem is that the collector stops the log flow as soon as I change the supervisor ip. "Last Receiver" shows that moment.
If you have access to the collector
You could try to re-register the collector with the command ...
phProvisionCollector --update
(Note the word update here .. rather than add)
I tried this process as you said and then we expect it to reboot itself, but the reboot does not happen.
Continuing to provision the Collector
This collector is registered successfully. Waiting for reboot...
In additional, Is it enough to change the ip of the components alone for the change or should the hostname also change?
Welcome to your new Fortinet Community!
You'll find your previous forum posts under "Forums"
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.