On Wed, Jan 12, 2011 at 12:41, Thomas Bellman wrote:
> Felix Frank wrote:
>
>> That's why I originally asked for pastes of configs, manifests *and*
>> filesystem listings (not to the list preferably, use pastebin services).
>
> I strongly disagree! Having things on a website instead of in
> the a
Felix Frank wrote:
That's why I originally asked for pastes of configs, manifests *and*
filesystem listings (not to the list preferably, use pastebin services).
I strongly disagree! Having things on a website instead of in
the actual mail I'm reading and possibly responding to sucks.
It's one
On 10/01/11 16:33, Felix Frank wrote:
On 01/10/2011 05:30 PM, Jonathan Gazeley wrote:
On 10/01/11 16:20, Felix Frank wrote:
Hauling out the big guns boils down to (for me):
strace -e trace=file -f puppet master --no-daemonize ... 2>&1 | grep ntp
That should eventually spit a few stat or open
On 01/10/2011 05:30 PM, Jonathan Gazeley wrote:
> On 10/01/11 16:20, Felix Frank wrote:
>> Hauling out the big guns boils down to (for me):
>>
>> strace -e trace=file -f puppet master --no-daemonize ... 2>&1 | grep ntp
>>
>> That should eventually spit a few stat or open attempts that fail, when
>>
On 10/01/11 16:20, Felix Frank wrote:
Hauling out the big guns boils down to (for me):
strace -e trace=file -f puppet master --no-daemonize ... 2>&1 | grep ntp
That should eventually spit a few stat or open attempts that fail, when
the master tries to import the ntp module.
Thank you. Using s
On 01/10/2011 05:11 PM, Jonathan Gazeley wrote:
> 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 "
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.p
> Hmm, no luck using ntp::ntp instead of ntp. The problem seems to be in
> importing rather than including. I tried using ntp, ntp::ntp, and the
> full path /etc/puppet/modules/ntp/manifests/init.pp.
>
> It always fails with:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERV
On 10/01/11 13:59, Felix Frank wrote:
node 'espresso.resnet.bris.ac.uk' {
include ntp
}
To get anything going, try to rename class ntp to ntp::ntp and include
it as that. You can strip down to more straight-forward naming once that
works.
Hmm, no luck using ntp::ntp instead of ntp. The pr
> node 'espresso.resnet.bris.ac.uk' {
>include ntp
> }
To get anything going, try to rename class ntp to ntp::ntp and include
it as that. You can strip down to more straight-forward naming once that
works.
BTW, I don't see how your 'import "nodes"' ever worked. But apparently
it does.
--
Yo
On 10/01/11 13:34, Felix Frank wrote:
To reiterate, my 'ntp' class is defined in
/etc/puppet/modules/ntp/manifests/init.pp and I have defined modulepath
in my puppet.conf. The ntp module is imported in site.pp and included in
nodes.pp.
Are the permissions adequate for your puppetmaster process?
> To reiterate, my 'ntp' class is defined in
> /etc/puppet/modules/ntp/manifests/init.pp and I have defined modulepath
> in my puppet.conf. The ntp module is imported in site.pp and included in
> nodes.pp.
Are the permissions adequate for your puppetmaster process?
> So it looks like my puppetmas
On 07/01/11 14:54, luke.bigum wrote:
I created the tree /etc/puppet/modules/ntp/manifests/ and created an
init.pp with this content:
class ntp {
package { "ntp": ensure => installed }
service { "ntpd": ensure => stopped }
}
Hi Jonathan,
How do you know the client isn't
> I created the tree /etc/puppet/modules/ntp/manifests/ and created an
> init.pp with this content:
>
> class ntp {
> package { "ntp": ensure => installed }
> service { "ntpd": ensure => stopped }
>
> }
Hi Jonathan,
How do you know the client isn't doing what you told it if ther
14 matches
Mail list logo