How do I apply a manifest from a Puppet Master server to a Puppet Agent node server?
up vote
1
down vote
favorite
I installed Puppet Agent on a CentOS 7 server. I installed Puppet Master on a different CentOS 7 server. I'm using the free version of Puppet on both servers. The Puppet Agent server requested a certificate. I signed it on the Puppet Master server. There is no software firewall on either server. There is no firewall between the servers. I temporarily enabled port 8140 with SSHD. I used SSH to verify port 8140 was open. I then reverted SSHD to only listen on port 22. Port 8140 wasn't blocked. nslookup on the IP addresses and ping against the domain names shows that both servers have correct networking information about the other server. These are new servers. Puppet has never worked on them before. I created a simple manifest. I applied it to the Puppet Master server locally. It worked without errors. I then tried to apply it to the Puppet Agent server. It didn't work.
From the Puppet Master server, I ran this:
puppet agent neat.pp --server hostNameOfPuppetAgentServer --verbose
There were no errors on the Puppet Master server after I pressed enter. There was no output at all. This produced no logs on the Puppet Agent server. There was no evidence it worked on the Puppet Agent server. I checked, and the effects were not performed.
On the Puppet Master server I ran this:
puppet agent --server hostNameOfPuppetAgentServer --test
The results included "Connection refused -- connect (2)." What is wrong? I expect the manifest to work on a Puppet Agent node.
linux centos ssh networking puppet
asked Jan 20 '16 at 2:47
Kiran
133619
add a comment |
up vote
1
down vote
favorite
I installed Puppet Agent on a CentOS 7 server. I installed Puppet Master on a different CentOS 7 server. I'm using the free version of Puppet on both servers. The Puppet Agent server requested a certificate. I signed it on the Puppet Master server. There is no software firewall on either server. There is no firewall between the servers. I temporarily enabled port 8140 with SSHD. I used SSH to verify port 8140 was open. I then reverted SSHD to only listen on port 22. Port 8140 wasn't blocked. nslookup on the IP addresses and ping against the domain names shows that both servers have correct networking information about the other server. These are new servers. Puppet has never worked on them before. I created a simple manifest. I applied it to the Puppet Master server locally. It worked without errors. I then tried to apply it to the Puppet Agent server. It didn't work.
From the Puppet Master server, I ran this:
puppet agent neat.pp --server hostNameOfPuppetAgentServer --verbose
There were no errors on the Puppet Master server after I pressed enter. There was no output at all. This produced no logs on the Puppet Agent server. There was no evidence it worked on the Puppet Agent server. I checked, and the effects were not performed.
On the Puppet Master server I ran this:
puppet agent --server hostNameOfPuppetAgentServer --test
The results included "Connection refused -- connect (2)." What is wrong? I expect the manifest to work on a Puppet Agent node.
linux centos ssh networking puppet
asked Jan 20 '16 at 2:47
Kiran
133619
Puppet Master server does not push rules to the slaves, but its the slave that pulls the rules from the master. You go have to start the Puppet Agent daemon on the puppet slaves, not on the master.
– haxxor
Jan 20 '16 at 5:14
run ` puppet agent --server <puppet-master> --test` on your puppet agent. Not on your puppet master.
– Siddharth sharma
Jan 20 '16 at 6:37
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I installed Puppet Agent on a CentOS 7 server. I installed Puppet Master on a different CentOS 7 server. I'm using the free version of Puppet on both servers. The Puppet Agent server requested a certificate. I signed it on the Puppet Master server. There is no software firewall on either server. There is no firewall between the servers. I temporarily enabled port 8140 with SSHD. I used SSH to verify port 8140 was open. I then reverted SSHD to only listen on port 22. Port 8140 wasn't blocked. nslookup on the IP addresses and ping against the domain names shows that both servers have correct networking information about the other server. These are new servers. Puppet has never worked on them before. I created a simple manifest. I applied it to the Puppet Master server locally. It worked without errors. I then tried to apply it to the Puppet Agent server. It didn't work.
From the Puppet Master server, I ran this:
puppet agent neat.pp --server hostNameOfPuppetAgentServer --verbose
There were no errors on the Puppet Master server after I pressed enter. There was no output at all. This produced no logs on the Puppet Agent server. There was no evidence it worked on the Puppet Agent server. I checked, and the effects were not performed.
On the Puppet Master server I ran this:
puppet agent --server hostNameOfPuppetAgentServer --test
The results included "Connection refused -- connect (2)." What is wrong? I expect the manifest to work on a Puppet Agent node.
linux centos ssh networking puppet
asked Jan 20 '16 at 2:47
Kiran
133619
I installed Puppet Agent on a CentOS 7 server. I installed Puppet Master on a different CentOS 7 server. I'm using the free version of Puppet on both servers. The Puppet Agent server requested a certificate. I signed it on the Puppet Master server. There is no software firewall on either server. There is no firewall between the servers. I temporarily enabled port 8140 with SSHD. I used SSH to verify port 8140 was open. I then reverted SSHD to only listen on port 22. Port 8140 wasn't blocked. nslookup on the IP addresses and ping against the domain names shows that both servers have correct networking information about the other server. These are new servers. Puppet has never worked on them before. I created a simple manifest. I applied it to the Puppet Master server locally. It worked without errors. I then tried to apply it to the Puppet Agent server. It didn't work.
From the Puppet Master server, I ran this:
puppet agent neat.pp --server hostNameOfPuppetAgentServer --verbose
There were no errors on the Puppet Master server after I pressed enter. There was no output at all. This produced no logs on the Puppet Agent server. There was no evidence it worked on the Puppet Agent server. I checked, and the effects were not performed.
On the Puppet Master server I ran this:
puppet agent --server hostNameOfPuppetAgentServer --test
The results included "Connection refused -- connect (2)." What is wrong? I expect the manifest to work on a Puppet Agent node.
linux centos ssh networking puppet
linux centos ssh networking puppet
asked Jan 20 '16 at 2:47
Kiran
133619
asked Jan 20 '16 at 2:47
Kiran
133619
asked Jan 20 '16 at 2:47
Kiran
133619
asked Jan 20 '16 at 2:47
Kiran
133619
asked Jan 20 '16 at 2:47
Kiran
133619
133619
Puppet Master server does not push rules to the slaves, but its the slave that pulls the rules from the master. You go have to start the Puppet Agent daemon on the puppet slaves, not on the master.
– haxxor
Jan 20 '16 at 5:14
run ` puppet agent --server <puppet-master> --test` on your puppet agent. Not on your puppet master.
– Siddharth sharma
Jan 20 '16 at 6:37
add a comment |
Puppet Master server does not push rules to the slaves, but its the slave that pulls the rules from the master. You go have to start the Puppet Agent daemon on the puppet slaves, not on the master.
– haxxor
Jan 20 '16 at 5:14
run ` puppet agent --server <puppet-master> --test` on your puppet agent. Not on your puppet master.
– Siddharth sharma
Jan 20 '16 at 6:37
Puppet Master server does not push rules to the slaves, but its the slave that pulls the rules from the master. You go have to start the Puppet Agent daemon on the puppet slaves, not on the master.
– haxxor
Jan 20 '16 at 5:14
Puppet Master server does not push rules to the slaves, but its the slave that pulls the rules from the master. You go have to start the Puppet Agent daemon on the puppet slaves, not on the master.
– haxxor
Jan 20 '16 at 5:14
run ` puppet agent --server <puppet-master> --test` on your puppet agent. Not on your puppet master.
– Siddharth sharma
Jan 20 '16 at 6:37
run ` puppet agent --server <puppet-master> --test` on your puppet agent. Not on your puppet master.
– Siddharth sharma
Jan 20 '16 at 6:37
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
On your puppet client, edit puppet.conf [main] section include server = <puppet_server_name>.
And try run puppet agent -t .
answered Jan 20 '16 at 5:21
Muralibabud
843
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
On your puppet client, edit puppet.conf [main] section include server = <puppet_server_name>.
And try run puppet agent -t .
answered Jan 20 '16 at 5:21
Muralibabud
843
add a comment |
up vote
0
down vote
On your puppet client, edit puppet.conf [main] section include server = <puppet_server_name>.
And try run puppet agent -t .
answered Jan 20 '16 at 5:21
Muralibabud
843
add a comment |
up vote
0
down vote
up vote
0
down vote
On your puppet client, edit puppet.conf [main] section include server = <puppet_server_name>.
And try run puppet agent -t .
answered Jan 20 '16 at 5:21
Muralibabud
843
On your puppet client, edit puppet.conf [main] section include server = <puppet_server_name>.
And try run puppet agent -t .
answered Jan 20 '16 at 5:21
Muralibabud
843
answered Jan 20 '16 at 5:21
Muralibabud
843
answered Jan 20 '16 at 5:21
Muralibabud
843
answered Jan 20 '16 at 5:21
Muralibabud
843
843
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f256450%2fhow-do-i-apply-a-manifest-from-a-puppet-master-server-to-a-puppet-agent-node-ser%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Puppet Master server does not push rules to the slaves, but its the slave that pulls the rules from the master. You go have to start the Puppet Agent daemon on the puppet slaves, not on the master.
– haxxor
Jan 20 '16 at 5:14
run ` puppet agent --server <puppet-master> --test` on your puppet agent. Not on your puppet master.
– Siddharth sharma
Jan 20 '16 at 6:37