Issue #2889 has been updated by Nicholas Veeser.
So I did some digging in case anyone cares. I am curious because my namespaceauth.conf file is wrong and I would like to fix it, but debugging the parsing of it is becoming difficult. Here is my description so far, correct as necessary: --- Using Webrick, we have Puppet::Network::XMLRPC::WEBrickServlet It "include"s Puppet::Network::XMLRPCProcessor which "include"s Puppet::Network::Authorization (I understand what ruby does mechanically here, but I am not sure how to talk about it in OO terms I can say "The WEBrickServlet is now also a XMLRPCProcessor. Is it also an "Authorization") Request comes in, sent to Puppet::Network::XMLRPCProcessor.process(data, request) That calls verify(request). This looks up the authconfig member, which uses the "initialize object on first call" pattern (better name?). This presumably loads and parses the namespaceconfig.conf file. Which has a parse error and throws an exception. Well the XMLProcessor is not expecting any config parsing to be going on, so it ignores the exception, which (I believe) that Webrick just catches and turns into an undefined 500 Server error. --- Seems like the problem is that Puppet::Network::Authorization needs to be initialized at some point. Idealy for me, the user, somewhere before it starts taking requests. That way it can tell me I did something foolish with my ns.conf file and tell me what and where. However it's a Module so I don't know the expected ruby like pattern to initialize a Module. Isn't this an error that should come out on the server side, at initialization, not the client side as a response. That is, I would expect the webrick daemon not to start if the file is there and not valid. I am experimenting with patches...and looking for guidance. ---------------------------------------- Bug #2889: puppetrun gives error 500 with no explanation http://projects.reductivelabs.com/issues/2889 Author: Alex Urbanowicz Status: Needs design decision Priority: Low Assigned to: James Turnbull Category: Target version: Affected version: 0.24.8 Keywords: puppetrun 500 Branch: Hello! We have problem using puppetrun: [r...@stonka alex]# puppetrun --trace --debug --host hostname.fqdn debug: Parsing /etc/puppet/puppet.conf debug: Puppet::Network::Client::Runner: defining puppetrunner.run Triggering hostname.fqdn debug: Calling puppetrunner.run err: Could not call puppetrunner.run: #<RuntimeError: HTTP-Error: 500 Internal Server Error > Host hostname.fqdn failed: HTTP-Error: 500 Internal Server Error hostname.fqdn finished with exit code 2 Failed: hostname.fqdn on the puppet the --trace --debug --verbose log looks as follows: Dec 4 18:06:57 hostname puppetd[30452]: (access[fileserver]) allowing puppet.fqdn access namespaceauth.conf contents is: [fileserver] allow puppet.fqdn [puppetmaster] allow puppet.fqdn [puppetrunner] allow *.fqdn [puppetbucket] allow *.fqdn [puppetreports] allow puppet.fqdn [resource] allow puppet.fqdn Strace gives unconclusive results. I suspect the problem is somewhat related to the network setup (the puppet I try to trigger has no access to reverse dns of the fqdn domain, and uses /etc/hosts lookups) but I found no way to confirm this. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
