On 16 June 2010 10:13, Nigel Kersten <nig...@google.com> wrote:
>
>
> On Tue, Jun 15, 2010 at 4:13 PM, Eric Sorenson <eric.soren...@me.com> wrote:
>>
>> I have seen this too; I suspect (but have not been able to reduce a simple
>> test case to confirm) that the ruby-openssl bindings in snow leopard are
>> returning EINVAL (thus the "Invalid argument" string) when called from
>> puppet. But it seems the transaction actually succeeds despite the error.
>> When setting up new puppetd on 10.6.x I see this error at each stage of the
>> certificate generation process: key generation, csr generation, cert
>> submission, but re-running after the error bulls it through. This matches
>> what you show with the revocation, where you got an error message but the
>> cert actually was revoked.  Very odd and I would love a way to isolate this
>> outside of puppet and report it to the relevant people as it seems to affect
>> all flavours of 10.6 release thus far.
>
> oh, now this sounds familiar...
> I think I ran into a similar issue on Snow Leopard, and it was reasonably
> obvious working out what went wrong by running ruby in debug mode like
> /usr/bin/ruby --debug /path/to/puppetfoo whatever you're doing
> as that way you were avoiding puppet trapping exceptions and re-raising them
> incorrectly.

OK, I've run it in debug mode, with /opt/local/bin/ruby though as I
haven't installed puppet in the system's ruby. Full output is in this
pastie: http://pastie.org/1006381 ... It has lots of Exception lines,
which I don't know what to make of! Many of the latter ones feature
'invalid value for Integer: "puppet"' which seems a bit suspect, eg:

Exception `ArgumentError' at
/opt/local/lib/ruby/site_ruby/1.8/puppet/type/file/owner.rb:56 -
invalid value for Integer: "puppet"
Exception `ArgumentError' at
/opt/local/lib/ruby/site_ruby/1.8/puppet/util/posix.rb:117 - invalid
value for Integer: "puppet"
...
Exception `ArgumentError' at
/opt/local/lib/ruby/site_ruby/1.8/puppet/util/posix.rb:94 - invalid
value for Integer: "puppet"


Some other exceptions:

Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems.rb:1113 - no such file to
load -- rubygems/defaults/operating_system
Exception `NoMethodError' at /opt/local/lib/ruby/1.8/rational.rb:78 -
undefined method `gcd' for Rational(1, 2):Rational
Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/config_file.rb:34 - no
such file to load -- Win32API

Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:31 - no
such file to load -- active_record

Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:38 - no
such file to load -- Win32API

Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:31 - no
such file to load -- selinux

Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:31 - no
such file to load -- shadow
Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:38 - no
such file to load -- shadow

Exception `ArgumentError' at /opt/local/lib/ruby/1.8/open-uri.rb:32 -
illegal access mode 80

Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:31 - no
such file to load -- puppet/provider/confine/operatingsystem
Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:38 - no
such file to load -- puppet/provider/confine/operatingsystem
Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:31 - no
such file to load -- ldap
Exception `LoadError' at
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:38 - no
such file to load -- ldap

I take it most of these are fine and being handled by puppet or lower
down subsystesms.

> I probably won't have time to look at it soon if we bug report it, as I'm
> heading back to Australia (hopefully will drop by and visit Jesse :) ) at
> the end of the week for 5 weeks vacation.

Hope to catch up with you in person Nigel :-)

Cheers
Jesse

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.

Reply via email to