Adam, thanks for the response! With that, I'll mark it as Confirmed.
The symptoms all seem to center around the order that modules are loaded
and perhaps how networking is handled. Perhaps keepalived needs to be
delayed until after all networking. I have to wonder if this still
affects 12.04, sinc
There is clearly more than one reporter (I'm one of them).
I worked around it by compiling from source.
Keepalived IF you are using it is liking to be a HIGHLY critical service
(I am not currently but will again).
Maybe it's still a medium but just to put a counterpoint to your comment
Clint.
-
Setting Importance to Medium. 5 year old bug that has only one reporter,
so the scope of the impact seems fairly limited.
** Changed in: keepalived (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
Yes, this porblem happens right after a reboot and if I try to restart
the service result the same.
I'm obtaining an IP dynamically by VRRP. It has one statically
configured IP and additionally gets second if this computer becomes
master router.
--
You received this bug notification because you
Hi there,
Does this problem only happens right after a reboot? IIRC, this might be
related to having keepalived after networking is started.
it is up to upstart/sysvinit to start the daemon, and then this happens?
Are you obtaining an IP address with DHCP or is it statically configured?
Could y
I have the same problem.
Keepalived v1.1.17 (02/10,2010)
Config:
virtual_server localhost 8443 {
delay_loop 5
protocol TCP
real_server localhost 8443 {
notify_up "logger -p daemon.warn -t Keepalived 'Proxy UP';"
notify_down "logger -p daemon.err -t Keepalived '
** Changed in: keepalived (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/160426
Title:
keepalived using genhash keeps getting "zombied" and
