Comment 3 for bug 1800159

Hi Thorsten,

I tried installing keepalived on a fresh xenial VM, and all seems to be working:

karl@tp-work:~$ uvt-kvm create x release=xenial arch=amd64 label=daily
karl@tp-work:~$ uvt-kvm wait x
karl@tp-work:~$ uvt-kvm ssh x
ubuntu@x:~$ sudo apt update && sudo apt dist-upgrade -y && sudo apt install -y keepalived
ubuntu@x:~$ echo "global_defs {

   notification_email {
       <email address hidden>
   }
   notification_email_from <email address hidden>
   smtp_server 127.0.0.1
   smtp_connect_timeout 60
}" | sudo tee /etc/keepalived/keepalived.conf >/dev/null
ubuntu@x:~$ sudo service keepalived start
ubuntu@x:~$ sudo service keepalived status
● keepalived.service - Keepalive Daemon (LVS and VRRP)
   Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-11-14 11:35:56 UTC; 18s ago
  Process: 8850 ExecStart=/usr/sbin/keepalived $DAEMON_ARGS (code=exited, status=0/SUCCESS)
 Main PID: 8854 (keepalived)
    Tasks: 3
   Memory: 1.7M
      CPU: 11ms
   CGroup: /system.slice/keepalived.service
           ├─8854 /usr/sbin/keepalived
           ├─8855 /usr/sbin/keepalived
           └─8856 /usr/sbin/keepalived

Nov 14 11:35:56 x Keepalived_vrrp[8856]: Registering gratuitous ARP shared channel
Nov 14 11:35:56 x Keepalived_vrrp[8856]: Unable to load ipset library
Nov 14 11:35:56 x Keepalived_vrrp[8856]: Unable to initialise ipsets
Nov 14 11:35:56 x Keepalived_vrrp[8856]: Opening file '/etc/keepalived/keepalived.conf'.
Nov 14 11:35:56 x Keepalived_vrrp[8856]: Using LinkWatch kernel netlink reflector...
Nov 14 11:35:56 x Keepalived_healthcheckers[8855]: Initializing ipvs
Nov 14 11:35:56 x Keepalived_healthcheckers[8855]: Registering Kernel netlink reflector
Nov 14 11:35:56 x Keepalived_healthcheckers[8855]: Registering Kernel netlink command channel
Nov 14 11:35:56 x Keepalived_healthcheckers[8855]: Opening file '/etc/keepalived/keepalived.conf'.
Nov 14 11:35:56 x Keepalived_healthcheckers[8855]: Using LinkWatch kernel netlink reflector...

Are you running it in a container? If so, Patrick's comments will apply.