Bug #2781
closed
Importing classes - Permission denied - /var/lib/puppet/ssl/private_keys/name.pem
Description
Hi
I get the following exceptions when trying to import puppet classes from a new puppetmaster / foreman-proxy. The pem above is actually the foreman pem that is in the exception. All other puppetmaster continue to work just fine. Full exception is:
Errno::EACCES
Permission denied - /var/lib/puppet/ssl/private_keys/name.pem
lib/proxy_api.rb:25:in `read'
lib/proxy_api.rb:25:in `initialize'
lib/proxy_api.rb:97:in `initialize'
app/models/puppet_class_importer.rb:9:in `new'
app/models/puppet_class_importer.rb:9:in `initialize'
lib/foreman/controller/environments.rb:8:in `new'
lib/foreman/controller/environments.rb:8:in `import_environments'
lib/foreman/thread_session.rb:31:in `clear_thread'
Updated by Lukas Zapletal almost 11 years ago
- Priority changed from Urgent to Normal
- Target version deleted (
1.2.1)
Hello,
this might be permissions problem. Can you do
- ll /var/lib/puppet/ssl/private_keys/name.pem
- ps axu | grep foreman
- ps axu | grep smart
Updated by Dominic Cleal almost 11 years ago
- Status changed from New to Need more information
Also check the 'foreman' user is part of the 'puppet' group and ls -ld /var/lib/puppet/ssl/private_keys.
Updated by John Julien about 10 years ago
The only time I received this error was when I was trying to add the foreman url as a smart proxy. I went to the extent of making the file world readable and still received the error.
So, my foreman server was running at https://foreman.example.com/ and I wanted to import my puppet classes for which a proxy is required, so I tried to add https://foreman.example.com/ as a smart-proxy.
Updated by Tomer Brisker about 8 years ago
- Status changed from Need more information to Rejected
No action in over 2 years. Assuming this issue was solved - apparently some permissions needed tweaking. Closing.