Problems bootstrapping

The most common problems with bootstrapping are related to:

Firewall

Make sure port 5308 is open for both incoming and outgoing traffic.

Policy access control list (acl)

By default, the hub is available to clients that reside in the same class B network. If some clients are not part of that network, make sure the IPs are added to the acl in/var/cfengine/masterfiles/def.cf, bundle common def:

      "acl" slist => {
     
                # Assume /16 LAN clients to start with 
                 "$(sys.policy_hub)/16",
                # Add clients' IP addresses (or IP range) here (for
                # example: an acl of 192.168.0.0/16 would allow all
                # clients that have an IP address that starts with 
                # 192.168 to connect to the hub)

cf-serverd is not running on the hub

The CFEngine component cf-serverd takes care of all CFEngine communication. It can take a few minutes after you bootstrapped the hub to itself before this component is started, just wait a bit and retry

Problems bootstrapping

Comments