Re: [Puppet Users] puppet post install launchd osx
Hi Moses,
I was able to successfully uninstall the previous versions of gem installed
'puppet'.
i did reinstall with dmg but and still having puppetd exit with a code of 1.
what am i doing wrong?
here is my updated plist and manifest to start launchctl
http://pastebin.com/CX56cucf
http://pastebin.com/NuurLgvq
On Thu, Feb 13, 2014 at 2:05 PM, Matthaus Owens wrote:
> Rudy,
>
> You also need to uninstall the facter and hiera gems, as they may be
> contributing to your issues. Aside from that, what happens if you run
> `puppet agent --no-daemonize --verbose --logdest console`? Does it also
> error out? If so, how?
>
>
> On Thu, Feb 13, 2014 at 12:14 PM, Rudy McComb wrote:
>
>> Hi Moses,
>>
>> I was able to successfully uninstall the previous versions of gem
>> installed 'puppet'.
>>
>> i did reinstall with dmg but and still having puppetd exit with a code of
>> 1.
>>
>> what am i doing wrong?
>>
>> here is my updated plist and manifest to start launchctl
>>
>> http://pastebin.com/CX56cucf
>> http://pastebin.com/NuurLgvq
>>
>>
>>
>> On Wed, Feb 12, 2014 at 9:19 AM, Rudy McComb wrote:
>>
>>> Hi Moses,
>>>
>>> I was able to successfully uninstall the previous versions of gem
>>> installed 'puppet'.
>>>
>>> i did reinstall with dmg but and still having puppetd exit with a code
>>> of 1.
>>>
>>> what am i doing wrong?
>>>
>>> here is my updated plist and manifest to start launchctl
>>>
>>> http://pastebin.com/CX56cucf
>>> http://pastebin.com/NuurLgvq
>>>
>>>
>>>
>>>
>>> On Tuesday, February 11, 2014 12:21:59 PM UTC-8, Moses Mendoza wrote:
>>>
>>>> Hi Rudy,
>>>>
>>>> To uninstall a gem, just do `gem uninstall `, e.g. `gem
>>>> uninstall puppet.`.
>>>>
>>>> Just to clarify, the directory you pointed out isn't the gem dir, it's
>>>> the Mavericks system ruby site dir.
>>>>
>>>> As you discovered, OSX, the path "/usr/lib/ruby/site_ruby" is actually
>>>> a symlink to the directory "/Library/Ruby/Site." This directory is where
>>>> the dmg's of puppet, hiera, and facter install to (as shown in your image).
>>>> Prior to Puppet 3.4.0 and Facter 1.7.5, the dmgs would install in the
>>>> ruby-version-specific subdirectory, "/Library/Ruby/Site/1.8", but we've
>>>> moved away from that, as "/Library/Ruby/Site" is in the load path in OSX
>>>> versions going awhile back and won't break when ruby versions change.
>>>>
>>>> The gem dir is actually a separate location, where rubygems stores
>>>> information about itself, including all of your installed gems. To see the
>>>> system gem dir, do `/usr/bin/ruby -e 'puts Gem::dir'`. This should show you
>>>> "/Library/Ruby/Gems/2.0.0/", which contains a subdirectory ("gems") with
>>>> all of your installed gems. Hope that helps.
>>>>
>>>> Moses
>>>>
>>>>
>>>> On Tue, Feb 11, 2014 at 9:23 AM, Rudy McComb wrote:
>>>>
>>>>>
>>>>> <https://lh4.googleusercontent.com/-1Y6RPiM0C2A/UvpcG1v6NCI/AAs/OXNKqoF8KHk/s1600/Screen+Shot+2014-02-11+at+9.16.58+AM.png>
>>>>> Moses,
>>>>>
>>>>> can i rm puppet facter and hiera from the gem dir
>>>>> (usr/lib/ruby/site_ruby) w/o breaking puppet dmg installed in correct
>>>>> location?
>>>>>
>>>>> or is there another remedy you propose?
>>>>>
>>>>> thanks
>>>>>
>>>>>
>>>>> On Tuesday, February 11, 2014 8:42:31 AM UTC-8, Moses Mendoza wrote:
>>>>>
>>>>>> Hi Rudy,
>>>>>>
>>>>>> Installing puppet,facter via dmg and also via gem is almost certainly
>>>>>> a contributing factor to your issues. The dmg installs to ruby's
>>>>>> sitedir (in the load path) and the gem installs to rubygems' gem dir
>>>>>> (also in the load path). This means you have two installs of puppet
>>>>>> at
>>>>>> separate versions in the same ruby load path. This will break things!
>>>>>> Charlie explains briefly why this won't work, here:
>>>>>> https://projects.puppetlabs.com/issues/19
Re: [Puppet Users] puppet post install launchd osx
Matthaus,
Here is my output from that run
cabimd011032:~ madmin$ sudo puppet agent --no-daemonize --verbose --logdest
console
Notice: Starting Puppet client version 3.4.3
Error: Could not run: Could not create PID file:
/var/lib/puppet/run/agent.pid
cabimd011032:~ madmin$
On Thursday, February 13, 2014 2:05:11 PM UTC-8, Matthaus Litteken wrote:
>
> Rudy,
>
> You also need to uninstall the facter and hiera gems, as they may be
> contributing to your issues. Aside from that, what happens if you run
> `puppet agent --no-daemonize --verbose --logdest console`? Does it also
> error out? If so, how?
>
>
> On Thu, Feb 13, 2014 at 12:14 PM, Rudy McComb
>
> > wrote:
>
>> Hi Moses,
>>
>> I was able to successfully uninstall the previous versions of gem
>> installed 'puppet'.
>>
>> i did reinstall with dmg but and still having puppetd exit with a code of
>> 1.
>>
>> what am i doing wrong?
>>
>> here is my updated plist and manifest to start launchctl
>>
>> http://pastebin.com/CX56cucf
>> http://pastebin.com/NuurLgvq
>>
>>
>>
>> On Wed, Feb 12, 2014 at 9:19 AM, Rudy McComb
>>
>> > wrote:
>>
>>> Hi Moses,
>>>
>>> I was able to successfully uninstall the previous versions of gem
>>> installed 'puppet'.
>>>
>>> i did reinstall with dmg but and still having puppetd exit with a code
>>> of 1.
>>>
>>> what am i doing wrong?
>>>
>>> here is my updated plist and manifest to start launchctl
>>>
>>> http://pastebin.com/CX56cucf
>>> http://pastebin.com/NuurLgvq
>>>
>>>
>>>
>>>
>>> On Tuesday, February 11, 2014 12:21:59 PM UTC-8, Moses Mendoza wrote:
>>>
>>>> Hi Rudy,
>>>>
>>>> To uninstall a gem, just do `gem uninstall `, e.g. `gem
>>>> uninstall puppet.`.
>>>>
>>>> Just to clarify, the directory you pointed out isn't the gem dir, it's
>>>> the Mavericks system ruby site dir.
>>>>
>>>> As you discovered, OSX, the path "/usr/lib/ruby/site_ruby" is actually
>>>> a symlink to the directory "/Library/Ruby/Site." This directory is where
>>>> the dmg's of puppet, hiera, and facter install to (as shown in your
>>>> image).
>>>> Prior to Puppet 3.4.0 and Facter 1.7.5, the dmgs would install in the
>>>> ruby-version-specific subdirectory, "/Library/Ruby/Site/1.8", but we've
>>>> moved away from that, as "/Library/Ruby/Site" is in the load path in OSX
>>>> versions going awhile back and won't break when ruby versions change.
>>>>
>>>> The gem dir is actually a separate location, where rubygems stores
>>>> information about itself, including all of your installed gems. To see the
>>>> system gem dir, do `/usr/bin/ruby -e 'puts Gem::dir'`. This should show
>>>> you
>>>> "/Library/Ruby/Gems/2.0.0/", which contains a subdirectory ("gems") with
>>>> all of your installed gems. Hope that helps.
>>>>
>>>> Moses
>>>>
>>>>
>>>> On Tue, Feb 11, 2014 at 9:23 AM, Rudy McComb wrote:
>>>>
>>>>>
>>>>> <https://lh4.googleusercontent.com/-1Y6RPiM0C2A/UvpcG1v6NCI/AAs/OXNKqoF8KHk/s1600/Screen+Shot+2014-02-11+at+9.16.58+AM.png>
>>>>> Moses,
>>>>>
>>>>> can i rm puppet facter and hiera from the gem dir
>>>>> (usr/lib/ruby/site_ruby) w/o breaking puppet dmg installed in correct
>>>>> location?
>>>>>
>>>>> or is there another remedy you propose?
>>>>>
>>>>> thanks
>>>>>
>>>>>
>>>>> On Tuesday, February 11, 2014 8:42:31 AM UTC-8, Moses Mendoza wrote:
>>>>>
>>>>>> Hi Rudy,
>>>>>>
>>>>>> Installing puppet,facter via dmg and also via gem is almost certainly
>>>>>> a contributing factor to your issues. The dmg installs to ruby's
>>>>>> sitedir (in the load path) and the gem installs to rubygems' gem dir
>>>>>> (also in the load path). This means you have two installs of puppet
>>>>>> at
>>>>>> separate versions in the same ruby load path. This will break things!
>>>>>> Charlie explains briefly why this won't work, here
Re: [Puppet Users] puppet post install launchd osx
Hi Moses,
I was able to successfully uninstall the previous versions of gem installed
'puppet'.
i did reinstall with dmg but and still having puppetd exit with a code of 1.
what am i doing wrong?
here is my updated plist and manifest to start launchctl
http://pastebin.com/CX56cucf
http://pastebin.com/NuurLgvq
On Wed, Feb 12, 2014 at 9:19 AM, Rudy McComb wrote:
> Hi Moses,
>
> I was able to successfully uninstall the previous versions of gem
> installed 'puppet'.
>
> i did reinstall with dmg but and still having puppetd exit with a code of
> 1.
>
> what am i doing wrong?
>
> here is my updated plist and manifest to start launchctl
>
> http://pastebin.com/CX56cucf
> http://pastebin.com/NuurLgvq
>
>
>
>
> On Tuesday, February 11, 2014 12:21:59 PM UTC-8, Moses Mendoza wrote:
>
>> Hi Rudy,
>>
>> To uninstall a gem, just do `gem uninstall `, e.g. `gem
>> uninstall puppet.`.
>>
>> Just to clarify, the directory you pointed out isn't the gem dir, it's
>> the Mavericks system ruby site dir.
>>
>> As you discovered, OSX, the path "/usr/lib/ruby/site_ruby" is actually a
>> symlink to the directory "/Library/Ruby/Site." This directory is where the
>> dmg's of puppet, hiera, and facter install to (as shown in your image).
>> Prior to Puppet 3.4.0 and Facter 1.7.5, the dmgs would install in the
>> ruby-version-specific subdirectory, "/Library/Ruby/Site/1.8", but we've
>> moved away from that, as "/Library/Ruby/Site" is in the load path in OSX
>> versions going awhile back and won't break when ruby versions change.
>>
>> The gem dir is actually a separate location, where rubygems stores
>> information about itself, including all of your installed gems. To see the
>> system gem dir, do `/usr/bin/ruby -e 'puts Gem::dir'`. This should show you
>> "/Library/Ruby/Gems/2.0.0/", which contains a subdirectory ("gems") with
>> all of your installed gems. Hope that helps.
>>
>> Moses
>>
>>
>> On Tue, Feb 11, 2014 at 9:23 AM, Rudy McComb wrote:
>>
>>>
>>> <https://lh4.googleusercontent.com/-1Y6RPiM0C2A/UvpcG1v6NCI/AAs/OXNKqoF8KHk/s1600/Screen+Shot+2014-02-11+at+9.16.58+AM.png>
>>> Moses,
>>>
>>> can i rm puppet facter and hiera from the gem dir
>>> (usr/lib/ruby/site_ruby) w/o breaking puppet dmg installed in correct
>>> location?
>>>
>>> or is there another remedy you propose?
>>>
>>> thanks
>>>
>>>
>>> On Tuesday, February 11, 2014 8:42:31 AM UTC-8, Moses Mendoza wrote:
>>>
>>>> Hi Rudy,
>>>>
>>>> Installing puppet,facter via dmg and also via gem is almost certainly
>>>> a contributing factor to your issues. The dmg installs to ruby's
>>>> sitedir (in the load path) and the gem installs to rubygems' gem dir
>>>> (also in the load path). This means you have two installs of puppet at
>>>> separate versions in the same ruby load path. This will break things!
>>>> Charlie explains briefly why this won't work, here:
>>>> https://projects.puppetlabs.com/issues/19670. You should install from
>>>> gem or dmg, but not both:) Also, just to be clear, the dmg creates the
>>>> puppet user, but the gem does not. Finally, facter 1.7.5 was released
>>>> yesterday, which has mavericks compatibility when installed via dmg.
>>>> Also, my apologies for calling you 'Ryan'!
>>>>
>>>> cheers
>>>> Moses
>>>>
>>>> On Mon, Feb 10, 2014 at 12:14 PM, Rudy McComb
>>>> wrote:
>>>> > Hi Moses,
>>>> >
>>>> > I'm on Puppet 3.4.2, Facter 1.7.4, Mavericks 10.9.1 and installed
>>>> with the
>>>> > dmg. I also keep puppet updated
>>>> > using gem update puppet.
>>>> >
>>>> > ill install puppet and facter with the dmg and then gem install
>>>> puppet so
>>>> > that it creates the nec users groups etc for puppet.
>>>> >
>>>> > I have updated the plist to point to the newer version of ruby since
>>>> > upgraded macs keep both directories.
>>>> >
>>>> >
>>>> > On Monday, February 10, 2014 11:49:54 AM UTC-8, Moses Mendoza wrote:
>>>> >>
>>>> >> On Mon, Feb 10, 2014 at 10:55 AM, Rudy McComb
>>>> wrote:
>
Re: [Puppet Users] puppet post install launchd osx
Hi Moses,
I was able to successfully uninstall the previous versions of gem installed
'puppet'.
i did reinstall with dmg but and still having puppetd exit with a code of 1.
what am i doing wrong?
here is my updated plist and manifest to start launchctl
http://pastebin.com/CX56cucf
http://pastebin.com/NuurLgvq
On Tuesday, February 11, 2014 12:21:59 PM UTC-8, Moses Mendoza wrote:
>
> Hi Rudy,
>
> To uninstall a gem, just do `gem uninstall `, e.g. `gem
> uninstall puppet.`.
>
> Just to clarify, the directory you pointed out isn't the gem dir, it's the
> Mavericks system ruby site dir.
>
> As you discovered, OSX, the path "/usr/lib/ruby/site_ruby" is actually a
> symlink to the directory "/Library/Ruby/Site." This directory is where the
> dmg's of puppet, hiera, and facter install to (as shown in your image).
> Prior to Puppet 3.4.0 and Facter 1.7.5, the dmgs would install in the
> ruby-version-specific subdirectory, "/Library/Ruby/Site/1.8", but we've
> moved away from that, as "/Library/Ruby/Site" is in the load path in OSX
> versions going awhile back and won't break when ruby versions change.
>
> The gem dir is actually a separate location, where rubygems stores
> information about itself, including all of your installed gems. To see the
> system gem dir, do `/usr/bin/ruby -e 'puts Gem::dir'`. This should show you
> "/Library/Ruby/Gems/2.0.0/", which contains a subdirectory ("gems") with
> all of your installed gems. Hope that helps.
>
> Moses
>
>
> On Tue, Feb 11, 2014 at 9:23 AM, Rudy McComb
> > wrote:
>
>>
>> <https://lh4.googleusercontent.com/-1Y6RPiM0C2A/UvpcG1v6NCI/AAs/OXNKqoF8KHk/s1600/Screen+Shot+2014-02-11+at+9.16.58+AM.png>
>> Moses,
>>
>> can i rm puppet facter and hiera from the gem dir
>> (usr/lib/ruby/site_ruby) w/o breaking puppet dmg installed in correct
>> location?
>>
>> or is there another remedy you propose?
>>
>> thanks
>>
>>
>> On Tuesday, February 11, 2014 8:42:31 AM UTC-8, Moses Mendoza wrote:
>>
>>> Hi Rudy,
>>>
>>> Installing puppet,facter via dmg and also via gem is almost certainly
>>> a contributing factor to your issues. The dmg installs to ruby's
>>> sitedir (in the load path) and the gem installs to rubygems' gem dir
>>> (also in the load path). This means you have two installs of puppet at
>>> separate versions in the same ruby load path. This will break things!
>>> Charlie explains briefly why this won't work, here:
>>> https://projects.puppetlabs.com/issues/19670. You should install from
>>> gem or dmg, but not both:) Also, just to be clear, the dmg creates the
>>> puppet user, but the gem does not. Finally, facter 1.7.5 was released
>>> yesterday, which has mavericks compatibility when installed via dmg.
>>> Also, my apologies for calling you 'Ryan'!
>>>
>>> cheers
>>> Moses
>>>
>>> On Mon, Feb 10, 2014 at 12:14 PM, Rudy McComb
>>> wrote:
>>> > Hi Moses,
>>> >
>>> > I'm on Puppet 3.4.2, Facter 1.7.4, Mavericks 10.9.1 and installed with
>>> the
>>> > dmg. I also keep puppet updated
>>> > using gem update puppet.
>>> >
>>> > ill install puppet and facter with the dmg and then gem install puppet
>>> so
>>> > that it creates the nec users groups etc for puppet.
>>> >
>>> > I have updated the plist to point to the newer version of ruby since
>>> > upgraded macs keep both directories.
>>> >
>>> >
>>> > On Monday, February 10, 2014 11:49:54 AM UTC-8, Moses Mendoza wrote:
>>> >>
>>> >> On Mon, Feb 10, 2014 at 10:55 AM, Rudy McComb
>>> wrote:
>>> >> > I'm having a an issue with running puppet as launchd. I'm using
>>> this
>>> >> > http://docs.puppetlabs.com/guides/files/com.puppetlabs.puppet.plistand
>>> >> > on
>>> >> > some macs it will run and start at reboot and on others it doesnt.
>>> >> >
>>> >> > According to the logs puppet is exiting with a code of 1. What can
>>> i
>>> >> > due to
>>> >> > ensure that the puppet launchd mod runs uninhibited.
>>> >> >
>>> >> > http://pastebin.com/raw.php?i=CX56cucf
>>> >> >
>>> >> > I&
Re: [Puppet Users] puppet post install launchd osx
<https://lh4.googleusercontent.com/-1Y6RPiM0C2A/UvpcG1v6NCI/AAs/OXNKqoF8KHk/s1600/Screen+Shot+2014-02-11+at+9.16.58+AM.png> Moses, can i rm puppet facter and hiera from the gem dir (usr/lib/ruby/site_ruby) w/o breaking puppet dmg installed in correct location? or is there another remedy you propose? thanks On Tuesday, February 11, 2014 8:42:31 AM UTC-8, Moses Mendoza wrote: > > Hi Rudy, > > Installing puppet,facter via dmg and also via gem is almost certainly > a contributing factor to your issues. The dmg installs to ruby's > sitedir (in the load path) and the gem installs to rubygems' gem dir > (also in the load path). This means you have two installs of puppet at > separate versions in the same ruby load path. This will break things! > Charlie explains briefly why this won't work, here: > https://projects.puppetlabs.com/issues/19670. You should install from > gem or dmg, but not both:) Also, just to be clear, the dmg creates the > puppet user, but the gem does not. Finally, facter 1.7.5 was released > yesterday, which has mavericks compatibility when installed via dmg. > Also, my apologies for calling you 'Ryan'! > > cheers > Moses > > On Mon, Feb 10, 2014 at 12:14 PM, Rudy McComb > > > wrote: > > Hi Moses, > > > > I'm on Puppet 3.4.2, Facter 1.7.4, Mavericks 10.9.1 and installed with > the > > dmg. I also keep puppet updated > > using gem update puppet. > > > > ill install puppet and facter with the dmg and then gem install puppet > so > > that it creates the nec users groups etc for puppet. > > > > I have updated the plist to point to the newer version of ruby since > > upgraded macs keep both directories. > > > > > > On Monday, February 10, 2014 11:49:54 AM UTC-8, Moses Mendoza wrote: > >> > >> On Mon, Feb 10, 2014 at 10:55 AM, Rudy McComb > wrote: > >> > I'm having a an issue with running puppet as launchd. I'm using this > >> > http://docs.puppetlabs.com/guides/files/com.puppetlabs.puppet.plistand > >> > on > >> > some macs it will run and start at reboot and on others it doesnt. > >> > > >> > According to the logs puppet is exiting with a code of 1. What can i > >> > due to > >> > ensure that the puppet launchd mod runs uninhibited. > >> > > >> > http://pastebin.com/raw.php?i=CX56cucf > >> > > >> > I've also tried using a modified version of this > >> > > >> > > >> > >> > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> > >> > > >> > > >> > EnvironmentVariables > >> > > >> > PATH > >> > /sbin:/usr/sbin:/bin:/usr/bin > >> > RUBYLIB > >> > /usr/lib/ruby/site_ruby/1.8/ > >> > > >> > Label > >> > com.puppetlabs.puppet > >> > KeepAlive > >> > > >> > ProgramArguments > >> > > >> > /usr/bin/puppet > >> > agent > >> > --verbose > >> > --no-daemonize > >> > --logdest > >> > console > >> > > >> > RunAtLoad > >> > > >> > ServiceDescription > >> > Puppet Daemon > >> > ServiceIPC > >> > > >> > StandardErrorPath > >> > /var/log/puppet/puppet.err > >> > StandardOutPath > >> > /var/log/puppet/puppet.out > >> > > >> > > >> > > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "Puppet Users" group. > >> > To unsubscribe from this group and stop receiving emails from it, > send > >> > an > >> > email to puppet-users...@googlegroups.com. > >> > To view this discussion on the web visit > >> > > >> > > https://groups.google.com/d/msgid/puppet-users/0b798c59-e87c-4dde-886f-885b1a2045ea%40googlegroups.com. > > > >> > For more options, visit https://groups.google.com/groups/opt_out. > >> > >>
Re: [Puppet Users] puppet post install launchd osx
Hi Moses, I'm on Puppet 3.4.2, Facter 1.7.4, Mavericks 10.9.1 and installed with the dmg. I also keep puppet updated using gem update puppet. ill install puppet and facter with the dmg and then gem install puppet so that it creates the nec users groups etc for puppet. I have updated the plist to point to the newer version of ruby since upgraded macs keep both directories. On Monday, February 10, 2014 11:49:54 AM UTC-8, Moses Mendoza wrote: > > On Mon, Feb 10, 2014 at 10:55 AM, Rudy McComb > > > wrote: > > I'm having a an issue with running puppet as launchd. I'm using this > > http://docs.puppetlabs.com/guides/files/com.puppetlabs.puppet.plist and > on > > some macs it will run and start at reboot and on others it doesnt. > > > > According to the logs puppet is exiting with a code of 1. What can i > due to > > ensure that the puppet launchd mod runs uninhibited. > > > > http://pastebin.com/raw.php?i=CX56cucf > > > > I've also tried using a modified version of this > > > > > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> > > > > > > EnvironmentVariables > > > > PATH > > /sbin:/usr/sbin:/bin:/usr/bin > > RUBYLIB > > /usr/lib/ruby/site_ruby/1.8/ > > > > Label > > com.puppetlabs.puppet > > KeepAlive > > > > ProgramArguments > > > > /usr/bin/puppet > > agent > > --verbose > > --no-daemonize > > --logdest > > console > > > > RunAtLoad > > > > ServiceDescription > > Puppet Daemon > > ServiceIPC > > > > StandardErrorPath > > /var/log/puppet/puppet.err > > StandardOutPath > > /var/log/puppet/puppet.out > > > > > > > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Puppet Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to puppet-users...@googlegroups.com . > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/puppet-users/0b798c59-e87c-4dde-886f-885b1a2045ea%40googlegroups.com. > > > > For more options, visit https://groups.google.com/groups/opt_out. > > Hi Ryan, > > Unfortunately the plist at that link is a little out of date. The > ServiceIPC and ServiceDescription keys aren't supported in recent > versions of OSX. You can just remove them, really. Also, how did you > install puppet, which version of puppet did you install, and on what > version of OSX? Puppet >= 3.4.0 installed via dmg lives in > /Library/Ruby/Site, to make it compatible with ruby 2 on Mavericks, so > you may want to update the plist to reflect this. Puppet < 3.4.0 > installed via dmg is installed to the "RUBYLIB" in your plist. > Finally, if you're using mavericks and installing from dmg, you'll > need facter 1.7.5-rc1 or later (I believe we are shipping the final > version of facter 1.7.5 very soon). > > -- > Moses Mendoza > Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco - > http://bit.ly/pupconf14 > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/091b78d2-561c-409c-984c-175fca39211b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet post install launchd osx
I'm having a an issue with running puppet as launchd. I'm using this http://docs.puppetlabs.com/guides/files/com.puppetlabs.puppet.plist and on some macs it will run and start at reboot and on others it doesnt. According to the logs puppet is exiting with a code of 1. What can i due to ensure that the puppet launchd mod runs uninhibited. http://pastebin.com/raw.php?i=CX56cucf I've also tried using a modified version of this http://www.apple.com/DTDs/PropertyList-1.0.dtd";> EnvironmentVariables PATH /sbin:/usr/sbin:/bin:/usr/bin RUBYLIB /usr/lib/ruby/site_ruby/1.8/ Label com.puppetlabs.puppet KeepAlive ProgramArguments /usr/bin/puppet agent --verbose --no-daemonize --logdest console RunAtLoad ServiceDescription Puppet Daemon ServiceIPC StandardErrorPath /var/log/puppet/puppet.err StandardOutPath /var/log/puppet/puppet.out -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0b798c59-e87c-4dde-886f-885b1a2045ea%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
