On 23.12.2009 01:13, Matthew Delves wrote:
> Hey All,
> I seem to be getting errors when running puppet under sles 11.
> The first weird issue I'm seeing is that the node information isn't being
> sent through to puppet correctly as It doesn't pick up the $operatingsystem
> variable correctly and instead relies on the default setting.
>
You are saying something about a default setting, I'm guessing that this
is in a case statement and it doesn't match any of the options provided.
Have you checked the actual value of the fact? One way of doing it is
warning($operatingsystem) in the manifest and check the logs on the server.
I also had some issues with distinguishing between debian and ubuntu.
> The puppet version I'm using is 0.25.1
> The ruby version I'm using is 1.8.7
>
> The puppet server is running 0.25.1
>
> I've tested this with 2 different sles 11 nodes against 2 different puppet
> servers. Both of them fail.
>
> As for the puppet server setup I currently have 4 mongrel sessions sitting
> behind an nginx proxy.
>
> By using curl to connect to the server I can get the yaml for the node,
> though when using puppetd I get the error:
> No specified acceptable formats (*/*) are functional on this machine
>
Other than that do some debug runs... Run facter and see what it
outputs. If it is somewhere in between try testing with webrick (aka run
puppetmasterd and run a client against it). Run it directly against
mongrel and see how it behaves there. This should at least point out
where is your problem.
Also try to post the complete trace/debug output as it might reveal
other interesting information.
This does not apply only to puppet:
When trying to solve a computer problem simplify it as much as you can
till you only remain with the core of the problem. In what you stated
before the culprit may be facter, puppet, mongrel, nginx proxying,
puppet server or some unknown transparent proxy on your network and with
some simple tests you could rule most of them out. While doing so you
might solve the problem by yourself. Second you haven't specified any
configs or debug traces, if anybody on the list could help you, he/she
wouldn't have the necessary info to do so. As a final note if you would
reduce your problem to say nginx proxying an nginx expert, which might
be a puppet newbie could help you, but with so many variables and
unknowns in your config he/she wouldn't be able to state that this is a
nginx problem.
Good luck,
Silviu
--
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.
