zsy12
September 16, 2021, 11:22am
#1
Problem: when I click "puppetrun " report error exexute puppetrun ([RestClient::InternalServerError]:500 Internal Server Error) proxyserver https://dc.dc.com:8443/puppet
Expected outcome:
**Foreman and Proxy versions:**2.0
**Foreman and Proxy plugin versions:**2.0
Distribution and version:
Other relevant data:
Do I need to modify the configuration file to enable the function of puppetrun
Did you have a look at the new documentation Using Puppet for Configuration Management ?
Also, Foreman 2.0 is no longer supported. Would you consider updating to Foreman 2.5 or later?
Can you check /var/log/foreman/production.log
to see what happens when you click Run Puppet Once ?
1 Like
zsy12
September 17, 2021, 9:36am
#3
I didn’t see the error message in the log.What’s going on
ekohl
September 17, 2021, 10:50am
#4
The Puppetrun feature is removed in currently supported versions. It’s important to realize that puppetrun (renamed to puppet kick in Puppet 3) was removed in Puppet 4. I wouldn’t spend my time in getting it to work. Instead, focus on getting remote execution set up as a replacement.
zsy12
September 17, 2021, 11:32am
#5
But when I execute puppet kick, I report an error.
zsy12
September 17, 2021, 11:37am
#6
I execute on the client puppet kick -p 10 --host dc.sc.com
Error :Host dc.sc.com failed:Connection refused -connect (2)