Nagios nsca插件进程突然死掉
nsca监控属于被动式监控,是nagios的一个重要插件;使用克隆的方式增加nagios分布式节点一段时间后,nsca进程自动关闭
原因:nsca配置文件没有修改
[root@sznagiosapp1 etc]# cat nsca.cfg
####################################################
# Sample NSCA Daemon Config File
# Written by: Ethan Galstad (nagios@nagios.org)
#
# Last Modified: 11-23-2007
####################################################
# LOG FACILITY
# The syslog facility that should be used for logging purposes.
log_facility=daemon
# Check Result directory. If passed, skip command pipe and submit
# directly into the checkresult directory. Requires Nagios 3+
# For best results, mount dir on ramdisk.
#check_result_path=/usr/local/nagios/var/checkresults
# PID FILE
# The name of the file in which the NSCA daemon should write it's process ID
# number. The file is only written if the NSCA daemon is started by the root
# user as a single- or multi-process daemon.
pid_file=/var/run/nsca.pid
# PORT NUMBER
# Port number we should wait for connections on.
# This must be a non-priveledged port (i.e. > 1024).
server_port=5667
# SERVER ADDRESS
# Address that NSCA has to bind to in case there are
# more as one interface and we do not want NSCA to bind
# (thus listen) on all interfaces.
server_address=192.168.9.122 (服务器ip对应)
# NSCA USER
# This determines the effective user that the NSCA daemon should run as.
# You can either supply a username or a UID.
#
# NOTE: This option is ignored if NSCA is running under either inetd or xinetd
nsca_user=nagios
# NSCA GROUP
# This determines the effective group that the NSCA daemon should run as.
# You can either supply a group name or a GID.
#
# NOTE: This option is ignored if NSCA is running under either inetd or xinetd
nsca_group=nagios
# NSCA CHROOT
# If specified, determines a directory into which the nsca daemon
# will perform a chroot(2) operation before dropping its privileges.
# for the security conscious this can add a layer of protection in
# the event that the nagios daemon is compromised.
#
# NOTE: if you specify this option, the command file will be opened
# relative to this directory.
#nsca_chroot=/var/run/nagios/rw
# DEBUGGING OPTION
# This option determines whether or not debugging
# messages are logged to the syslog facility.
# Values: 0 = debugging off, 1 = debugging on
debug=0
# COMMAND FILE
# This is the location of the Nagios command file that the daemon
# should write all service check results that it receives.
command_file=/usr/local/nagios/var/rw/nagios.cmd
# ALTERNATE DUMP FILE
# This is used to specify an alternate file the daemon should
# write service check results to in the event the command file
# does not exist. It is important to note that the command file
# is implemented as a named pipe and only exists when Nagios is
# running. You may want to modify the startup script for Nagios
# to dump the contents of this file into the command file after
# it starts Nagios. Or you may simply choose to ignore any
# check results received while Nagios was not running...
alternate_dump_file=/usr/local/nagios/var/rw/nsca.dump
# AGGREGATED WRITES OPTION
# This option determines whether or not the nsca daemon will
# aggregate writes to the external command file for client
# connections that contain multiple check results. If you
# are queueing service check results on remote hosts and
# sending them to the nsca daemon in bulk, you will probably
# want to enable bulk writes, as this will be a bit more
# efficient.
# Values: 0 = do not aggregate writes, 1 = aggregate writes
aggregate_writes=0
# APPEND TO FILE OPTION
# This option determines whether or not the nsca daemon will
# will open the external command file for writing or appending.
# This option should almost *always* be set to 0!
# Values: 0 = open file for writing, 1 = open file for appending
append_to_file=0
# MAX PACKET AGE OPTION
# This option is used by the nsca daemon to determine when client
# data is too old to be valid. Keeping this value as small as
# possible is recommended, as it helps prevent the possibility of
# "replay" attacks. This value needs to be at least as long as
# the time it takes your clients to send their data to the server.
# Values are in seconds. The max packet age cannot exceed 15
# minutes (900 seconds). If this variable is set to zero (0), no
# packets will be rejected based on their age.
max_packet_age=60
# DECRYPTION PASSWORD
# This is the password/passphrase that should be used to descrypt the
# incoming packets. Note that all clients must encrypt the packets
# they send using the same password!
# IMPORTANT: You don't want all the users on this system to be able
# to read the password you specify here, so make sure to set
# restrictive permissions on this config file!
password=password123
# DECRYPTION METHOD
# This option determines the method by which the nsca daemon will
# decrypt the packets it receives from the clients. The decryption
# method you choose will be a balance between security and performance,
# as strong encryption methods consume more processor resources.
# You should evaluate your security needs when choosing a decryption
# method.
#
# Note: The decryption method you specify here must match the
# encryption method the nsca clients use (as specified in
# the send_nsca.cfg file)!!
# Values:
#
# 0 = None (Do NOT use this option)
# 1 = Simple XOR (No security, just obfuscation, but very fast)
#
# 2 = DES
# 3 = 3DES (Triple DES)
# 4 = CAST-128
# 5 = CAST-256
# 6 = xTEA
# 7 = 3WAY
# 8 = BLOWFISH
# 9 = TWOFISH
# 10 = LOKI97
# 11 = RC2
# 12 = ARCFOUR
#
# 14 = RIJNDAEL-128
# 15 = RIJNDAEL-192
# 16 = RIJNDAEL-256
#
# 19 = WAKE
# 20 = SERPENT
#
# 22 = ENIGMA (Unix crypt)
# 23 = GOST
# 24 = SAFER64
# 25 = SAFER128
# 26 = SAFER+
#
decryption_method=1
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/29500582/viewspace-1300310/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/29500582/viewspace-1300310/
Nagios nsca插件进程突然死掉相关推荐
- 查看终端进程是否死掉技巧
有时候我们打开某个终端执行命令会出现以下情况,比如源码装wdcp: installing mysql,this may take a few minutes,hold on plz... config ...
- java 进程 突然死掉_一次 java 进程猝死的原因分析
问题 Java进程在服务器中运行一段时间,服务不稳定,偶尔出现进程无故的死亡.临时的办法是重启进程,但过一段时间后又无故死亡.没有任何 jvm oom的错误信息. 路径 1.通过jvm监控查看jvm监 ...
- Nagios的插件-nsca
原创作品,允许转载,转载时请务必以超链接形式标明文章 原始出处 .作者信息和本声明.否则将追究法律责任.http://5122542.blog.51cto.com/5112542/1037600 Na ...
- 服务器清理死掉的进程
服务器清理死掉的进程 在服务器上跑程序突然发现GPU占用了 先用 nvidia-smi 看一下是什么进程占用了,发现里面并没有显示 那应该是有之前跑的网络程序死掉了,没清理干净,查看一下占用情况: p ...
- Cartographor定位-shell脚本:不停拉起死掉的程序和脚本
这个数据问题已经通过修改ros的消息发送方式解决了! 基站定位 在使用UWB基站进行定位的时候,由于消息格式不一致,且偶尔会有数据缺失,容易造成底层ROS程序出现vector(size()==0 ), ...
- 解决Ubuntu中文件管理器死掉的情况
有时会遇到Ubuntu文件管理器死掉的情况,怎么点击都没有反应,这时只需在终端上运行 ps -A | grep nautilus, 查找文件管理器nautilus对应的pid,然后sudo+kill+ ...
- linux进程假死的原因_Linux系统死机的原因及解决办法
系统出现死机,一般分为两种情况:一是硬件问题;二是软件问题. 一.硬件问题 可以考虑分析以下几点: 1.不要超频CPU,如果已经超频的先回复到原来的频率 虽然平时运行没有问题,但可能在高负载的使用中就 ...
- Java程序突然死掉的原因
Java程序突然死掉的原因一般有三种: 程序OOM了,自己的Java程序申请内存创建对象的时候,申请的内存超出了堆内存的限制,此时我们叫做堆OOM了,当然还包括栈溢出,本地方法区溢出. 程序占用的内存 ...
- linux下使用daemontools的supervise让不稳定程序死掉自动马上重启
前言:supervise是daemontools的一个工具,可以用来监控linux下程序的进程状态,当程序有一些问题(例如死掉)会根据设置 自动重启.我有一个socket服务器端需要一直监听数据,但是 ...
最新文章
- pd.dataframe.append
- gcc / -L 和 -Wl,-rpath 区别
- jquery.zSlide.js-基于CSS3/HTML5演示文档jQuery插件
- for range 经典问题
- mysql中如何把两个查询结果列数不同并成一张表_MySQL
- 如何关闭父窗体?C#
- c++ 显示三维散点图_Python数据可视化,Matplotlib绘制“散点图”的两种方法!
- [笔记]远传中继的实现
- 冒泡排序之Java实现
- js 容易忽略的小知识点
- 偏相关分析MATLAB代码实现
- 雨木林风 的 Ylmf OS
- 迪乐尼童鞋防骗子—常见网络骗子骗术防御要点
- 新手怎样才能快速的学会建网站
- 创意示范:苹果如何使用无线充电技术
- thinkadmin 配置 iis 宝塔、护卫神、phpstudy伪静态设置
- 三代终端容器 KUN 的首次大考【架构演进】
- 2020博客之星年度总评选TOP200名单已出,感谢老铁们的支持目前排名TOP77
- iOS开发- 文件共享(利用iTunes导入文件, 并且显示已有文件)
- 被取代的ERP?EBC正在用业务数字化让管理出效益
热门文章
- php inpo,优化PHP in_array()函数,效率提高50倍
- 测试过程中,遇到开发不认为是bug的bug,该怎么办
- 绑定机制(转自天运科技)
- 为什么项目经理都需要PMP认证?
- About Spreadsheets
- TCP的核心系列 — SACK和DSACK的实现(六)
- 拼团商城是如何盈利的?
- QTextEdit只接受数字输入
- linux查找多少天前的文件,linuxfind查找大于多少天的文件,并删除之
- angular中的 :host 、:host-context、::ng-deep