Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] keepalived IP used instead of the normal one #163

Closed
sahara101 opened this issue Aug 10, 2024 · 4 comments
Closed

[BUG] keepalived IP used instead of the normal one #163

sahara101 opened this issue Aug 10, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@sahara101
Copy link

Describe the bug
I am trying to add a system with ip .170. All good but after the agent is installed I see the keepalived vip 172

I can add logs if needed but not sure which ones.

Thanks

@SquirrelDeveloper SquirrelDeveloper added the bug Something isn't working label Aug 12, 2024
@SquirrelDeveloper
Copy link
Collaborator

Hi,
What do you mean by keepalive?
The one used by the docker lib? The agent doesnt have one per-se.

@sahara101
Copy link
Author

I have two piholes in HA mode using keepalived. The VIP is 192.168.1.172. The master is 192.168.1.170 and the slave 192.168.1.168. Afte adding the master with ip 192.168.1.170 I see actually the vip 192.168.1.172 in the inventory.

@SquirrelDeveloper
Copy link
Collaborator

Ok, thanks. This is related to #119 , I will add an option to the agent to force a specific IP, as the agent is not getting the right IP in some specific cases

@SquirrelDeveloper
Copy link
Collaborator

@sahara101 You can use the env var OVERRIDE_IP_DETECTION in the .env file of the agent directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants