Puppet Trouble Shooting Tips

| Comments

Overview

Below are some tips and tricks for trouble shooting puppet.

Manually Running Puppet Agent

You can manually execute puppet on a remote node and see the output. This needs to be run from the puppet.arin.net server

1
sudo puppet agent --test

Puppet Agent takes a long time to complete

This has happened a few times where executing the puppet agent will take a long period to complete ( The average is 5-10 sec ). To determine what is taking a long time with applying the catalog you can use —summarize to a summary of change and times to complete.

1
sudo puppet agent --test --summarize
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
notice: Finished catalog run in 3.57 seconds
Changes:
 Total: 2
Events:
 Total: 2
 Success: 2
Resources:
 Total: 114
 Out of sync: 2
 Changed: 2
 Skipped: 6
Time:
 Filebucket: 0.00
 Package: 0.00
 Yumrepo: 0.00
 Exec: 0.01
 Group: 0.01
 Ssh authorized key: 0.03
 User: 0.03
 File: 0.23
 Last run: 1334583207
 Service: 2.34
 Config retrieval: 2.90
 Total: 5.56
Version:
 Config: 1334581806
 Puppet: 2.7.12

You can also see the evaluation commands and changes being executed by adding the —evaltrace switch

1
sudo puppet agent --test --summarize --evaltrace

Comments