On Dec 7, 4:31 pm, Mark_SysAdm <[email protected]> wrote: > James, > I haven't heard anything back from the list. The only workaround I > found was to try installing puppet-server on exactly the same OS, but > on a freshly-installed server. Puppet starts without a problem! So > maybe we have some competing packages/RPMs added to the original > system, which is of course the one Puppet really needs to run on. > > Thanks, > Mark > > ---- > from: James M. > > Hello, > > I'm running into the same error as you described in a post to the > puppet mailing list, though I'm running on RHEL 5.6. I was wondering > if you had discovered a fix. > > Starting puppetmaster: > /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > `gem_original_require': no such file to load -- puppet/network/server > (LoadError) > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: > 31:in `require' > from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb: > 191:in `main' > from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb: > 144:in > `run_command' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:307:in > `run' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:411:in > `hook' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:307:in > `run' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:402:in > `exit_on_fail' > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:307:in > `run' > from /usr/sbin/puppetmasterd:4 > [FAILED] > > Cheers, > > James > > On Nov 30, 9:35 am, Mark_SysAdm wrote: > > > > > Hi, > > On RHEL6, no matter which version of puppet installed, I can not start > > the puppetmaster service: > > > service puppetmaster restart > > Stopping puppetmaster: [FAILED]
I strongly recommend avoiding using gem to manage modules in a ruby library itself managed by RPM. You will cause yourself grief. I'm not certain that is your present problem, but I do find it highly suspcious that the error is arising in /usr/lib/ruby/site_ruby/1.8/ rubygems/custom_require.rb. Is it possible that you once installed Puppet as a gem, then switched to an RPM version? If so, then perhaps the system is still trying to start the gem version. It could be looking for the supposedly missing file under your rubygems directory. In that case, I'm not sure offhand what you would need to do to fix the problem. I would think that a complete Ruby wipe / reinstall would do the trick, but surely there is a lower-impact solution. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
