I'm using Puppet Opensource 4.6.1 with MCollective 2.9.0. I need to trigger the Puppet agent from the Puppet Master. However, I'm unable to find the puppet runonce command. Was this command deprecated, or is there a new command to trigger the Puppet agent from the puppet master.
using Latest puppet opensource 2.6.0 and Mcollective 2.9.0
Related
I am trying to install Eclipse Hono using Helm and have the latest Helm version 3.3.0 installed in the system. I tried to follow the instructions from here - https://github.com/eclipse/packages/tree/master/charts/hono
I created the hono namespace with command -
minikube kubectl create namespace hono
And then tried to install hono with this command -
helm install --dependency-update -n hono eclipse-hono eclipse-iot/hono
but I got this error -
Error: failed to download "eclipse-iot/hono" (hint: running helm repo update may help)
I had searched for solutions related to this error and read that the chart repository should be added first. what is the name of the chart repository for eclipse hono?
Basically I want to know what I could be missing so that hono can be installed on my system or if there is an alternate method to install hono successfully on my local system. I have minikube version: v1.12.3 and windows version 10
You should follow the instructions provided on the IoT Packages project page.
After that you should do a helm repo update. The helm install command should then be able to download the chart successfully.
When trying to run the following command from puppet agent node:
puppet agent --test --verbose
The following error was prompted
Error: certificate verify failed [unable to get local issuer certificate for CN=puppetmaster.example.com]
I have already added FQDN to my hosts in /etc/hosts file.
I deleted the SSL folder in puppet directory and everything worked fine then after.
rm -rf /etc/puppetlabs/puppet/ssl/
puppet agent --test --verbose
You can check your logs using the command
journalctl -u puppet
I went round in circles on this - i was using the standard Ubuntu repo and just installed puppet on my client machines....
My docker puppetmaster is running 6.14 but the agent I pulled from standard Ubuntu world was version 5. The bellow as I am sure you will know will add puppetlabs to your repos and then install the upto date version 6 agent.
wget https://apt.puppetlabs.com/puppet6-release-bionic.deb
sudo dpkg -i puppet6-release-bionic.deb
sudo apt update
sudo apt install puppet-agent
All the answers I have seen to any puppet cerficate type errors just say regenerate your certificate and I could find nothing that offered any further help.
I would suggest check your server and client versions match after my experiance!
To add to #shubham-singh answer, on some system the ssl directory may not be in /etc/puppetlabs/puppet/.
You can run:
sudo find / -name puppet.conf
to find puppet.conf file and look for the value of ssldir property in puppet.conf and then delete/rename the ssl directory and rerun:
puppet agent --test
The rerun may give you error and ask to run additional commands at server and agent to clear the certificate.
Follow the commands and then rerun:
puppet agent --test
and it should work now.
Edit:
If you are still having issue, it may be due to different versions of puppet on server and agent. Check the puppet version using below command on master and agent and make sure the versions are matching.
puppet --version
I was trying to install puppet 5(opensource) set up in ubuntu 18(bionic) machines.
But i cannot see puppetserver package available in ubuntu 18 repo and can see puppet-master package.As per puppet documentation puppet master is deprecated.Still i can add the puppet repo and install puppetserver.
1.Is there any reason why ubuntu repo is not having puppetserver package.
2.Can i use puppet-master instead of puppetserver for puppet 5.
yeah I had the same issue and answering to your questions below:
.Is there any reason why ubuntu repo is not having puppetserver package. It is having the package puppetserver on Ubuntu 18 LTS bionic :
root#test-l1-ubuntu1804:~# cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
root#test-l1-ubuntu1804:~# apt-cache search puppetserver
puppetserver - Puppet Labs puppetserver. Contains: Puppet Server (puppetlabs/puppetserver 6.2.1,org.clojure/clojure 1.10.0,org.clojure/clojurescript 1.10.238,puppetlabs/puppetserver 6.2.1,puppetlabs/trapperkeeper-webserver-jetty9 2.3.1)
root#test-l1-ubuntu1804:~#
The trick is to enable the universe repository althought you have it in your /etc/apt/source.list with sudo add-apt-repository universe
Can i use puppet-master instead of puppetserver for puppet 5 . Yes you can use the package puppet-master.. I am using it :)
#John Bollinger - for everything is a documentation so if you do not help then why comment what you do not know
I believe that puppetserver is the puppetlabs version and puppetmaster is the apache/passenger version of puppet. I prefer working with puppetlabs, but it is not part of the standard ubuntu repo. We have to wget the puppetlabs package, install the deb with dpkg and do an apt update for all machines to get the puppetlabs repo. However puppetmaster will work fine too.
I'm trying to install puppet-server 3.8.7.
The problem is that the puppet-server automatically requires puppet, that requires puppet-agent, who supplies me only the newest version that fits puppet 4.x only (puppet-agent-1.5.2).
The
"yum install puppet-server"
Failed .
What can i do?
I use vagrant 1.0.1 on a precise32 base box to play with puppet.
Provisioning works fine, my manifests are being executed.
By default vagrant installs puppet 2.7.14 under /opt/vagrant_ruby/bin/puppet on the guest.
How can I configure vagrant (or who ever installs puppet on the guest) to use a more recent version like puppet 3.0 or 3.1?
Also you could update puppet with shell provisioner specified before puppet provisioner. As said in Vagrant documentation:
Multiple config.vm.provision methods can be used to define multiple provisioners. These provisioners will be run in the order they're defined. This is useful for a variety of reasons, but most commonly it is used so that a shell script can bootstrap some of the system so that another provisioner can take over later.
Here is example Vagrantfile for CentOS 6:
# Update puppet to version 3.2.2 before using puppet provisioning.
$puppet_update_script = <<SCRIPT
[ `rpm -qa puppetlabs-release` = 'puppetlabs-release-6-7.noarch' ] || rpm -ivh http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-7.noarch.rpm
[ `rpm -qa puppet` = 'puppet-3.2.2-1.el6.noarch' ] || yum -y update-to puppet-3.2.2
SCRIPT
config.vm.provision :shell, :inline => $puppet_update_script
# Puppet-3.2.2 provisioning here
config.vm.provision :puppet do |puppet|
puppet.options = '--parser future'
puppet.manifests_path = 'puppet/manifests'
end
You need to rebuild the basebox that you are using in vagrant and install whatever version of Puppet you want. I did the same for Cent 6.3 w/puppet 3.0. The Veewee gem is a great utility to building and managing Vagrant baseboxes for Oracle Virtualbox.