Jose, thank you for the reply. Yes, I understand all those commands. Oh, so you are saying I can use mco to temporarily stop my puppet agent when I need to do mco runonce and then start it back. Good idea!
But what is the answer to my question: Can I have both puppet agent running (so that it can retrieve/apply the catalog as runinterval scheduled) and at same time run "mco puppet runonce" to push configuration change to multiple machines? Now I can't, I always get daemon running error. What is the correct mco command to run to achieve my purpose? If that's not possible, should I stop puppet agent entirely so that I can run mco puppet runone successfully, and setup a cron job to start puppet agent as the runinterval scheduled? What will not happen if puppet agent is stopped entirely? It won't retrieve and apply catalog, right? No sending report to puppet master? thanks, Stella On Friday, September 5, 2014 2:53:06 PM UTC-4, Jose Luis Ledesma wrote: > > Forgot about last question,you can specify more than one -I in each command > El 05/09/2014 20:46, "Stella" <stellat...@gmail.com <javascript:>> > escribió: > >> Hi, >> >> I am using open source Puppet 3.6.2 with Dashboard and Mcollective. >> >> If I have puppet agent running and then from puppet master I run "mco >> puppet runonce --server puppetmaster_name", I will get this error: >> Cannot specify any custom puppet options when the daemon is running >> >> I understand that I do not need to have puppet agent running for the >> agent to work. >> I can stop it entirely and then trigger runs through mcollective -- in >> that setup it will happily pass custom arguments like --noop or --no-noop >> etc. >> >> However, that's not exactly what I want. Here is what I want: >> >> 1. I want my puppet agent to be running so that it can retrieve the >> catalog from puppet master based on the runinterval set in >> /etc/puppet/puppet.conf on agent machine. For example, >> >> #The interval between each puppet agent run, in seconds >> runinterval = 6000 >> >> In one post, someone mentioned that if you did want periodic noop runs >> then just cron >> puppet agent --daemonize --onetime --noop >> >> So if I setup cron for puppet agent, that will run "puppet agent --test" >> based on the cron schedule? >> >> 2. Occasionally, I want to push configuration change and don't want to >> wait until the next runinterval time. I want to push the change to my >> puppet agent machines using MCollective command line "mco puppet runonce". >> >> mco puppet runonce --server host_name >> >> In this case, I always get "daemon is running" error, if puppet agent is >> running, if I use --server option. >> If I use -I option (mco puppet runonce -I puppet-agent.example.com) >> <http://puppet-agent.example.com>, it works even if puppet agent daemon >> is running. >> What is the difference between option --server and -I? If I want to push >> configurations to multiple hosts, which option should I use? >> >> Hope I make myself understood :) >> >> Thanks a lot, >> Stella >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/15daf8e8-b45e-49d4-9358-c9a03969e85f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/puppet-users/15daf8e8-b45e-49d4-9358-c9a03969e85f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4654b2fb-fefd-4c63-99e5-5bac4f40833e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
