Hi, For the last couple of days, I have been banging my head against many hard objects to solve some of my puppet setting problems, but I can''t seem to sort it out. All my manifests appear to be correct. On my nodes running puppetd, I''m getting a bunch of HTTP-Error: 500 Internal Server Errors. For examlpe [0;34mdebug: Calling fileserver.describe[0m [0;33merr: Could not call fileserver.describe: #<RuntimeError: HTTP- Error: 500 Internal Server Error >[0m [0;33merr: //Node[default]/File[crontab]: Failed to retrieve current state of resource: HTTP-Error: 500 Internal Server Error Could not describe /files/crontab: HTTP-Error: 500 Internal Server Error at / etc/puppet/manifests/site.pp:153[0m [0;34mdebug: Calling fileserver.describe[0m On my puppetmasterd server, I''m also getting a bunch of error messages like these - which I believe are related... notice: Denying authenticated client domu-12-31-39-00- d9-84.compute-1.internal(67.202.55.67) access to puppetmaster.getconfig debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert name domu-12-31-39-00-d9-84.compute-1.internal notice: Denying authenticated client domu-12-31-39-00- d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert name domu-12-31-39-00-d9-84.compute-1.internal notice: Denying authenticated client domu-12-31-39-00- d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe From my understanding, authentication is working, but I don''t think the file server or file checking mechanism is working....my fileserver.conf settings are wide open... [files] path /var/puppet/files allow * As further evidence, changes in my manifests do not seem to be propagating to the nodes. If any one could help me sort out these error messages and these issues, I would greatly appreciate it. Thanks, Chad http://www.neomantic.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
for fileserver auth, I am using [fileserver], not [files] and it works fine, in the output when puppetmasterd starts, do you have the following message: info: mount[fileserver]: allowing * access On Sep 4, 2:44 pm, "Chad A." <calb...@neomantic.com> wrote:> Hi, > > For the last couple of days, I have been banging my head against many > hard objects to solve some of my puppet setting problems, but I can''t > seem to sort it out. All my manifests appear to be correct. > > On my nodes running puppetd, I''m getting a bunch of HTTP-Error: 500 > Internal Server Errors. For examlpe > > [0;34mdebug: Calling fileserver.describe[0m > [0;33merr: Could not call fileserver.describe: #<RuntimeError: HTTP- > Error: 500 Internal Server Error >[0m > [0;33merr: //Node[default]/File[crontab]: Failed to retrieve current > state of resource: HTTP-Error: 500 Internal Server Error Could not > describe /files/crontab: HTTP-Error: 500 Internal Server Error at / > etc/puppet/manifests/site.pp:153[0m > [0;34mdebug: Calling fileserver.describe[0m > > On my puppetmasterd server, I''m also getting a bunch of error messages > like these - which I believe are related... > notice: Denying authenticated client domu-12-31-39-00- > d9-84.compute-1.internal(67.202.55.67) access to > puppetmaster.getconfig > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > name domu-12-31-39-00-d9-84.compute-1.internal > notice: Denying authenticated client domu-12-31-39-00- > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > name domu-12-31-39-00-d9-84.compute-1.internal > notice: Denying authenticated client domu-12-31-39-00- > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > > From my understanding, authentication is working, but I don''t think > the file server or file checking mechanism is working....my > fileserver.conf settings are wide open... > > [files] > path /var/puppet/files > allow * > > As further evidence, changes in my manifests do not seem to be > propagating to the nodes. > > If any one could help me sort out these error messages and these > issues, I would greatly appreciate it. > > Thanks, > > Chadhttp://www.neomantic.com--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chad, Are you using a namespaceauth.conf file? I''ve found that this can also cause the issues you are seeing, if the file is inappropriate for your environment. - --Paul On Thu, Sep 4, 2008 at 6:44 AM, Chad A. wrote: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: http://getfiregpg.org iEYEARECAAYFAkjAQJYACgkQX6ecHn3cW4lAtQCeJb14VRNCLyP6Afo3SaR+wYkz MK4An0jsMlmg6ddGWBh4DVT/FioA/BJE =ZGaA -----END PGP SIGNATURE-----> > Hi, > > For the last couple of days, I have been banging my head against many > hard objects to solve some of my puppet setting problems, but I can''t > seem to sort it out. All my manifests appear to be correct. > > On my nodes running puppetd, I''m getting a bunch of HTTP-Error: 500 > Internal Server Errors. For examlpe > > [0;34mdebug: Calling fileserver.describe[0m > [0;33merr: Could not call fileserver.describe: #<RuntimeError: HTTP- > Error: 500 Internal Server Error >[0m > [0;33merr: //Node[default]/File[crontab]: Failed to retrieve current > state of resource: HTTP-Error: 500 Internal Server Error Could not > describe /files/crontab: HTTP-Error: 500 Internal Server Error at / > etc/puppet/manifests/site.pp:153[0m > [0;34mdebug: Calling fileserver.describe[0m > > On my puppetmasterd server, I''m also getting a bunch of error messages > like these - which I believe are related... > notice: Denying authenticated client domu-12-31-39-00- > d9-84.compute-1.internal(67.202.55.67) access to > puppetmaster.getconfig > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > name domu-12-31-39-00-d9-84.compute-1.internal > notice: Denying authenticated client domu-12-31-39-00- > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > name domu-12-31-39-00-d9-84.compute-1.internal > notice: Denying authenticated client domu-12-31-39-00- > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > > From my understanding, authentication is working, but I don''t think > the file server or file checking mechanism is working....my > fileserver.conf settings are wide open... > > [files] > path /var/puppet/files > allow * > > As further evidence, changes in my manifests do not seem to be > propagating to the nodes. > > If any one could help me sort out these error messages and these > issues, I would greatly appreciate it. > > Thanks, > > Chad > http://www.neomantic.com > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
We added that, and it didn''t make a difference. Reading http://reductivelabs.com/trac/puppet/wiki/FileServingConfiguration, I think this is correct behavior because those [*] labels define "modules" which are used elsewhere by puppet. For instance, since we are serving files from /var/puppet/files, we have a [files] label referring the "files" directory. I may be reading the documentation wrong, though. Any other ideas? Chad On Sep 4, 11:13 am, Dan Bode <bod...@gmail.com> wrote:> for fileserver auth, I am using [fileserver], not [files] and it works > fine, in the output when puppetmasterd starts, do you have the > following message: > > info: mount[fileserver]: allowing * access > > On Sep 4, 2:44 pm, "Chad A." <calb...@neomantic.com> wrote: > > > Hi, > > > For the last couple of days, I have been banging my head against many > > hard objects to solve some of my puppet setting problems, but I can''t > > seem to sort it out. All my manifests appear to be correct. > > > On my nodes running puppetd, I''m getting a bunch of HTTP-Error: 500 > > Internal Server Errors. For examlpe > > > [0;34mdebug: Calling fileserver.describe[0m > > [0;33merr: Could not call fileserver.describe: #<RuntimeError: HTTP- > > Error: 500 Internal Server Error >[0m > > [0;33merr: //Node[default]/File[crontab]: Failed to retrieve current > > state of resource: HTTP-Error: 500 Internal Server Error Could not > > describe /files/crontab: HTTP-Error: 500 Internal Server Error at / > > etc/puppet/manifests/site.pp:153[0m > > [0;34mdebug: Calling fileserver.describe[0m > > > On my puppetmasterd server, I''m also getting a bunch of error messages > > like these - which I believe are related... > > notice: Denying authenticated client domu-12-31-39-00- > > d9-84.compute-1.internal(67.202.55.67) access to > > puppetmaster.getconfig > > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > > name domu-12-31-39-00-d9-84.compute-1.internal > > notice: Denying authenticated client domu-12-31-39-00- > > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > > name domu-12-31-39-00-d9-84.compute-1.internal > > notice: Denying authenticated client domu-12-31-39-00- > > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > > > From my understanding, authentication is working, but I don''t think > > the file server or file checking mechanism is working....my > > fileserver.conf settings are wide open... > > > [files] > > path /var/puppet/files > > allow * > > > As further evidence, changes in my manifests do not seem to be > > propagating to the nodes. > > > If any one could help me sort out these error messages and these > > issues, I would greatly appreciate it. > > > Thanks, > > > Chadhttp://www.neomantic.com > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Paul, You hit the nail on the head. Yesterday, we tracked it to an updated namespaceauth.conf file. Lesson learned - don''t mess with this file unless you really understand it. Thanks for everyone''s help, Chad On Sep 4, 4:09 pm, "Paul Lathrop" <p...@tertiusfamily.net> wrote:> > Hi, > > > For the last couple of days, I have been banging my head against many > > hard objects to solve some of my puppet setting problems, but I can''t > > seem to sort it out. All my manifests appear to be correct. > > > On my nodes running puppetd, I''m getting a bunch of HTTP-Error: 500 > > Internal Server Errors. For examlpe > > > [0;34mdebug: Calling fileserver.describe[0m > > [0;33merr: Could not call fileserver.describe: #<RuntimeError: HTTP- > > Error: 500 Internal Server Error >[0m > > [0;33merr: //Node[default]/File[crontab]: Failed to retrieve current > > state of resource: HTTP-Error: 500 Internal Server Error Could not > > describe /files/crontab: HTTP-Error: 500 Internal Server Error at / > > etc/puppet/manifests/site.pp:153[0m > > [0;34mdebug: Calling fileserver.describe[0m > > > On my puppetmasterd server, I''m also getting a bunch of error messages > > like these - which I believe are related... > > notice: Denying authenticated client domu-12-31-39-00- > > d9-84.compute-1.internal(67.202.55.67) access to > > puppetmaster.getconfig > > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > > name domu-12-31-39-00-d9-84.compute-1.internal > > notice: Denying authenticated client domu-12-31-39-00- > > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > > debug: Overriding ec2-67-202-55-67.compute-1.amazonaws.com with cert > > name domu-12-31-39-00-d9-84.compute-1.internal > > notice: Denying authenticated client domu-12-31-39-00- > > d9-84.compute-1.internal(67.202.55.67) access to fileserver.describe > > > From my understanding, authentication is working, but I don''t think > > the file server or file checking mechanism is working....my > > fileserver.conf settings are wide open... > > > [files] > > path /var/puppet/files > > allow * > > > As further evidence, changes in my manifests do not seem to be > > propagating to the nodes. > > > If any one could help me sort out these error messages and these > > issues, I would greatly appreciate it. > > > Thanks, > > > Chad > >http://www.neomantic.com > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---