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 protected]
   }
   notification_email_from [email protected]
   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.


** Changed in: keepalived (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1800159

Title:
  keepalived ip_vs

Status in keepalived package in Ubuntu:
  Incomplete

Bug description:
  1) 
  Description:  Ubuntu 16.04.5 LTS
  Release:      16.04
  2) keepalived:
    Installed: 1:1.2.24-1ubuntu0.16.04.1
    Candidate: 1:1.2.24-1ubuntu0.16.04.1
    Version table:
   *** 1:1.2.24-1ubuntu0.16.04.1 500
          500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com 
xenial-updates/main amd64 Packages
          100 /var/lib/dpkg/status

  3) not loading the kernel module
  systemctl start keepalived.service
  Keepalived_healthcheckers[1680]: IPVS: Protocol not available
  Keepalived_healthcheckers[1680]: message repeated 8 times: [ IPVS: Protocol 
not available]
  ...

  4) loading the module manually 
  systemctl stop keepalived.service
  modprobe ip_vs
  kernel: [  445.363609] IPVS: ipvs loaded.
  systemctl start keepalived.service
  Keepalived_healthcheckers[5533]: Initializing ipvs
  kernel: [  600.828683] IPVS: [wlc] scheduler registered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1800159/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

Reply via email to