The puppet master runs as the puppet user so try 'chown -R puppet:puppet /etc/puppet /var/log/puppet /var/lib/puppet'.
- Keith
Hey all, this is my first post. I did try and search the group first before posting :)
I've been using puppet for quit some time now and decide it was time to install 3.02.. So I blew a way my old installation of 2.6 and started from scratch. So to test I have two servers running on cent os 6.3. One's to be a master and one's a client
On the client I have installed (yum install puppet)
on the master I have installed (yum install puppet and yum install puppet-server)
I kept my old puppet.conf for reference and determined that most of the configuration options are the same... ( just a basic test.. wanna run a couple modules to move files thats about it )
I have yum installed everything as root
So when I start my master.. I'm able to start the puppet agent(service puppet start).(as root) but then when I try and start the master (service puppetmaster start) (as root) it says its starts.. but then when I do a service status it states puppet dead but pid file exists.. so then I go under /var/log/messages and I See this
Starting puppet master version 3.0.2
reopening log files
Could not run: Permission denied - /var/log/puppet/masterhttpd.log
I also see this too
Starting puppet client version 3.0.2
reopening log file
failed to apply catalog connection refused - connect 2
could not send report - connect
when I check /var/log/puppet/masterhttpd.log it shows masterhttpd.log as rw -rw puppet puppet.. So naturally I do a chmod 777 on it but it doesn't make a difference.
any ideas what could be my issue? Never had anything like this on 2.6..
Thanks so much
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Try 'service puppetmaster restart' and see if you get any logs under /var/logs/puppet.
If that doesn't work try 'service puppetmaster stop', delete the pid file and then run 'service puppet master start'.
- Keith
Do the parent directories - /etc, /var, /var/log etc have 755 permissions? Perhaps the puppet user can't access one or more of these directories.
- Keith