Bug #3121

Issues running puppetmasterd as a genetic user

Added by Steven Ellis over 2 years ago. Updated over 2 years ago.

Status:Rejected Start date:01/28/2010
Priority:Normal Due date:
Assignee:Markus Roberts % Done:

0%

Category:-
Target version:-
Affected Puppet version:0.25.3 Branch:
Keywords:
Votes: 0

Description

To speed debugging of rules I want to run puppetmasterd under my own userid so that it has access to my SVN tree’s containing my recipes as well as my files/templates.

Under ~/.puppet I have created a puppet.conf to override default locations.

Started puppermasterd some of these values are not being picked up.

I’m running puppet-server-0.25.3-2.el5 from the epel repository on Centos 5.4 64bit.

puppet.conf - Puppet configuration file (2.1 kB) Steven Ellis, 01/28/2010 03:27 am

genconfig.conf (32.6 kB) Steven Ellis, 01/28/2010 03:29 am

History

Updated by Steven Ellis over 2 years ago

I’ve also run

puppetmaster genconfig --config=/home/stevene/.puppet/puppet.conf --confdir=/home/stevene/.puppet > genconfig.conf

See attached output

Updated by Steven Ellis over 2 years ago

Trying a run as a local non-system user.

puppetmasterd --no-daemonize --debug --trace --config=/home/stevene/.puppet/puppet.conf --confdir=/home/stevene/.puppet/ --verbose

/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:929:in `parse_file'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:892:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:892:in `parse_file'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:334:in `unsafe_parse'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:326:in `parse'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:325:in `parse'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:215:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:215:in `run'
/usr/sbin/puppetmasterd:66
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/puppet/lib]: Autorequiring File[/var/puppet]
debug: /File[/var/puppet/yaml]: Autorequiring File[/var/puppet]
debug: /File[/var/puppet/run]: Autorequiring File[/var/puppet]
debug: /File[/home/stevene/.puppet/manifests]: Autorequiring File[/home/stevene/.puppet]
debug: /File[/var/puppet/rrd]: Autorequiring File[/var/puppet]
debug: /File[/var/puppet/reports]: Autorequiring File[/var/puppet]
debug: /File[/home/stevene/.puppet/ssl/certificate_requests]: Autorequiring File[/home/stevene/.puppet/ssl]
debug: /File[/var/puppet/facts]: Autorequiring File[/var/puppet]
debug: /File[/home/stevene/.puppet/ssl/private]: Autorequiring File[/home/stevene/.puppet/ssl]
debug: /File[/home/stevene/.puppet/fileserver.conf]: Autorequiring File[/home/stevene/.puppet]
debug: /File[/home/stevene/.puppet/ssl]: Autorequiring File[/home/stevene/.puppet]
debug: /File[/var/puppet/bucket]: Autorequiring File[/var/puppet]
debug: /File[/home/stevene/.puppet/ssl/public_keys/puppetserver.pem]: Autorequiring File[/home/stevene/.puppet/ssl/public_keys]
debug: /File[/home/stevene/.puppet/ssl/certs]: Autorequiring File[/home/stevene/.puppet/ssl]
debug: /File[/var/puppet/state]: Autorequiring File[/var/puppet]
debug: /File[/home/stevene/.puppet/manifests/site.pp]: Autorequiring File[/home/stevene/.puppet/manifests]
debug: /File[/home/stevene/.puppet/ssl/certs/puppetserver.pem]: Autorequiring File[/home/stevene/.puppet/ssl/certs]
debug: /File[/var/puppet/log]: Autorequiring File[/var/puppet]
debug: /File[/home/stevene/.puppet/ssl/certs/ca.pem]: Autorequiring File[/home/stevene/.puppet/ssl/certs]
debug: /File[/home/stevene/.puppet/auth.conf]: Autorequiring File[/home/stevene/.puppet]
debug: /File[/home/stevene/.puppet/ssl/private_keys]: Autorequiring File[/home/stevene/.puppet/ssl]
debug: /File[/home/stevene/.puppet/ssl/public_keys]: Autorequiring File[/home/stevene/.puppet/ssl]
debug: /File[/var/puppet/log/masterhttp.log]: Autorequiring File[/var/puppet/log]
debug: /File[/home/stevene/.puppet/ssl/private_keys/puppetserver.pem]: Autorequiring File[/home/stevene/.puppet/ssl/private_keys]
debug: /File[/home/stevene/.puppet/puppet.conf]: Autorequiring File[/home/stevene/.puppet]
debug: Finishing transaction 23866204758080 with 0 changes
debug: /File[/home/stevene/.puppet/ssl/ca/inventory.txt]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: /File[/home/stevene/.puppet/ssl/ca/requests]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: /File[/home/stevene/.puppet/ssl/ca/ca_crl.pem]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: /File[/home/stevene/.puppet/ssl/ca/ca_key.pem]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: /File[/home/stevene/.puppet/ssl/ca/private]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: /File[/home/stevene/.puppet/ssl/ca/serial]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: /File[/home/stevene/.puppet/ssl/ca/ca_crt.pem]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: /File[/home/stevene/.puppet/ssl/ca/private/ca.pass]: Autorequiring File[/home/stevene/.puppet/ssl/ca/private]
debug: /File[/home/stevene/.puppet/ssl/ca/signed]: Autorequiring File[/home/stevene/.puppet/ssl/ca]
debug: Finishing transaction 23866234777400 with 0 changes
debug: Using cached certificate for ca, good until Sun Jan 25 03:17:10 UTC 2015
debug: Using cached certificate for ca, good until Sun Jan 25 03:17:10 UTC 2015
debug: Using cached certificate for puppetserver, good until Mon Jan 26 02:17:29 UTC 2015
notice: Starting Puppet server version 0.25.3
/usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `initialize': Permission denied - /var/puppet/run/puppetmasterd.pid (Errno::EACCES)
    from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `open'
    from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `lock'
    from /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:46:in `create_pidfile'
    from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
    from /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:45:in `create_pidfile'
    from /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:124:in `start'
    from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb:122:in `main'
    from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send'
    from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command'
    from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
    from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail'
    from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
    from /usr/sbin/puppetmasterd:66

Based on the config it shouldn’t be using /var/puppet/run for the pid file.

The generated config from running @puppetmaster genconfig@ also shows that some of the variables aren’t being picked up from the configuration file correctly.

Updated by Markus Roberts over 2 years ago

  • Status changed from Unreviewed to Investigating
  • Assignee set to Markus Roberts

If you get a chance, could you try testing with 0.25.4rc3 to see if the problem still exists?

I’m also going to try to replicate.

Updated by Markus Roberts over 2 years ago

  • Status changed from Investigating to Rejected

The problem is that your puppet.conf file is malformed (probably the “user stevene” line, but there may be other issues). If you look at the start of the output you provided, you’ll see part of the stack trace where it failed parsing your settings. Shortly before the part you quoted you should see information about the line(s) that it choked on.

— Markus

Updated by Steven Ellis over 2 years ago

Thanks Markus.

Confirmed it was the “user stevene” line which should have been “user = stevene”.

Also available in: Atom PDF