We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hi,
I use keepalived container in VM ubuntu 14.04, He important use CPU, because a process to inititialize IPVS start loop.
15/2/2016 03:00:46Initializing ipvs 2.6 15/2/2016 03:00:46Keepalived_healthcheckers[15852]: Initializing ipvs 2.6 15/2/2016 03:00:46IPVS: Can't initialize ipvs: Protocol not available 15/2/2016 03:00:46Keepalived_healthcheckers[15852]: IPVS: Can't initialize ipvs: Protocol not available 15/2/2016 03:00:46Healthcheck child process(15852) died: Respawning 15/2/2016 03:00:46Keepalived[9]: Healthcheck child process(15852) died: Respawning 15/2/2016 03:00:46Starting Healthcheck child process, pid=15854 15/2/2016 03:00:46Keepalived[9]: Starting Healthcheck child process, pid=15854 15/2/2016 03:00:46Initializing ipvs 2.6 15/2/2016 03:00:46Keepalived_healthcheckers[15854]: Initializing ipvs 2.6 15/2/2016 03:00:46IPVS: Can't initialize ipvs: Protocol not available 15/2/2016 03:00:46Keepalived_healthcheckers[15854]: IPVS: Can't initialize ipvs: Protocol not available
An idea to resolve it please ?
NB: Virtual IP works well
The text was updated successfully, but these errors were encountered:
Hi, did you enable ip_vs module on your docker host ?
Sorry, something went wrong.
Hi,
I provisioned my virtual machine with ipvsadm package . Problem solved.
ipvsadm
Thank you!
No branches or pull requests
hi,
I use keepalived container in VM ubuntu 14.04, He important use CPU, because a process to inititialize IPVS start loop.
An idea to resolve it please ?
NB: Virtual IP works well
The text was updated successfully, but these errors were encountered: