Good morning all, I''ve a VERY new user to puppet and picked up the "Pulling Strings ..." book. I was working through the setup section and ran into a problem. Here''s my environment: Windows Vista box running VMWare Server hosting 2 VMs; each is running Fedora 10. I manually installed Ruby, Factor, and Puppet as per the instructions in the book. All seemd to be going well. I added a puppet user/group to both VMs. I added puppetmaster.testing.com to the /etc/hosts of the client box. When I started puppetmasterd I did NOT get a the complaint message about a missing site.pp ... it just started. I created a site.pp as done in the book''s example and restarted puppetmasterd --verbose --no- daemonize and that display the expected message. However, puppetd on the client did not connect, did not display the "notice: did not receive certificate" and did not repeat after 60 seconds as I was lead to believe would happen if I used puppetd --server puppetmaster.testing.com --verbose --waitforcert 60 and running puppetca --list on the server VM showed no indication that my client was waiting. Any help would be greatly appreciated. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Steve, I can''t think of an obvious reason for failure but to rule out network issues you can run the puppetd command below on the puppetmaster itself , effectively making it a client which is a legitimate thing to do. If that works I would start looking at your network settings between the master / client. Paul 2009/5/26 SteveCriscuoli <stephen.criscuoli@gmail.com>> > Good morning all, > > I''ve a VERY new user to puppet and picked up the "Pulling Strings ..." > book. I was working through the setup section and ran into a problem. > > Here''s my environment: > > Windows Vista box running VMWare Server hosting 2 VMs; each is running > Fedora 10. > > I manually installed Ruby, Factor, and Puppet as per the instructions > in the book. All seemd to be going well. > I added a puppet user/group to both VMs. I added > puppetmaster.testing.com to the /etc/hosts of the client box. > When I started puppetmasterd I did NOT get a the complaint message > about a missing site.pp ... it just started. I created a site.pp as > done in the book''s example and restarted puppetmasterd --verbose --no- > daemonize and that display the expected message. However, puppetd on > the client did not connect, did not display the "notice: did not > receive certificate" and did not repeat after 60 seconds as I was lead > to believe would happen if I used > > puppetd --server puppetmaster.testing.com --verbose --waitforcert 60 > > and running puppetca --list on the server VM showed no indication that > my client was waiting. > > Any help would be greatly appreciated. > > > >-- Paul Matthews ---------------------------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 26 May 2009, at 13:27, SteveCriscuoli wrote:> I manually installed Ruby, Factor, and Puppet as per the instructions > in the book. All seemd to be going well. > I added a puppet user/group to both VMs. I added > puppetmaster.testing.com to the /etc/hosts of the client box. > When I started puppetmasterd I did NOT get a the complaint message > about a missing site.pp ... it just started. I created a site.pp as > done in the book''s example and restarted puppetmasterd --verbose --no- > daemonize and that display the expected message. However, puppetd on > the client did not connect, did not display the "notice: did not > receive certificate" and did not repeat after 60 seconds as I was lead > to believe would happen if I used > > puppetd --server puppetmaster.testing.com --verbose --waitforcert 60 > > and running puppetca --list on the server VM showed no indication that > my client was waiting.Have you checked your iptables setup? Kind regards, Pieter. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
You mentioned that each Fedora install was running in its own VM. Is TCP functional in those VM''s and are they able to communicate with each other ? Cheers Dave On 27/05/2009, at 1:02 AM, Pieter Barrezeele wrote:> > > On 26 May 2009, at 13:27, SteveCriscuoli wrote: > > >> I manually installed Ruby, Factor, and Puppet as per the instructions >> in the book. All seemd to be going well. >> I added a puppet user/group to both VMs. I added >> puppetmaster.testing.com to the /etc/hosts of the client box. >> When I started puppetmasterd I did NOT get a the complaint message >> about a missing site.pp ... it just started. I created a site.pp as >> done in the book''s example and restarted puppetmasterd --verbose -- >> no- >> daemonize and that display the expected message. However, puppetd on >> the client did not connect, did not display the "notice: did not >> receive certificate" and did not repeat after 60 seconds as I was >> lead >> to believe would happen if I used >> >> puppetd --server puppetmaster.testing.com --verbose --waitforcert 60 >> >> and running puppetca --list on the server VM showed no indication >> that >> my client was waiting. > > > Have you checked your iptables setup? > > Kind regards, > > Pieter. > > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hey Dave, I purposely set them up as ''bridged'' so they''re on the same subnet as my entire LAN. I modified the /etc/hosts table on each to have entries for both and can ping each by its name; I''m hoping that was a sufficient test. Appreciate the help, Steve On May 26, 11:09 am, Dave Cheney <d...@cheney.net> wrote:> You mentioned that each Fedora install was running in its own VM. Is > TCP functional in those VM''s and are they able to communicate with > each other ? > > Cheers > > Dave > > On 27/05/2009, at 1:02 AM, Pieter Barrezeele wrote: > > > > > > > On 26 May 2009, at 13:27, SteveCriscuoli wrote: > > >> I manually installed Ruby, Factor, and Puppet as per the instructions > >> in the book. All seemd to be going well. > >> I added a puppet user/group to both VMs. I added > >> puppetmaster.testing.com to the /etc/hosts of the client box. > >> When I started puppetmasterd I did NOT get a the complaint message > >> about a missing site.pp ... it just started. I created a site.pp as > >> done in the book''s example and restarted puppetmasterd --verbose -- > >> no- > >> daemonize and that display the expected message. However, puppetd on > >> the client did not connect, did not display the "notice: did not > >> receive certificate" and did not repeat after 60 seconds as I was > >> lead > >> to believe would happen if I used > > >> puppetd --server puppetmaster.testing.com --verbose --waitforcert 60 > > >> and running puppetca --list on the server VM showed no indication > >> that > >> my client was waiting. > > > Have you checked your iptables setup? > > > Kind regards, > > > Pieter.- Hide quoted text - > > - Show quoted text ---~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hey Pieter, I purposely set up the VMs on the same subnet as my physical boxes. I know that VMWare Server does set up multiple networks but I did have the ability to ping each from the other. I will look into it when I get home from work though. Thanks, Steve On May 26, 11:02 am, Pieter Barrezeele <mac...@gmail.com> wrote:> On 26 May 2009, at 13:27, SteveCriscuoli wrote: > > > > > > > I manually installed Ruby, Factor, and Puppet as per the instructions > > in the book. All seemd to be going well. > > I added a puppet user/group to both VMs. I added > > puppetmaster.testing.com to the /etc/hosts of the client box. > > When I started puppetmasterd I did NOT get a the complaint message > > about a missing site.pp ... it just started. I created a site.pp as > > done in the book''s example and restarted puppetmasterd --verbose --no- > > daemonize and that display the expected message. However, puppetd on > > the client did not connect, did not display the "notice: did not > > receive certificate" and did not repeat after 60 seconds as I was lead > > to believe would happen if I used > > > puppetd --server puppetmaster.testing.com --verbose --waitforcert 60 > > > and running puppetca --list on the server VM showed no indication that > > my client was waiting. > > Have you checked your iptables setup? > > Kind regards, > > Pieter.- Hide quoted text - > > - Show quoted text ---~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Ok, so here''s an update ... I think we''re getting closer to the problem. Since the VMs acquire a new IP each time I start them I made an entry in the /etc/hosts for the host puppet.testing.com Here''s what happened on the server and client windows when running both on the same box: --- server --- root@rh1 steve]# puppetmasterd --verbose --no-daemonize info: Starting server for Puppet version 0.24.8 info: Listening on port 8140 notice: Starting Puppet server version 0.24.8 ^Cnotice: Caught INT; shutting down notice: Shutting down [root@rh1 steve]# puppetmasterd --server puppet.testing.com --verbose --no-daemonize info: Starting server for Puppet version 0.24.8 info: Listening on port 8140 notice: Starting Puppet server version 0.24.8 --- client --- [root@rh1 steve]# puppetd --server puppet.testing.com --verbose -- waitforcert 60 --test warning: Certificate validation failed; consider using the certname configuration option err: Could not retrieve catalog: Certificates were not trusted: hostname was not match with the server certificate warning: Not using cache on failed catalog [root@rh1 steve]# puppetd --server puppet.testing.com --verbose -- waitforcert 60 --test warning: Certificate validation failed; consider using the certname configuration option err: Could not retrieve catalog: Certificates were not trusted: hostname was not match with the server certificate warning: Not using cache on failed catalog On May 26, 12:30 pm, SteveCriscuoli <stephen.criscu...@gmail.com> wrote:> Hey Dave, > > I purposely set them up as ''bridged'' so they''re on the same subnet as > my entire LAN. > I modified the /etc/hosts table on each to have entries for both and > can ping each by > its name; I''m hoping that was a sufficient test. > > Appreciate the help, > > Steve > > On May 26, 11:09 am, Dave Cheney <d...@cheney.net> wrote: > > > > > You mentioned that eachFedorainstall was running in its own VM. Is > > TCP functional in those VM''s and are they able to communicate with > > each other ? > > > Cheers > > > Dave > > > On 27/05/2009, at 1:02 AM, Pieter Barrezeele wrote: > > > > On 26 May 2009, at 13:27, SteveCriscuoli wrote: > > > >> I manually installed Ruby, Factor, and Puppet as per the instructions > > >> in the book. All seemd to be going well. > > >> I added a puppet user/group to both VMs. I added > > >> puppetmaster.testing.com to the /etc/hosts of the client box. > > >> When I started puppetmasterd I did NOT get a the complaint message > > >> about a missing site.pp ... it just started. I created a site.pp as > > >> done in the book''s example and restarted puppetmasterd --verbose -- > > >> no- > > >> daemonize and that display the expected message. However, puppetd on > > >> the client did not connect, did not display the "notice: did not > > >> receive certificate" and did not repeat after 60 seconds as I was > > >> lead > > >> to believe would happen if I used > > > >> puppetd --server puppetmaster.testing.com --verbose --waitforcert 60 > > > >> and running puppetca --list on the server VM showed no indication > > >> that > > >> my client was waiting. > > > > Have you checked your iptables setup? > > > > Kind regards, > > > > Pieter.- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text ---~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---