On 10/01/11 16:00, luke.bigum wrote:
Hi Jonathan,
You shouldn't need to "import" your ntp module as Puppet should auto
load it if the pathing is all correct, which it looks like it is.
OK, good to know.
Remote the 'import "ntp"' line from your site.pp:
I've removed this line.
In site.pp:
import "nodes.pp"
Got that.
In nodes.pp:
node 'espresso.resnet.bris.ac.uk' {
include ntp
}
Got that too.
Unfortunately puppetmaster can't find the ntp class. Running the
puppetmasterd in debug mode, it prints this:
err: Could not find class ntp at /etc/puppet/manifests/nodes.pp:3 on
node espresso.resnet.bris.ac.uk
Line 3 in nodes.pp is the "include ntp" line.
So it still seems as if the modulepath declaration isn't work properly.
Puppet doesn't print any debug messages at startup about bad permissions
etc, and I've verified that the path is typed correctly.
Can I confirm that the modulepath declaration should be in the [main]
section of puppet.conf? I've it in all sections without luck, though.
Thanks for your help,
Jonathan
Then run the evaltrace on your node to see if your module and
resources are there. Like Felix, an import of "nodes" seems is strange
to me - maybe Puppet will implicitly add a .pp extension for files in
the CWD? You should not need to explicitly import your module
manifests, using include and Puppet with a correct modulepath should
find it.
-Luke
--
----------------------------
Jonathan Gazeley
Systems Support Specialist
ResNet | Wireless & VPN Team
IT Services
University of Bristol
----------------------------
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
