After installing PE, you can change some default settings to further configure the orchestrator and pe-orchestration-services.
Configure the orchestrator and pe-orchestration-services
There are several parameters you can add to configure the behavior of the orchestrator and pe-orchestration-services.
Configure PXP agent log file location
Use the PXP agent log file to debug issues with the Puppet orchestrator.
By default the log files are at /var/log/puppetlabs/pxp-agent/pxp-agent.log
(on *nix) or C:/ProgramData/PuppetLabs/pxp-agent/var/log/pxp-agent.log
(on Windows). You can configure these locations with Hiera.
puppet_enterprise::pxp_agent::pxp_logfile: '<PATH TO LOG FILE>'
Correct ARP table overflow
In larger deployments that use MCollective or the PCP broker, you may encounter ARP table overflows and need to adjust some system settings.
Overflows occur when the ARP table—a local cache of IP address to MAC address resolutions—fills and starts evicting old entries. When frequently used entries are evicted, this can lead to an increase of extra network traffic (increasing CPU load on the broker and network latency) to restore them.
A typical log message will resemble the following:
[root@s1 peadmin]# tail -f /var/log/messages
Aug 10 22:42:36 s1 kernel: Neighbour table overflow.
Aug 10 22:42:36 s1 kernel: Neighbour table overflow.
Aug 10 22:42:36 s1 kernel: Neighbour table overflow.
To work around this issue:
# Set max table size
net.ipv6.neigh.default.gc_thresh3=4096
net.ipv4.neigh.default.gc_thresh3=4096
# Start aggressively clearing the table at this threshold
net.ipv6.neigh.default.gc_thresh2=2048
net.ipv4.neigh.default.gc_thresh2=2048
# Don't clear any entries until this threshold
net.ipv6.neigh.default.gc_thresh1=1024
net.ipv4.neigh.default.gc_thresh1=1024