Does anyone have any suggestions as to why storeconfigs aren't working
for me?
On Aug 28, 1:44 pm, josbal wrote:
> Hey Ohad,
>
> Does my puppet.conf from my puppetmaster help you?
>
> Cheers,
> Josh
>
> On Aug 27, 2:53 pm, josbal wrote:
>
> > Surething...
>
> > [main]
> > # Where Puppet sto
> Are the opensuse repositories basically identical to the SLES repos?
Note the following from the release notes of SLES11:
The puppet tools shipped with SUSE Linux Enterprise Server 11 are a
Technology Preview.
That being said, according to the package list for SLES11 (available
here:
http://
Hello list,
In our company we use puppet to configure our ec2 instances.
we start our servers with fresh instances debian lenny, some small and
some large.
we install puppet like this:
apt-get -y --force-yes install ruby1.8 rubygems1.8
gem install puppet --include-dependencies --version 0.24.8 -
I create this class pmaster in order to restart puppetmaster daemon
after /etc/puppet/puppet.conf file change.
class pmaster {
file { "/etc/puppet/puppet.conf":
ensure => "file";
}
service { "puppetmaster":
2009/8/30 Nigel Kersten :
>
> On Sun, Aug 30, 2009 at 10:30 AM, grandpa wrote:
>>
>> I am running 0.25rc1 from your package. Also running facter built from
>> a clone of your git repo(think it was on github),
>> since there seem to be a bug with versioning concerning 10.6 not fixed
>> in your pack
On Sun, Aug 30, 2009 at 10:30 AM, grandpa wrote:
>
> I am running 0.25rc1 from your package. Also running facter built from
> a clone of your git repo(think it was on github),
> since there seem to be a bug with versioning concerning 10.6 not fixed
> in your package.
Yeah. There's no released ver
I am running 0.25rc1 from your package. Also running facter built from
a clone of your git repo(think it was on github),
since there seem to be a bug with versioning concerning 10.6 not fixed
in your package.
Thanks for providing those packages.
Puppetmaster server is running on Debian 5. Also h
I should also add that you really want to be running 0.25.0rc1 for Snow Leopard.
The package installer is broken in 0.24.8 for SnoLo as Apple started
dereferencing mount points, and we got it fixed in 0.25.x
I can get the service issue fixed pretty quickly for 0.25.x
On Sun, Aug 30, 2009 at 9:1
We need to re-do some of the way the service provider works. Your
solution isn't going to work for all cases.
Apple decided to stop using the plist to store state in, and it's all
in /var now.
Can you bug report this and assign it to me John?
On Sun, Aug 30, 2009 at 7:57 AM, grandpa wrote:
>
I'm no ruby expert... rather I'm a complete newbie, but I found that
commenting out the places
in the launchd provider (in stop and start) where it decides whether
to use the -w switch (so it always
includes that switch) makes the problem (well, MY problem) go away.
I haven't tested this on Leopa
Doing another run reveals a bit more... perhaps I missed pasting that
part previously.
Here we can see what puppet executes. If I do the same from a terminal
I get "nothing found to load".
launchctl unload -w /System/Library/LaunchDaemons/ssh.plist
then
launchctl load /System/Library/LaunchDaemon
The actual problem still seems to be with the provider. Doing a proper
trace/debug/verbose I get this output:
debug: Service[com.openssh.sshd](provider=launchd): Executing
'launchctl load /System/Library/LaunchDaemons/ssh.plist'
/Library/Ruby/Site/1.8/puppet/provider/service/launchd.rb:141:in
`st
And looking through the ruby code for provider launchd I see this:
# start the service. To get to a state of running/enabled, we need to
# conditionally enable at load, then disable by modifying the
plist file
# directly.
def start
job_path, job_plist = plist_from_label(resour
Talking to myself here ;-)... I've noticed in the man pages for
launchctl in Snow Leopard this:
-w Overrides the Disabled key and sets it to false. In previous
versions, this option would modify the configuration file. Now the
state of the Disabled key is stored elsewhere on-disk.
So I gue
Forgot to add that I'm running Snow Leopard...
I've noticed that to start the ssh server from terminal I must do:
launchctl load -w /System/Library/LaunchDaemons/ssh.plist
Notice the -w switch. Without it I just get "nothing found to load"...
I wonder if this is new to Snow Leopard?
/John
On
Anyone out there who've tried updating sshd_config on macs and
restarting / ensure running the ssh server?
I've found that this ALMOST works:
service {
"com.openssh.sshd":
enable => true,
ensure => running;
}
and then notif
16 matches
Mail list logo
