Hi all,
I've released a small tool that displays when puppet last ran
successfully on your nodes. Here's a bit more about that:
http://blog.absurd.li/2010/06/07/a_small_tool_for_puppet.html
You can get it here:
http://github.com/kschiess/last_puppetrun
Note that you probably have to ins
So I don't get how you could have lost your pool, as zpool will refuse
to overwrite an existing pool without the "-f". All you would have had
to do was run "zpool import" and you'd been back to normal.
To be perfectly honest with you, I am a bit in the dark about that as
well. I've done the sam
Use "puppetd --disable" the next time to keep your tools from stampeding
over your manual recovery efforts.
I am not sure I understand - I could only boot into failsafe mode at the
time. And the first real boot came up with puppetd running first thing.
I can't think of anything to stop that,
Nat wrote:
has anyone else experienced puppet clients that die when the network goes
down for an extended period of time ?
That happens here as well. We even have a script to monitor last_run
times of all puppet clients to detect this.
It seems that a puppet master not answering for some tim
Hi
as far as I understood was that the zpool information was lost, hence
puppet thought that there was no zpool anymore. I assume that this means
that zpool-tools didn't know about that anymore either, but it might
have been recoverable with manual interaction.
That's what happened. Actually, it
Hi everyone,
Just wanted to tell you a little story. We've been enthusiastic puppet
users since about a year ago here at the Geographic Institute of the
University of Zürich.
But we won't use the zpool type ever again. Its just not worth it.
Here's what happened:
. one of our servers lost
