# [OmniOS-discuss] Keepalived in an LX branded zone

Serge Fonville serge.fonville at gmail.com
Sun Dec 3 18:05:03 UTC 2017

- Next message: [OmniOS-discuss] Keepalived in an LX branded zone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hi,

    I am currently trying to setup keepalived in an LX branded zone.

    Since I get a lot of errors that might be related to the fact it is an LX
    branded zone, I was wondering if someone would be so kind to shed their
    light on it.

    Especially since I never setup keepalived before, I am unsure if these
    errors are caused by the fact it is an LX branded zone, of just
    misconfiguration of keepalived.

    # Inside the zone
    keepalived.conf

    > global_defs {    router_id haproxy01
    >     vrrp_version 3
    > }
    >
    > vrrp_script check_haproxy {
    >     script "/etc/keepalived/check_haproxy.sh"
    >     interval 0.05
    >     fall 2
    >     rise 2
    > }
    >
    > vrrp_instance haproxy_instance {
    >     state MASTER
    >     interface haproxy01vnic0
    >     virtual_router_id 25
    >     priority 150
    >     advert_int 0.05
    >     virtual_ipaddress {
    >         192.168.1.25/2 label haproxy01vnic0:0
    >     }
    >     track_script {
    >         check_haproxy
    >     }
    > }
    >
    >
    keepalived -f /etc/keepalived/keepalived.conf -l -n

    > Starting Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2
    > Unable to resolve default script username 'keepalived_script' - ignoring
    > Opening file '/etc/keepalived/keepalived.conf'.
    > Starting Healthcheck child process, pid=13481
    > Initializing ipvs
    > Starting VRRP child process, pid=13482
    > Registering Kernel netlink reflector
    > Registering Kernel netlink command channel
    > Error while registering gratuitous ARP shared channel
    > Opening file '/etc/keepalived/keepalived.conf'.
    > IPVS: Can't initialize ipvs: No such file or directory
    > Keepalived_vrrp exited due to segmentation fault (SIGSEGV).
    > Please report a bug at https://github.com/acassen/keepalived/issues
    > and include this log from when keepalived started, what happened
    > immediately before the crash, and your configuration file.
    >

    /etc/keepalived/check_haproxy.sh

    > #!/bin/bash
    > kill -0 $(cat /run/haproxy.pid) && echo 'OK' && exit 0 || echo 'NOK' && exit 1
    >
    >
    # Inside the global zone
    cat /etc/zones/haproxy01.xml

    > <?xml version="1.0"?>
    > <!--
    >     DO NOT EDIT THIS FILE.  Use zonecfg(1M) instead.
    > -->
    > <!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN"
    > "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">
    > <zone name="haproxy01" zonepath="/export/zones/haproxy01" autoboot="true"
    > brand="lx" ip-type="exclusive" debugid="20">
    >   <network physical="haproxy01vnic0">
    >     <net-attr name="gateway" value="192.168.1.254"/>
    >     <net-attr name="ips" value="192.168.1.22/24"/>
    >     <net-attr name="primary" value="true"/>
    >   </network>
    >   <attr name="dns-domain" type="string" value="sergefonville.nl"/>
    >   <attr name="resolvers" type="string" value="192.168.1.20"/>
    >   <attr name="kernel-version" type="string" value="3.10.0"/>
    >   <network physical="haproxy01vnic1">
    >     <net-attr name="ips" value="10.0.0.1/24"/>
    >   </network>
    > </zone>
    >

    uname -v
    omnios-r151022-f9693432c2

    Any feedback or input is greatly appreciated!

    Kind regards/met vriendelijke groet,

    Serge Fonville

    http://www.sergefonville.nl
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20171203/19a99615/attachment.html>

- Next message: [OmniOS-discuss] Keepalived in an LX branded zone
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the OmniOS-discuss mailing list