[Puppet Users] Joining a Windows domain
I have use the Windows DSC module to add a window 2016 server to a domain.
dsc_xcomputer { 'domain_membership':
dsc_name => $facts['hostname'],
dsc_domainname => $domain_name,
dsc_credential => {
'user' => "${username}@${domain_name}",
'password' => $sensitive_password
},
dsc_joinou => $machine_ou,
}
reboot { 'after_domain_membership' :
subscribe => Dsc_xcomputer['domain_membership'],
}
}
After the reboot the Server joins the domain, but I am unable to log in
with my domain credentials to the server.
I am part of the admin group for the domain. Looking at the active
directory it appears that the server has joined, but that I don't seem to
have rights to remote access this server.
If I join the domain manually without puppet, I have no problem
accessing the server.
Any idea's?
--
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/0e2b8150-6671-4678-8bb6-b65d7d352e02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] How to start puppet master for v6.0.0 or late
Hi there, I am new to puppet. I want to know how to start puppet master for v6.0.0 or late versions. For version below v6.0.0, I can install puppet by: gem install puppet -v 5.5.14 Then start by : puppet master --verbose --no-daemonizepuppet However, after v6.0.0, there is no subcommand "master" option. If installing v6.4.2, the "puppet help" shows below: "puppet]# puppet help Usage: puppet [options] [options] Available subcommands: Common: agent The puppet agent daemon apply Apply Puppet manifests locally configInteract with Puppet's settings. help Display Puppet help. lookupInteractive Hiera lookup moduleCreates, installs and searches for modules on the Puppet Forge. resource The resource abstraction layer shell Specialized: catalog Compile, save, view, and convert catalogs. describe Display help about resource types deviceManage remote network devices doc Generate Puppet references epp Interact directly with the EPP template parser/renderer. facts Retrieve and store facts. filebucketStore and retrieve files in a filebucket generate Generates Puppet code from Ruby definitions. node View and manage node definitions. parserInteract directly with the parser. scriptRun a puppet manifests as a script without compiling a catalog ssl Manage SSL keys and certificates for puppet SSL clients Thanks, -- 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/0d3ae17b-e47e-4c79-a631-88c2dc163311%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] class invocation conflicts
Most likely because that’s an easy way to show the parameters a class
supports. Some modules use hiera data to show that, though it is a bit more
complicated to explain and understand, especially for novices.
On Tue, May 21, 2019 at 9:42 AM Peter Berghold
wrote:
> Using include instead of class makes sense to me and was my instinctive
> thought.
>
> Why on earth, then, do all the (or most) of the Puppet Forge modules use
> the
>
> class{'myclass':
> param1 => 'thing'
> }
>
> patterns in their examples. I had begun to believe that was the preferred
> pattern.
>
> I will mend my ways.
>
> On Mon, May 20, 2019 at 3:33 PM Henrik Lindberg <
> henrik.lindb...@puppet.com> wrote:
>
>> On 2019-05-20 18:57, Peter Berghold wrote:
>> > So here I am I have a base profile for my Ubuntu (Debian family)
>> > machines that invokes the class
>> >
>> > class{'apt':
>> > ... some paramters
>> > }
>> >
>> > I then invoke the class
>> >
>> > class{'postgresql': }
>> >
>> > and now Puppet is screaming that the class 'apt' cannot be invoked
>> > twice. This seems to be a flaw in Puppet manifests to me. How to fix?
>> >
>> >
>>
>> The best practice is to not use the resource like `class { name: ... }`
>> syntax to declare a class and instead use `include name` and letting all
>> parameter values come from hiera via automatic parameter lookup.
>>
>> That way, you can include the class as many times as you like - as the
>> parameters are the same every time. Unfortunately, the compiler cannot
>> do the same when classes are declared with parameters even if all places
>> this is done use the exact same values.
>>
>> While it is possible to have a single `class { name: ... }` declaration
>> with subsequent `include name` declarations, the opposite does not work.
>>
>> Hope this helps.
>> - henrik
>>
>> > --
>> >
>> > Peter L. Berghold salty.cowd...@gmail.com > salty.cowd...@gmail.com>
>> >
>> > http://devops.berghold.net
>> >
>> >
>> > --
>> > 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/CAArvnv2Ya1Vo1R%3D%2B3YW%3DMp%2BubL%2BZR_WFG1J4o_7OKe33tfm4vw%40mail.gmail.com
>> > <
>> https://groups.google.com/d/msgid/puppet-users/CAArvnv2Ya1Vo1R%3D%2B3YW%3DMp%2BubL%2BZR_WFG1J4o_7OKe33tfm4vw%40mail.gmail.com?utm_medium=email_source=footer
>> >.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>>
>> Visit my Blog "Puppet on the Edge"
>> http://puppet-on-the-edge.blogspot.se/
>>
>> --
>> 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/qbuve5%246tlm%241%40blaine.gmane.org
>> .
>> For more options, visit https://groups.google.com/d/optout.
>
>
>>
>
> --
>
> Peter L. Berghold salty.cowd...@gmail.com
>
> http://devops.berghold.net
>
>
> --
> 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/CAArvnv3dQ-t2W_0%2BNpq0qD9%2BkHAnsLXfwJtJQHxJURywdb7wZA%40mail.gmail.com
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Rob Nelson
--
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/CAC76iT9NzEmv8cgMfo-_J3gf-HB-6odjnT1GxOyPyL85aVCVRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] class invocation conflicts
Using include instead of class makes sense to me and was my instinctive
thought.
Why on earth, then, do all the (or most) of the Puppet Forge modules use
the
class{'myclass':
param1 => 'thing'
}
patterns in their examples. I had begun to believe that was the preferred
pattern.
I will mend my ways.
On Mon, May 20, 2019 at 3:33 PM Henrik Lindberg
wrote:
> On 2019-05-20 18:57, Peter Berghold wrote:
> > So here I am I have a base profile for my Ubuntu (Debian family)
> > machines that invokes the class
> >
> > class{'apt':
> > ... some paramters
> > }
> >
> > I then invoke the class
> >
> > class{'postgresql': }
> >
> > and now Puppet is screaming that the class 'apt' cannot be invoked
> > twice. This seems to be a flaw in Puppet manifests to me. How to fix?
> >
> >
>
> The best practice is to not use the resource like `class { name: ... }`
> syntax to declare a class and instead use `include name` and letting all
> parameter values come from hiera via automatic parameter lookup.
>
> That way, you can include the class as many times as you like - as the
> parameters are the same every time. Unfortunately, the compiler cannot
> do the same when classes are declared with parameters even if all places
> this is done use the exact same values.
>
> While it is possible to have a single `class { name: ... }` declaration
> with subsequent `include name` declarations, the opposite does not work.
>
> Hope this helps.
> - henrik
>
> > --
> >
> > Peter L. Berghold salty.cowd...@gmail.com salty.cowd...@gmail.com>
> >
> > http://devops.berghold.net
> >
> >
> > --
> > 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/CAArvnv2Ya1Vo1R%3D%2B3YW%3DMp%2BubL%2BZR_WFG1J4o_7OKe33tfm4vw%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/puppet-users/CAArvnv2Ya1Vo1R%3D%2B3YW%3DMp%2BubL%2BZR_WFG1J4o_7OKe33tfm4vw%40mail.gmail.com?utm_medium=email_source=footer
> >.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> 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/qbuve5%246tlm%241%40blaine.gmane.org
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Peter L. Berghold salty.cowd...@gmail.com
http://devops.berghold.net
--
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/CAArvnv3dQ-t2W_0%2BNpq0qD9%2BkHAnsLXfwJtJQHxJURywdb7wZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: puppet agent fails to self-restart on config change
Same issue: May 21 11:26:51 vm01 puppet-agent[419]: Shutdown/restart in progress (:restart_requested); skipping run May 21 12:26:51 vm01 puppet-agent[419]: Shutdown/restart in progress (:restart_requested); skipping run May 21 13:26:51 vm01 puppet-agent[419]: Shutdown/restart in progress (:restart_requested); skipping run On Friday, 29 March 2019 15:13:58 UTC+1, SCHAER Frederic wrote: > > Hi, > > > > For some time now, we’ve seen this kind of logs in our machines : > > (note: we do manage the puppet agent config with puppet) > > > > Mar 29 13:25:50 gate01 puppet-agent[2684]: Processing restart > > Mar 29 13:25:50 gate01 puppet-agent[2684]: Puppet::Agent::Locker.running? > is deprecated as it is inherently unsafe. The only safe way to know if the > lock is locked is to try lock and perform some action and then handle the > LockError that may result. > > Mar 29 13:25:50 gate01 puppet-agent[2684]:(location: > /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent/locker.rb:37:in > `running?') > > Mar 29 13:25:51 gate01 puppet-agent[38303]: Applied catalog in 16.78 > seconds > > Mar 29 13:26:00 gate01 puppet-agent[2684]: Config file > /etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all > config files. > > Mar 29 13:44:16 gate01 puppet-agent[2684]: Shutdown/restart in progress > (:restart_requested); skipping run > > > > Than puppet never runs again because of this stuck restart until we > manually restart the agent. > > puppet-agent-5.5.12 here. > > > > This happens on both el6 and el7 hosts. > > > > Bad thing is that this even happens when puppet is upgraded during our > install process … and we get freshly installed nodes with stuck puppets… > > Off course, this did not happen before. > > > > Would anyone know of a way to get rid of this damn “can’t restart” loop ? > > > > Regards > > > > Frédéric Schaer > > CEA/Saclay > > DRF/IRFU/DEDIP/LIS > > > -- 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/fe3f7f56-1802-441f-be7b-5aeba98bc36d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet 3.7.1 ,Unable to enable debug logs
All , Greetings !, I am facing a problem with my legacy community version puppetmaster 3.7 ,Which stops in between .I was trying to enable the logs ,but the methods mentioned in the documentation ( adding log_level =debug in puppet.conf ) seems not applicable in this version .In my case puppeet master doesnt use JVM and logback too. ps -ef | grep puppet puppetdb 20233 1 2 May17 ?02:37:14 /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/java -XX:OnOutOfMemoryError=kill -9 %p -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -Djava.security.egd=file:/dev/urandom -cp /usr/share/puppetdb/puppetdb.jar clojure.main -m com.puppetlabs.puppetdb.core services -c /etc/puppetdb/conf.d root 25048 1 0 00:01 ?00:00:00 /usr/bin/ruby /usr/bin/puppet agent puppet 26880 1 40 May20 ?03:29:48 /usr/bin/ruby /usr/bin/puppet master Thanks for looking in to this doubt and any help would be appreciated !!! -- 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/acabf542-c306-42f5-a1a6-09f84aafbc61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
