Here is my config.ru by the way... checking to make sure it is correct...
# This file is mostly based on puppetmasterd, which is part of
# the standard puppet distribution.
require 'rack'
require 'puppet'
require 'puppet/network/http_server/rack'
# startup code stolen from bin/puppetmasterd
Puppet.parse_config
Puppet::Util::Log.level = :info
Puppet::Util::Log.newdestination(:syslog)
# A temporary solution, to at least make the master work for now.
Puppet::Node::Facts.terminus_class = :yaml
# Cache our nodes in yaml. Currently not configurable.
Puppet::Node.cache_class = :yaml
# The list of handlers running inside this puppetmaster
handlers = {
:Status => {},
:FileServer => {},
:Master => {},
:CA => {},
:FileBucket => {},
:Report => {}
}
# Fire up the Rack-Server instance
server = Puppet::Network::HTTPServer::Rack.new(handlers)
# prepare the rack app
app = proc do |env|
server.process(env)
end
# Go.
run app
On Thu, Jan 26, 2012 at 10:19 AM, Peter Berghold <salty.cowd...@gmail.com>wrote:
> Based on what Nigel said I checked my auth.conf file lo and behold it was
> MIA. Don't know why but I created a new one at any rate and tried again.
> Still getting errors, but they are at least different errors.
>
> Looking in the apache2 log I find an intriguing error:
>
> from config.ru:1
> [ pid=7913 thr=70073891451320 file=utils.rb:176 time=2012-01-26 15:03:21.940
> ]: *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner
> (no such file to load -- puppet/network/http_server/rack) (process 7913,
> thread #<Thread:0x7f76b2d0e370>):
>
> I checked the directory
>
>
> /usr/lib/ruby/gems/1.8/doc/puppet-2.7.9/rdoc/files/lib/puppet/network/http_server
>
> and checked its contents and found there was no rack.rb in there. Where
> should this come from?
>
>
>
> On Wed, Jan 25, 2012 at 7:02 PM, Nan Liu <n...@puppetlabs.com> wrote:
>
>> I ran into the same error briefly on RHEL 6 with Puppet 2.7.9. After
>> downgrading to 2.7.8 master, everything works as expected. There's so
>> few difference when running git diff 2.7.8..2.7.9, I can't see what
>> could possibly cause this bug. And in the process of trying to confirm
>> the bug and upgrading it again to 2.7.9 it went away. I have to stand
>> up a few more masters and I'll dig into this a bit more if I can
>> repeat it.
>>
>> Thanks,
>>
>> Nan
>>
>> On Wed, Jan 25, 2012 at 4:57 PM, Peter Berghold <salty.cowd...@gmail.com>
>> wrote:
>> > Just for completeness:
>> >
>> > # type --all puppet{,d,masterd}
>> > puppet is /usr/bin/puppet
>> > puppetd is /usr/bin/puppetd
>> > puppetmasterd is /usr/bin/puppetmasterd
>> >
>> > # puppet --version
>> > 2.7.9
>> >
>> >
>> > # puppetd --version
>> > 2.7.9
>> >
>> > # puppetmasterd --version
>> > 2.7.9
>> >
>> > On Wed, Jan 25, 2012 at 4:37 PM, Peter Berghold <
>> salty.cowd...@gmail.com>
>> > wrote:
>> >>
>> >> There is only one version of puppet (agent and master) on the system.
>> This
>> >> system was installed from bare metal this morning.
>> >>
>> >> On Jan 25, 2012 4:24 PM, "Nigel Kersten" <ni...@puppetlabs.com> wrote:
>> >>
>> >> do you have multiple versions of puppet installed?
>> >>
>> >> If you're in bash:
>> >>
>> >> $ type --all puppet{,d,masterd}
>> >>
>> >> Do you get different versions returned for:
>> >>
>> >> $ puppet --version
>> >> $ puppetd --version
>> >>
>> >>
>> >> On newer installs you should be using "puppet agent" instead of
>> "puppetd"
>> >> (We moved to git-style subcommands a while ago)
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Jan 25, 2012 at 1:03 PM, Peter Berghold <
>> salty.cowd...@gmail.com>
>> >> wrote:
>> >> >
>> >> > master and ...
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups
>> >> "Puppet Users" group.
>> >> ...
>> >
>> >
>> >
>> >
>> > --
>> > Peter L. Berghold
>> > Owner, Shark River Technical Solutions LLC
>> >
>> > --
>> > 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+unsubscr...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/puppet-users?hl=en.
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>
>
> --
> Peter L. Berghold
> Owner, Shark River Technical Solutions LLC
>
--
Peter L. Berghold
Owner, Shark River Technical Solutions LLC
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
