if node['kernel']['machine'] == "x86_64"
chocolatey "NSClientPlusPlus.x64"
else
chocolatey "NSClientPlusPlus.x86"
end
template "#{node['chocolatey-base-packages']['nsclientpath']}NSC.ini" do
source "NSC.ini.erb"
action :create
notifies :restart, "service[NSClientpp]", :immediately
end
service "NSClientpp" do
service_name "NSClientpp"
supports :start => true, :stop => true, :restart => true
action [:restart, :enable]
Tim,I just created a new receipe that I call within my roles. I was going to had an override attribute/default attribute that chmod's the plugin for 755; however, it seems like something is overwriting that. I just don't know what/why it would change the plugin to 644 which doesn't allow for it to execute.As for the NSClient++ - I can have that manually dropped and installed on the windows (wish there was a cookbook that would do this; however, i would not be able to controls distributed changes across all windows servers. What has been done previously by others?--On Wed, Aug 28, 2013 at 4:29 PM, Tim Smith < " target="_blank"> > wrote:
NSClient++ can be used for Windows hosts, but there is not a cookbook that I know of for that right now. In general the idea behind the plugins is that this should be handled outside of the nagios cookbook itself. You should create a wrapper cookbook that drops the plugin files into the correct directory and then you should use the NRPE LWRP to create that check that uses the plugin. That way you avoid modifying the nagios cookbook and having to merge in changes from later community releases. In the past the nagios cookbook included a large number of commonly used plugins and hardcoded those into the NRPE config. It was a bit of a nightmare as every environment uses the checks a bit differently. We chose to remove them all and leave it up to the user to decide what they wanted.-TimOn Aug 28, 2013, at 12:40 PM, Nikhil Shah < " target="_blank"> > wrote:Also, do you know if there is a way to check windows server? Typically I would using NSClient++; however, I do not see a cookbook for this.Nikhil Shah / System AdministratorThe Orchard® / www.theorchard.com23 E. 4th St., 3rd Fl / New York, NY 10003The Daily Rind™ / www.dailyrindblog.com
Facebook / @orchtweets
Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.On Aug 28, 2013, at 1:09 PM, Daniel DeLeo < " target="_blank"> > wrote:On Wednesday, August 28, 2013 at 10:05 AM, " target="_blank"> wrote:
With some difficulties, I was able to deploy out the nagios cookbook.However, I noticed there was no "custom plugins location" so I created oneunder files with the following recipe:remote_directory node['nagios']['plugin_dir'] dosource "plugins"owner "nagios"group "nagios"mode 0775recursive trueendHowever, everytime I push up a new custom plugin, it's not accepting my mode0755 and I keep getting the following when I run chef-clientchange mode from '' to '0644What is right above this line? You should see the name of the resource that's making the change.--Daniel DeLeoNikhil Shah / System Administrator
nshah@theorchard.com
The Orchard® / www.theorchard.com
t (+1) 212.308.5648 / f (+1) 212.201.9203
23 E. 4th St., 3rd Fl / New York, NY 10003
The Daily Rind™ / www.dailyrindblog.com
Privileged And Confidential Communication.
This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited
Archive powered by MHonArc 2.6.16.