my thought in running the limited version of PE 2.0 Learning VM is that out of the box I could have a fully working Pupet master on a VM I could demo out with 10 clients.
didn't realize getting the certs working for the agents would be such an undocumented nightmare . . .oh the joys of open source On Mar 21, 4:32 pm, Denmat <tu2bg...@gmail.com> wrote: > That does complicate it for me a bit, I haven't had much of a go on PE. > > Essentially they are the same tools but PE runs behind passenger. -- I don't > have a working copy of PE to point you in the right directions for config > locations but there will be ssl_x_header directives in the puppet.conf on the > master that you can hash out to run the daemon without passenger. You need to > stop the httpd service that is running PE too. > > There maybe other things that need to be done as well. But that is a start > anyway. > > You can always install the open source version until you get comfy with the > way it works though. > > Cheers > Den > > On 22/03/2012, at 10:02, MrT <markthomasso...@gmail.com> wrote: > > > > > > > > > I should have clarified I am running the 10 user version of PE 2.0 if > > that makes a difference > > > On Mar 21, 2:33 pm, Denmat <tu2bg...@gmail.com> wrote: > >> Okay, sorry might have lead you down the wrong path a bit. --test on agent > >> is equivalent to --no-daemonize and a few other options. > > >> Agent: > >> sudo puppet agent --test --server <master> --verbose <--debug --noop> > > >> Master: > >> sudo puppetd --no-daemonize --verbose <--debug> > > >> Generally speaking, your client can newer than the master but not the > >> other way round. Most people on the list say you should have the same > >> versions on both. > > >> Have you seen the puppetlabs repo? They should have latest packages (sorry > >> don't know URL off the top of my head). Either that or you use gem to > >> install. > > >> Cheers, > >> Den > > >> On 22/03/2012, at 7:38, MrT <markthomasso...@gmail.com> wrote: > > >>> what EXACTLY is the syntax for running agent and server in no- > >>> daemonize mode > > >>> master is on centOS 5.7 running Puppet 2.7.6 > >>> agent is Debian6 running running 2.7.10 > > >>> any issues in running an earlier version of pupet on master than > >>> client > > >>> is there an EASY way to upgrade the master to 2.7.10 > > >>> On Mar 21, 1:18 pm, Denmat <tu2bg...@gmail.com> wrote: > >>>> Hi mrT > > >>>> Can you provide the error you receive? > > >>>> Another easy way to test what's going on is to run the master and agent > >>>> in --no-daemonize mode (stop existing master and agent and add that to > >>>> the command line with verbose and debug). > > >>>> Also, what version and OS are you running? > > >>>> So a quick run down of stuff to try(some you have done): > >>>> * make sure you can resolve the masters dns name from the client. > >>>> * stop all puppet services on master and client. > >>>> * remove the ssl dir on both. > >>>> * start the master in --no-daemonize mode > >>>> * start the agent in --no-daemonize mode > >>>> * if it errors use openssl s_client to check the certificate from the > >>>> master, and confirm the common name is that of the masters dns name. > > >>>> Okay, see how that goes. > > >>>> Cheers, > >>>> Den > > >>>> On 22/03/2012, at 6:36, MrT <markthomasso...@gmail.com> wrote: > > >>>>> I am a newbie to Puppet, so be gentle > > >>>>> Running puppet master on the learning VM in a test environment > > >>>>> testing connectivity of agents of various clients also VMs > > >>>>> running into issues on the master accepting cert requests from agents > > >>>>> confirm network connectivity from agent to master > >>>>> confirmed nothing else is running on port 8140 on master > >>>>> can telnet to port 8140 on master from agent > >>>>> iptable is turned off on client and master > >>>>> confirmed time of two machines are in sync and in the same time zone > >>>>> cleared out the SSL keys on clients > >>>>> confirmed thee were no old certs on master > > >>>>> any other troubleshooting steps Ican take > > >>>>> The existing documentation on basic troubleshooting seams somewhat > >>>>> lacking !!!! > >>>>>http://docs.puppetlabs.com/pe/2.0/maint_common_config_errors.html > > >>>>> -- > >>>>> You received this message because you are subscribed to the Google > >>>>> Groups "Puppet Users" group. > >>>>> To post to this group, send email to puppet-users@googlegroups.com. > >>>>> To unsubscribe from this group, send email to > >>>>> puppet-users+unsubscr...@googlegroups.com. > >>>>> For more options, visit this group > >>>>> athttp://groups.google.com/group/puppet-users?hl=en. > > >>> -- > >>> You received this message because you are subscribed to the Google Groups > >>> "Puppet Users" group. > >>> To post to this group, send email to puppet-users@googlegroups.com. > >>> To unsubscribe from this group, send email to > >>> puppet-users+unsubscr...@googlegroups.com. > >>> For more options, visit this group > >>> athttp://groups.google.com/group/puppet-users?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
