Charlie Schluting | 1 Jan 02:32 2007
Picon

Re: puppetd.pid and SMF woes

On 12/30/06, Matthew Palmer <mpalmer <at> hezmatt.org> wrote:
> According to #299, actually.  Whoops.

Awesome, thanks :)

 -Charlie
Matthew Palmer | 1 Jan 06:45 2007

Re: puppetd.pid and SMF woes

On Sun, Dec 31, 2006 at 05:32:20PM -0800, Charlie Schluting wrote:
> On 12/30/06, Matthew Palmer <mpalmer <at> hezmatt.org> wrote:
> > According to #299, actually.  Whoops.
> 
> Awesome, thanks :)

And if you follow puppet-commits, you will notice that I've gone through and
fixed up all the PID file handling code, so they should all work as $DEITY
intended.  It'd be handy if you could test it all thoroughly, to make sure
there's no unpleasantness hiding behind the scenes.

- Matt

--

-- 
when SuSE are doing better than you at publishing the tools they use, it's a
hint that maybe you suck.
		-- Andrew Suffield, debian-devel
Luke Kanies | 1 Jan 08:03 2007

Re: puppetd.pid and SMF woes

On Dec 31, 2006, at 11:45 PM, Matthew Palmer wrote:
>
> And if you follow puppet-commits, you will notice that I've gone  
> through and
> fixed up all the PID file handling code, so they should all work as  
> $DEITY
> intended.  It'd be handy if you could test it all thoroughly, to  
> make sure
> there's no unpleasantness hiding behind the scenes.

And I'm very happy you've got that done.

I think Puppet is almost ready for the next release, so it should be  
this week.

  --
  As a general rule, don't solve puzzles that open portals to Hell.
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com
John Dubery | 1 Jan 18:36 2007
Picon
Picon

File configuration difficulty

Hi,

I've been using puppet to manage a small Linux network fairly successfully
for a while now - thanks.

I've hit a spot of bother in managing some files, though.

There are a number of folders in /usr/local that I want to manage efficiently
using puppet - for example /usr/local/share/templates. I want to copy the
contents of a number of source folders on the puppet fileserver into that
folder (with the ability to omit some source folders on some PCs).

The simplest way of specifying this would seem to be ...
===================
file { "/usr/local/share/pixmaps":
   source => "puppet://server/puppetfiles/FindFilesEdit/usr-local-share-pixmaps",
   group => root,
   mode => 664,
   owner => root,
   purge => false,
   recurse => true
}
file { "/usr/local/share/pixmaps":
   source => "puppet://server/puppetfiles/FontBrowse/usr-local-share-pixmaps",
   group => root,
   mode => 664,
   owner => root,
   purge => false,
   recurse => true
}
(Continue reading)

John Dubery | 1 Jan 18:39 2007
Picon
Picon

suggestion - Password replication

Hi,

I would find it very useful if puppet were able to replicate passwords for
specified users from a master PC (the puppetmaster would do me fine, though
I suspect this may not suit everyone).

That would make changing passwords on my small Linux network a little easier.

cheers

John Dubery
Luke Kanies | 2 Jan 07:28 2007

Re: suggestion - Password replication

On Jan 1, 2007, at 11:39 AM, John Dubery wrote:

> Hi,
>
> I would find it very useful if puppet were able to replicate  
> passwords for
> specified users from a master PC (the puppetmaster would do me  
> fine, though
> I suspect this may not suit everyone).
>
> That would make changing passwords on my small Linux network a  
> little easier.

If that's not already an enhancement request, then please open it as  
one, but it's actually surprisingly complicated for many cases  
because many platforms do not provide the ability to set the password  
using any commands -- instead you have to edit /etc/passwd directly.

It's not something I'm likely to implement in the near future,  
although as always patches are always welcomed (and, of course, I'm  
always looking for custom development work).

  --
  Today I dialed a wrong number...The other person said, "Hello?" and
  I said, "Hello, could I speak to Joey?"...
  They said, "Uh...I don't think so...he's only 2 months old."
  I said, "I'll wait."  -- Steven Wright
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com
(Continue reading)

Luke Kanies | 2 Jan 08:40 2007

Re: File configuration difficulty


On Jan 1, 2007, at 11:36 AM, John Dubery wrote:

> Hi,
>
> I've been using puppet to manage a small Linux network fairly  
> successfully
> for a while now - thanks.
>
> I've hit a spot of bother in managing some files, though.
>
> There are a number of folders in /usr/local that I want to manage  
> efficiently
> using puppet - for example /usr/local/share/templates. I want to  
> copy the
> contents of a number of source folders on the puppet fileserver  
> into that
> folder (with the ability to omit some source folders on some PCs).
>
> The simplest way of specifying this would seem to be ...
[snip]
> .... however this failed because it is not possible to manage the  
> same folder
> from multiple places.

Each directory contains files that you want copied directly into the  
directory, right?  That is, you're not copying things into dir/A, dir/ 
B, etc.?

Yeah, currently that's disappointingly difficult, although I can  
(Continue reading)

Thijs Oppermann | 3 Jan 03:37 2007
Picon

error "Stack level too deep" on 'exec[ "perl Makefile.PL" ] ?

Hi,

I'm testing puppet from the subversion trunk. I have a rather
hacked-together system to install a CRM into one of my nodes, which
worked (more or less) with version 0.19.3. When I tried to do a puppet
run on a completely clean node it seemed to stall on the 'compilation'
part (I do an exec of 'perl Makefile.PL' in the appropriate dir). When
I broke it off, the debug showed the following:

stack level too deep
err: /base/enam/eserver/perlinstall[everything]/Exec[makefile-everything]/returns:
change from notrun to 0 failed: stack level too deep

And then a number of failed steps due to unresolved dependencies. Is
this an error message from puppet or is the "stack level too deep"
thing originating from something else?

Thijs
Luke Kanies | 3 Jan 07:16 2007

Re: error "Stack level too deep" on 'exec[ "perl Makefile.PL" ] ?

On Jan 2, 2007, at 8:37 PM, Thijs Oppermann wrote:

> Hi,
>
> I'm testing puppet from the subversion trunk. I have a rather
> hacked-together system to install a CRM into one of my nodes, which
> worked (more or less) with version 0.19.3. When I tried to do a puppet
> run on a completely clean node it seemed to stall on the 'compilation'
> part (I do an exec of 'perl Makefile.PL' in the appropriate dir). When
> I broke it off, the debug showed the following:
>
> stack level too deep
> err: /base/enam/eserver/perlinstall[everything]/Exec[makefile- 
> everything]/returns:
> change from notrun to 0 failed: stack level too deep
>
> And then a number of failed steps due to unresolved dependencies. Is
> this an error message from puppet or is the "stack level too deep"
> thing originating from something else?

'stack level too deep' is a ruby error.  What is the exact code that  
caused this?

  --
  One of the keys to happiness is a bad memory.   -- Rita Mae Brown
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com
Thijs Oppermann | 3 Jan 10:09 2007
Picon

Re: error "Stack level too deep" on 'exec[ "perl Makefile.PL" ] ?

OK, after some more testing I can say that this error does not occur
with 0.19.3. Same procedure (clean node, first run: 0.19.3 finishes
with all OK, latest svn checkout (yesterday) does not).

The code where it happens:

* a node calls a define with the following:

    perlinstall { "everything":
        ploverride      => "everything",
        require         => wgetfile[ "everything.tar.gz" ]
    }

* the define downloads a tar.gz file, extracts it, substitutes a
custom Makefile.PL into the extract dir and tries to do a 'perl
Makefile.PL', which seems to hang. On a ctrl-c I get the "stack level
too deep" error. The code where it hangs looks like this (nothing
fancy):

    exec { "makefile-$name":
        command => "cd $( ls -A -d $name*/ ) && perl Makefile.PL",
        path    => "/usr/bin:/bin",
        cwd     => $dest,
        require => [ package[ "perl" ], exec[ "untar-$name" ] ]
    }

It's probably a bit of a hack, but I'm trying this
off-the-cuff-like... ;) And in my defense it did work in 0.19.3. ;)

Thijs
(Continue reading)


Gmane