Hi Markus,
I'm pretty new, too, I struggled with the same error just today.
Here's how I resolved it.
The error message 'Could not find class' sometimes occurs when puppet
doesn't like the contents of the class.
Start with the simplest possible class, and see if puppet finds it.
Something like:
-- snip --
class mydir {
# create /etc/mydir
file { "/etc/mydir":
ensure => directory,
}
}
-- snip --
Paul
On Feb 25, 12:30 pm, Markus Falb <markus.f...@fasel.at> wrote:
> On 25.2.2012 20:11, Mike Knell wrote:
>
> > The first time a host runs Puppet, and every time I change anything in
> > the configs on the server, the agent has to run once and abort for
> > each included class (module, thing..) on the machine I'm trying to
> > configure before it finally just works after 'n' tries and everything
> > works fine.
>
> Could it be the filetimeout?
>
> $ puppet agent --genconfig
> ...
> # The minimum time to wait (in seconds) between checking for updates in
> # configuration files. This timeout determines how quickly Puppet
> checks whether
> # a file (such as manifests or templates) has changed on disk.
> # The default value is '15'.
> # filetimeout = 15
> ...
>
> --
> Kind Regards, Markus Falb
>
> signature.asc
> < 1KViewDownload
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@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.
