stefanero
2011-Mar-23 16:46 UTC
[Puppet Users] Could not run Puppet configuration client: SIGQUIT
Hello,
I am farly new to puppet and wanted to start configure a couple of my
servers.
I started to write a little test manifest and tryed to update the
puppet client configuration as a test.
This is my site.pp
-----------------------------------------------------------------------------
#set fileserver to get files from
$fileserver = "puppet.hugoboss.com"
#import different manifets / modules get loaded by default
import "puppetclient.pp"
# all hosts get these actions
node default {
include puppetclient
}
-----------------------------------------------------------------------------
and this is the included puppetclient.pp
cat puppetclient.pp
-----------------------------------------------------------------------------
#create puppet directory for loggin etc, this is default for all
clients
#also copy our puppet config files first, when done restart service
and continoue
class puppetclient {
package {
facter:
ensure => installed;
puppet:
ensure => installed;
}
file {
"/var/lib/puppet":
ensure => directory,
owner => "puppet",
group => "puppet",
mode => 0644;
"puppet.conf":
owner => "root",
path => "/etc/puppet/puppet.conf",
source => "puppet://$fileserver/files/puppet-agent.conf";
"auth.conf":
owner => "root",
path => "/etc/puppet/auth.conf",
source => "puppet://$fileserver/files/auth-agent.conf";
"namespaceauth.conf":
owner => "root",
path => "/etc/puppet/namespaceauth.conf",
source => "puppet://$fileserver/files/namespaceauth-agent.conf";
}
service {
puppet:
ensure => true,
enable => true,
subscribe => [File["puppet.conf"], File["auth.conf"],
File["namespaceauth.conf"], Package[puppet] ]
}
}
-----------------------------------------------------------------------------
As you can tell, I guess nothing special.
All files get transfered to the client, but when I change a file for
example the puppet.conf I get in the syslog a msg
Mar 23 17:35:26 test-box puppet-agent[32527]: Could not run Puppet
configuration client: SIGQUIT
Also the new configuration is not applied. I changed the "runinterval"
value from 180 sec to 20 sec, but still only every 30min I see a
connect.
This only works if I manually do a
/etc/init.d/puppet restart
I am running a opensuse 11.3 x86 and build the RPM myself using the
puppet specfile present in the tarbal.
Can anyone help me out what I am missing?
Thank you very much
stefanero
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Denmat
2011-Mar-24 03:16 UTC
Re: [Puppet Users] Could not run Puppet configuration client: SIGQUIT
Hi, If you try to restart the client during the update, won''t that confuse puppet a bit? Dont subscribe puppet.conf to the service. I''m not sure whether puppet re-reads changes to it''s config files before it does a run (I think it does), but I''m sure what you''re trying to do won''t work. Cheers On 24/03/2011, at 3:46, stefanero <stefanero@gmail.com> wrote:> Hello, > > I am farly new to puppet and wanted to start configure a couple of my > servers. > > I started to write a little test manifest and tryed to update the > puppet client configuration as a test. > > > This is my site.pp > ----------------------------------------------------------------------------- > #set fileserver to get files from > $fileserver = "puppet.hugoboss.com" > > #import different manifets / modules get loaded by default > import "puppetclient.pp" > > # all hosts get these actions > node default { > include puppetclient > } > ----------------------------------------------------------------------------- > > and this is the included puppetclient.pp > cat puppetclient.pp > > ----------------------------------------------------------------------------- > #create puppet directory for loggin etc, this is default for all > clients > #also copy our puppet config files first, when done restart service > and continoue > > class puppetclient { > > package { > facter: > ensure => installed; > puppet: > ensure => installed; > } > > file { > "/var/lib/puppet": > ensure => directory, > owner => "puppet", > group => "puppet", > mode => 0644; > "puppet.conf": > owner => "root", > path => "/etc/puppet/puppet.conf", > source => "puppet://$fileserver/files/puppet-agent.conf"; > "auth.conf": > owner => "root", > path => "/etc/puppet/auth.conf", > source => "puppet://$fileserver/files/auth-agent.conf"; > "namespaceauth.conf": > owner => "root", > path => "/etc/puppet/namespaceauth.conf", > source => "puppet://$fileserver/files/namespaceauth-agent.conf"; > } > > service { > puppet: > ensure => true, > enable => true, > subscribe => [File["puppet.conf"], File["auth.conf"], > File["namespaceauth.conf"], Package[puppet] ] > } > > } > > ----------------------------------------------------------------------------- > > As you can tell, I guess nothing special. > > All files get transfered to the client, but when I change a file for > example the puppet.conf I get in the syslog a msg > > Mar 23 17:35:26 test-box puppet-agent[32527]: Could not run Puppet > configuration client: SIGQUIT > > > Also the new configuration is not applied. I changed the "runinterval" > value from 180 sec to 20 sec, but still only every 30min I see a > connect. > This only works if I manually do a > > /etc/init.d/puppet restart > > I am running a opensuse 11.3 x86 and build the RPM myself using the > puppet specfile present in the tarbal. > > Can anyone help me out what I am missing? > > Thank you very much > stefanero > > > > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
stefanero
2011-Mar-24 08:37 UTC
[Puppet Users] Re: Could not run Puppet configuration client: SIGQUIT
Ah ok I see, I thought as a test to manage the puppet client first would be a good thing, thank your for your answer, then I will go with something like ntp for a test. cu stefanero On 24 Mrz., 04:16, Denmat <tu2bg...@gmail.com> wrote:> Hi, > > If you try to restart the client during the update, won''t that confuse puppet a bit? > > Dont subscribe puppet.conf to the service. I''m not sure whether puppet re-reads changes to it''s config files before it does a run (I think it does), but I''m sure what you''re trying to do won''t work. > > Cheers > > On 24/03/2011, at 3:46, stefanero <stefan...@gmail.com> wrote: > > > > > > > > > Hello, > > > I am farly new to puppet and wanted to start configure a couple of my > > servers. > > > I started to write a little test manifest and tryed to update the > > puppet client configuration as a test. > > > This is my site.pp > > --------------------------------------------------------------------------- -- > > #set fileserver to get files from > > $fileserver = "puppet.hugoboss.com" > > > #import different manifets / modules get loaded by default > > import "puppetclient.pp" > > > # all hosts get these actions > > node default { > > include puppetclient > > } > > --------------------------------------------------------------------------- -- > > > and this is the included puppetclient.pp > > cat puppetclient.pp > > > --------------------------------------------------------------------------- -- > > #create puppet directory for loggin etc, this is default for all > > clients > > #also copy our puppet config files first, when done restart service > > and continoue > > > class puppetclient { > > > package { > > facter: > > ensure => installed; > > puppet: > > ensure => installed; > > } > > > file { > > "/var/lib/puppet": > > ensure => directory, > > owner => "puppet", > > group => "puppet", > > mode => 0644; > > "puppet.conf": > > owner => "root", > > path => "/etc/puppet/puppet.conf", > > source => "puppet://$fileserver/files/puppet-agent.conf"; > > "auth.conf": > > owner => "root", > > path => "/etc/puppet/auth.conf", > > source => "puppet://$fileserver/files/auth-agent.conf"; > > "namespaceauth.conf": > > owner => "root", > > path => "/etc/puppet/namespaceauth.conf", > > source => "puppet://$fileserver/files/namespaceauth-agent.conf"; > > } > > > service { > > puppet: > > ensure => true, > > enable => true, > > subscribe => [File["puppet.conf"], File["auth.conf"], > > File["namespaceauth.conf"], Package[puppet] ] > > } > > > } > > > --------------------------------------------------------------------------- -- > > > As you can tell, I guess nothing special. > > > All files get transfered to the client, but when I change a file for > > example the puppet.conf I get in the syslog a msg > > > Mar 23 17:35:26 test-box puppet-agent[32527]: Could not run Puppet > > configuration client: SIGQUIT > > > Also the new configuration is not applied. I changed the "runinterval" > > value from 180 sec to 20 sec, but still only every 30min I see a > > connect. > > This only works if I manually do a > > > /etc/init.d/puppet restart > > > I am running a opensuse 11.3 x86 and build the RPM myself using the > > puppet specfile present in the tarbal. > > > Can anyone help me out what I am missing? > > > Thank you very much > > stefanero > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
stefanero
2011-Mar-24 11:33 UTC
[Puppet Users] Re: Could not run Puppet configuration client: SIGQUIT
I need to adjust the runinterval for example, because 30min is way to often when you change something once a month. Therefor I would have to update the puppet.conf file , and then give the client a restart to take its new config. Well I did another test, took out puppet.conf from the service definition, and changed puppet.conf. The client received an update, but it did not "restart" itself, so the old configuration was still active. So the client did not check if its config changed or not. Of course I could write a little script, to check when the puppet.conf changed and restart the puppet agent. But this seams to me just a workaround :-/ maybe someone knows a way to accomplish this. Thnx Stefanero On 24 Mrz., 09:37, stefanero <stefan...@gmail.com> wrote:> Ah ok I see, I thought as a test to manage the puppet client first > would be a good thing, > > thank your for your answer, then I will go with something like ntp for > a test. > > cu > stefanero > > On 24 Mrz., 04:16, Denmat <tu2bg...@gmail.com> wrote: > > > > > > > > > Hi, > > > If you try to restart the client during the update, won''t that confuse puppet a bit? > > > Dont subscribe puppet.conf to the service. I''m not sure whether puppet re-reads changes to it''s config files before it does a run (I think it does), but I''m sure what you''re trying to do won''t work. > > > Cheers > > > On 24/03/2011, at 3:46, stefanero <stefan...@gmail.com> wrote: > > > > Hello, > > > > I am farly new to puppet and wanted to start configure a couple of my > > > servers. > > > > I started to write a little test manifest and tryed to update the > > > puppet client configuration as a test. > > > > This is my site.pp > > > --------------------------------------------------------------------------- -- > > > #set fileserver to get files from > > > $fileserver = "puppet.hugoboss.com" > > > > #import different manifets / modules get loaded by default > > > import "puppetclient.pp" > > > > # all hosts get these actions > > > node default { > > > include puppetclient > > > } > > > --------------------------------------------------------------------------- -- > > > > and this is the included puppetclient.pp > > > cat puppetclient.pp > > > > --------------------------------------------------------------------------- -- > > > #create puppet directory for loggin etc, this is default for all > > > clients > > > #also copy our puppet config files first, when done restart service > > > and continoue > > > > class puppetclient { > > > > package { > > > facter: > > > ensure => installed; > > > puppet: > > > ensure => installed; > > > } > > > > file { > > > "/var/lib/puppet": > > > ensure => directory, > > > owner => "puppet", > > > group => "puppet", > > > mode => 0644; > > > "puppet.conf": > > > owner => "root", > > > path => "/etc/puppet/puppet.conf", > > > source => "puppet://$fileserver/files/puppet-agent.conf"; > > > "auth.conf": > > > owner => "root", > > > path => "/etc/puppet/auth.conf", > > > source => "puppet://$fileserver/files/auth-agent.conf"; > > > "namespaceauth.conf": > > > owner => "root", > > > path => "/etc/puppet/namespaceauth.conf", > > > source => "puppet://$fileserver/files/namespaceauth-agent.conf"; > > > } > > > > service { > > > puppet: > > > ensure => true, > > > enable => true, > > > subscribe => [File["puppet.conf"], File["auth.conf"], > > > File["namespaceauth.conf"], Package[puppet] ] > > > } > > > > } > > > > --------------------------------------------------------------------------- -- > > > > As you can tell, I guess nothing special. > > > > All files get transfered to the client, but when I change a file for > > > example the puppet.conf I get in the syslog a msg > > > > Mar 23 17:35:26 test-box puppet-agent[32527]: Could not run Puppet > > > configuration client: SIGQUIT > > > > Also the new configuration is not applied. I changed the "runinterval" > > > value from 180 sec to 20 sec, but still only every 30min I see a > > > connect. > > > This only works if I manually do a > > > > /etc/init.d/puppet restart > > > > I am running a opensuse 11.3 x86 and build the RPM myself using the > > > puppet specfile present in the tarbal. > > > > Can anyone help me out what I am missing? > > > > Thank you very much > > > stefanero > > > > -- > > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > > To post to this group, send email to puppet-users@googlegroups.com. > > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
jcbollinger
2011-Mar-24 13:03 UTC
[Puppet Users] Re: Could not run Puppet configuration client: SIGQUIT
On Mar 24, 6:33 am, stefanero <stefan...@gmail.com> wrote:> I need to adjust the runinterval for example, because 30min is way to > often when you change something once a month.Naturally you do need to choose a run interval that is appropriate for your situation. Do remember, however, that Puppet is about more than pushing out intentional configuration changes. It is also about *maintaining* your systems'' configurations in the state you have declared, in the face of possible alterations arising from other sources. It is also about monitoring, if you so choose. None of that makes 30 minutes any kind of magic interval, but I do encourage you to take the whole picture into account when you choose an interval.> Therefor I would have to update the puppet.conf file , and then give > the client a restart to take its new config. > > Well I did another test, > took out puppet.conf from the service definition, and changed > puppet.conf. > The client received an update, but it did not "restart" itself, so the > old configuration was still active. So the client did not check if its > config changed or not. > > Of course I could write a little script, to check when the puppet.conf > changed and restart the puppet agent. > But this seams to me just a workaround :-/ > > maybe someone knows a way to accomplish this.Some people trigger regular puppetd runs via cron instead of running puppetd in daemon mode. I think most choose that route for other reasons, but it certainly avoids problems with puppetd recognizing changes to its own configuration. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
stefanero
2011-Mar-24 16:09 UTC
[Puppet Users] Re: Could not run Puppet configuration client: SIGQUIT
Hi John, thnx you for an answer. I think cron might be a good option. Stefanero On 24 Mrz., 14:03, jcbollinger <John.Bollin...@stJude.org> wrote:> On Mar 24, 6:33 am, stefanero <stefan...@gmail.com> wrote: > > > I need to adjust the runinterval for example, because 30min is way to > > often when you change something once a month. > > Naturally you do need to choose a run interval that is appropriate for > your situation. Do remember, however, that Puppet is about more than > pushing out intentional configuration changes. It is also about > *maintaining* your systems'' configurations in the state you have > declared, in the face of possible alterations arising from other > sources. It is also about monitoring, if you so choose. > > None of that makes 30 minutes any kind of magic interval, but I do > encourage you to take the whole picture into account when you choose > an interval. > > > Therefor I would have to update the puppet.conf file , and then give > > the client a restart to take its new config. > > > Well I did another test, > > took out puppet.conf from the service definition, and changed > > puppet.conf. > > The client received an update, but it did not "restart" itself, so the > > old configuration was still active. So the client did not check if its > > config changed or not. > > > Of course I could write a little script, to check when the puppet.conf > > changed and restart the puppet agent. > > But this seams to me just a workaround :-/ > > > maybe someone knows a way to accomplish this. > > Some people trigger regular puppetd runs via cron instead of running > puppetd in daemon mode. I think most choose that route for other > reasons, but it certainly avoids problems with puppetd recognizing > changes to its own configuration. > > John-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.