10.09.2011, 18:35 UTC+2

Sie sind nicht angemeldet.

NDO, can't connect to sink....

DougWare

Anfänger

Beiträge: 7

Anzahl Nagios-Server: 3

Nagios-Version(en): 3.x

Verteiltes Monitoring: Nein

Redundantes Monitoring: Ja

Anzahl-Hosts: 50

Anzahl Services: 150

Betriebssystem(e): Linux

Plugin-Version(en): 3.x

NDO-Version: 3

1

27.02.2009, 19:59

NDO, can't connect to sink....

I've read the threads I can find about the error "ndomod: Still unable to connect to data sink.", but I can find anything to help my problem.

I'm running NagVis 1.3.2 on CentOS 5.2. I've enabled debugging in NDO, and the debug file is created but is completely empty.

Here is my ndomod.cfg file:

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150

#####################################################################
# NDOMOD CONFIG FILE
#
# Last Modified: 09-05-2007
#####################################################################


# INSTANCE NAME
# This option identifies the "name" associated with this particular
# instance of Nagios and is used to seperate data coming from multiple
# instances.  Defaults to 'default' (without quotes).

instance_name=default



# OUTPUT TYPE
# This option determines what type of output sink the NDO NEB module
# should use for data output.  Valid options include:
#   file        = standard text file
#   tcpsocket  = TCP socket
#   unixsocket = UNIX domain socket (default)

#output_type=file
output_type=tcpsocket
#output_type=unixsocket



# OUTPUT
# This option determines the name and path of the file or UNIX domain
# socket to which output will be sent if the output type option specified
# above is "file" or "unixsocket", respectively.  If the output type
# option is "tcpsocket", this option is used to specify the IP address
# of fully qualified domain name of the host that the module should
# connect to for sending output.

#output=/usr/local/nagios/var/ndo.dat
output=10.0.0.253
#output=/var/log/nagios/socket



# TCP PORT
# This option determines what port the module will connect to in
# order to send output.  This option is only vlaid if the output type
# option specified above is "tcpsocket".

tcp_port=5777



# OUTPUT BUFFER
# This option determines the size of the output buffer, which will help
# prevent data from getting lost if there is a temporary disconnect from
# the data sink.  The number of items specified here is the number of
# lines (each of variable size) of output that will be buffered.

output_buffer_items=5000



# BUFFER FILE
# This option is used to specify a file which will be used to store the
# contents of buffered data which could not be sent to the NDO2DB daemon
# before Nagios shuts down.  Prior to shutting down, the NDO NEB module
# will write all buffered data to this file for later processing.  When
# Nagios (re)starts, the NDO NEB module will read the contents of this
# file and send it to the NDO2DB daemon for processing.

buffer_file=/tmp/ndomod.tmp



# FILE ROTATION INTERVAL
# This option determines how often (in seconds) the output file is
# rotated by Nagios.  File rotation is handled by Nagios by executing
# the command defined by the file_rotation_command option.  This
# option has no effect if the output_type option is a socket.

file_rotation_interval=14400



# FILE ROTATION COMMAND
# This option specified the command (as defined in Nagios) that is
# used to rotate the output file at the interval specified by the
# file_rotation_interval option.  This option has no effect if the
# output_type option is a socket.
#
# See the file 'misccommands.cfg' for an example command definition
# that you can use to rotate the log file.

#file_rotation_command=rotate_ndo_log



# FILE ROTATION TIMEOUT
# This option specified the maximum number of seconds that the file
# rotation command should be allowed to run before being prematurely
# terminated.

file_rotation_timeout=60



# RECONNECT INTERVAL
# This option determines how often (in seconds) that the NDO NEB
# module will attempt to re-connect to the output file or socket if
# a connection to it is lost.

reconnect_interval=5



# RECONNECT WARNING INTERVAL
# This option determines how often (in seconds) a warning message will
# be logged to the Nagios log file if a connection to the output file
# or socket cannot be re-established.

reconnect_warning_interval=15
#reconnect_warning_interval=900



# DATA PROCESSING OPTION
# This option determines what data the NDO NEB module will process.
# Do not mess with this option unless you know what you're doing!!!!
# Read the source code (include/ndbxtmod.h) to determine what values
# to use here.  Values from source code should be OR'ed to get the
# value to use here.  A value of -1 will cause all data to be processed.
# Read the source code (include/ndomod.h) and look for "NDOMOD_PROCESS_"
# to determine what values to use here.  Values from source code should
# be OR'ed to get the value to use here.  A value of -1 will cause all
# data to be processed.

data_processing_options=-1



# CONFIG OUTPUT OPTION
# This option determines what types of configuration data the NDO
# NEB module will dump from Nagios.  Values can be OR'ed together.
# Values:
#       0 = Don't dump any configuration information
#       1 = Dump only original config (from config files)
#       2 = Dump config only after retained information has been restored
#       3 = Dump both original and retained configuration

config_output_options=3


Here is my /etc/nagios/ndo2db.cfg

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164

#####################################################################
# NDO2DB DAEMON CONFIG FILE
#
# Last Modified: 10-29-2007
#####################################################################


# USER/GROUP PRIVILIGES
# These options determine the user/group that the daemon should run as.
# You can specify a number (uid/gid) or a name for either option.

ndo2db_user=nagios
ndo2db_group=nagios



# SOCKET TYPE
# This option determines what type of socket the daemon will create
# an accept connections from.
# Value:
#   unix = Unix domain socket (default)
#   tcp  = TCP socket

#socket_type=unix
socket_type=tcp



# SOCKET NAME
# This option determines the name and path of the UNIX domain
# socket that the daemon will create and accept connections from.
# This option is only valid if the socket type specified above
# is "unix".

#socket_name=/var/log/nagios/socket



# TCP PORT
# This option determines what port the daemon will listen for
# connections on.  This option is only vlaid if the socket type
# specified above is "tcp".

tcp_port=5777



# DATABASE SERVER TYPE
# This option determines what type of DB server the daemon should
# connect to.
# Values:
#       mysql = MySQL
#       pgsql = PostgreSQL

db_servertype=mysql



# DATABASE HOST
# This option specifies what host the DB server is running on.

db_host=localhost

# DATABASE PORT
# This option specifies the port that the DB server is running on.
# Values:
#       3306 = Default MySQL port
#       5432 = Default PostgreSQL port

db_port=3306



# DATABASE NAME
# This option specifies the name of the database that should be used.

db_name=ndo



# DATABASE TABLE PREFIX
# Determines the prefix (if any) that should be prepended to table names.
# If you modify the table prefix, you'll need to modify the SQL script for
# creating the database!

db_prefix=nagios_



# DATABASE USERNAME/PASSWORD
# This is the username/password that will be used to authenticate to the DB.
# The user needs at least SELECT, INSERT, UPDATE, and DELETE privileges on
# the database.

db_user=ndo
db_pass=************HIDDEN************



## TABLE TRIMMING OPTIONS
# Several database tables containing Nagios event data can become quite large
# over time.  Most admins will want to trim these tables and keep only a
# certain amount of data in them.  The options below are used to specify the
# age (in MINUTES) that data should be allowd to remain in various tables
# before it is deleted.  Using a value of zero (0) for any value means that
# that particular table should NOT be automatically trimmed.

# Keep timed events for 24 hours
max_timedevents_age=1440

# Keep system commands for 1 week
max_systemcommands_age=10080

# Keep service checks for 1 week
max_servicechecks_age=10080

# Keep host checks for 1 week
max_hostchecks_age=10080

# Keep event handlers for 31 days
max_eventhandlers_age=44640





# DEBUG LEVEL
# This option determines how much (if any) debugging information will
# be written to the debug file.  OR values together to log multiple
# types of information.
# Values: -1 = Everything
#       0 = Nothing
#       1 = Process info
#       2 = SQL queries

debug_level=-1



# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
# Values: 0 = Brief output
#       1 = More detailed
#       2 = Very detailed

debug_verbosity=2



# DEBUG FILE
# This option determines where the daemon should write debugging information.

debug_file=/var/log/nagios/ndo2db.debug



# MAX DEBUG FILE SIZE
# This option determines the maximum size (in bytes) of the debug file.  If
# the file grows larger than this size, it will be renamed with a .old
# extension.  If a file already exists with a .old extension it will
# automatically be deleted.  This helps ensure your disk space usage doesn't
# get out of control when debugging.

max_debug_file_size=10000


Where should I go from here?

DougWare

Anfänger

Beiträge: 7

Anzahl Nagios-Server: 3

Nagios-Version(en): 3.x

Verteiltes Monitoring: Nein

Redundantes Monitoring: Ja

Anzahl-Hosts: 50

Anzahl Services: 150

Betriebssystem(e): Linux

Plugin-Version(en): 3.x

NDO-Version: 3

2

27.02.2009, 20:06

As a side note, here is my ./configure output....

Quellcode

 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224

[root ndoutils-1.4b7]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking whether make sets $(MAKE)... yes
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking dirent.h usability... yes
checking dirent.h presence... yes
checking for dirent.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking grp.h usability... yes
checking grp.h presence... yes
checking for grp.h... yes
checking for inttypes.h... (cached) yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking ltdl.h usability... no
checking ltdl.h presence... no
checking for ltdl.h... no
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking socket.h usability... no
checking socket.h presence... no
checking for socket.h... no
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking for stdint.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking sys/msg.h usability... yes
checking sys/msg.h presence... yes
checking for sys/msg.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking sys/sendfile.h usability... yes
checking sys/sendfile.h presence... yes
checking for sys/sendfile.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for sys/stat.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/timeb.h usability... yes
checking sys/timeb.h presence... yes
checking for sys/timeb.h... yes
checking for sys/types.h... (cached) yes
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking for sys/wait.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking tcpd.h usability... yes
checking tcpd.h presence... yes
checking for tcpd.h... yes
checking for unistd.h... (cached) yes
checking values.h usability... yes
checking values.h presence... yes
checking for values.h... yes
checking for an ANSI C-conforming const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for mode_t... yes
checking for pid_t... yes
checking for size_t... yes
checking return type of signal handlers... void
checking for uid_t in sys/types.h... yes
checking type of array argument to getgroups... gid_t
checking for int... yes
checking size of int... 4
checking for short... yes
checking size of short... 2
checking for long... yes
checking size of long... 4
checking for uint32_t... yes
checking for u_int32_t... yes
checking for int32_t... yes
checking for getopt_long... yes
checking for main in -lnsl... yes
checking for socket in -lsocket... no
checking for main in -lwrap... yes
checking for strdup... yes
checking for strstr... yes
checking for strtoul... yes
checking for initgroups... yes
checking for strtof... yes
checking for type of socket size... size_t
checking for linker flags for loadable modules... -shared
checking for compress in -lz... yes
checking for mysql_store_result in -lmysqlclient... yes
checking for mysql_connect in -lmysqlclient... no
checking mysql/mysql.h usability... yes
checking mysql/mysql.h presence... yes
checking for mysql/mysql.h... yes
MySQL library and include file(s) were found!
checking for PQconnectdb in -lpq... no


*** PostgreSQL library could not be located... *********************

You chose to compile NDBXT with PostgreSQL support, but I was
unable to locate the PostgreSQL library on your system.  If the
library is installed,  use the --with-pgsql-lib argument to specify
the location of the PostgreSQL library.

NOTE: After you install the necessary libraries on your system:
        1. Make sure /etc/ld.so.conf has an entry for the directory in
        which the PostgreSQL libraries are installed.
        2. Run 'ldconfig' to update the run-time linker options.
        3. Run 'make devclean' in the NDBXT distribution to clean out
        any old references to your previous compile.
        4. Rerun the configure script.

********************************************************************


checking libpq-fe.h usability... no
checking libpq-fe.h presence... no
checking for libpq-fe.h... no


*** PostgreSQL include file could not be located... ****************

You chose to compile NDBXT with PostgreSQL support, but I was unable
to locate  on your system.  If the include file is
installed, use the --with-pgsql-inc argument to specify the location
of the PostgreSQL include file.

********************************************************************


configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating subst
config.status: creating include/config.h
config.status: include/config.h is unchanged


*** Configuration summary for ndoutils 1.4b7 10-31-2007 ***:

 General Options:
 -------------------------
 NDO2DB user:   nagios
 NDO2DB group:   nagios


Review the options above for accuracy.  If they look okay,
type 'make' to compile the NDO utilities.

Andurin

Super Moderator

Beiträge: 4 393

3

28.02.2009, 11:04

Some Logfiles would be greater instead of the whole config dump.

Did you start the NDO2DB Daemon on the receiver?
Is it able to connect to the database?
Is there a firewall between the partners?
Wenn Sie das hier lesen, bin ich schon nicht mehr da... schön war die Ära, toll die Zeiten, super die Kontakte aber für den Moment bin ich raus.

DougWare

Anfänger

Beiträge: 7

Anzahl Nagios-Server: 3

Nagios-Version(en): 3.x

Verteiltes Monitoring: Nein

Redundantes Monitoring: Ja

Anzahl-Hosts: 50

Anzahl Services: 150

Betriebssystem(e): Linux

Plugin-Version(en): 3.x

NDO-Version: 3

4

28.02.2009, 19:02

Hey, thanks for the reply....

The only relevant log file entries are in the nagios.log

Quellcode

 
1
2
3
4
5
6
7
8
9

[1235843958] Nagios 3.0.6 starting... (PID=17322)
[1235843958] Local time is Sat Feb 28 12:59:18 EST 2009
[1235843958] LOG VERSION: 2.0
[1235843958] ndomod: NDOMOD 1.4b7 (10-31-2007) Copyright (c) 2005-2007 Ethan Galstad ()
[1235843958] ndomod: Successfully connected to data sink.  9 queued items to flush.
[1235843958] ndomod: Successfully flushed 9 queued items to data sink.
[1235843958] Event broker module '/usr/lib/nagios/plugins/ndomod.o' initialized successfully.
[1235843958] Finished daemonizing... (New PID=17324)
[1235843958] ndomod: Error writing to data sink!  Some output may get lost...


The ndo server is running. They are actually on the same server, but I couldn't make it work using a socket, or port using localhost so I tried using the actual IP address of the system. I've double checked the database settings for the NDO configuration file, and I can connect to the db using the username/pass/host/port that's configure in the NDO configuration file. The ndo debug file is completely empty (although it gets created when the NDO process is launched) and the mysql tables are empty.

DougWare

Anfänger

Beiträge: 7

Anzahl Nagios-Server: 3

Nagios-Version(en): 3.x

Verteiltes Monitoring: Nein

Redundantes Monitoring: Ja

Anzahl-Hosts: 50

Anzahl Services: 150

Betriebssystem(e): Linux

Plugin-Version(en): 3.x

NDO-Version: 3

5

05.03.2009, 23:51

Bump

dmelo

Anfänger

Beiträge: 1

Anzahl Nagios-Server: 1

Nagios-Version(en): 3

Verteiltes Monitoring: Nein

Redundantes Monitoring: Nein

Anzahl-Hosts: 10

Anzahl Services: 7

Betriebssystem(e): Ubuntu 11.04

Plugin-Version(en): 1.4.15-3

NDO-Version: 1

6

11.08.2011, 17:08

Same problem on Ubuntu 11.04

I'm having the same problem.

I have installed those packs:



ii nagios-images 0.7 Collection of images and icons for the nagios system
ii nagios-nrpe-plugin 2.12-4ubuntu1 Nagios Remote Plugin Executor Plugin
ii nagios-plugins 1.4.15-3ubuntu1 Plugins for the nagios network monitoring and management system
ii nagios-plugins-basic 1.4.15-3ubuntu1 Plugins for the nagios network monitoring and management system
ii nagios-plugins-extra 1.4.15-3ubuntu1 Plugins for the nagios network monitoring and manegement system.
ii nagios-plugins-standard 1.4.15-3ubuntu1 Plugins for the nagios network monitoring and management system
ii nagios3 3.2.3-1ubuntu1.2 A host/service/network monitoring and management system
ii nagios3-cgi 3.2.3-1ubuntu1.2 cgi files for nagios3
ii nagios3-common 3.2.3-1ubuntu1.2 support files for nagios3
ii nagios3-core 3.2.3-1ubuntu1.2 A host/service/network monitoring and management system core files
ii ndoutils-nagios3-mysql 1.4b9-1.1 This provides the NDOUtils for Nagios with MySQL support


ii nagios3-common 3.2.3-1ubuntu1.2 support files for nagios3
ii nagios3-core 3.2.3-1ubuntu1.2 A host/service/network monitoring and management system core files
ii ndoutils-nagios3-mysql 1.4b9-1.1 This provides the NDOUtils for Nagios with MySQL support

At the log it says


[1313072071] Successfully shutdown... (PID=13850)
[1313072071] ndomod: Shutdown complete.
[1313072071] Event broker module '/usr/lib/ndoutils/ndomod-mysql-3x.o' deinitialized successfully.
[1313072071] Nagios 3.2.3 starting... (PID=13927)
[1313072071] Local time is Thu Aug 11 11:14:31 BRT 2011
[1313072071] LOG VERSION: 2.0
[1313072071] ndomod: NDOMOD 1.4b9 (10-27-2009) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
[1313072071] ndomod: Could not open data sink! I'll keep trying, but some output may get lost...
[1313072071] Event broker module '/usr/lib/ndoutils/ndomod-mysql-3x.o' initialized successfully.
[1313072071] Finished daemonizing... (New PID=13928)
[1313072983] ndomod: Still unable to connect to data sink. 208 items lost, 5000 queued items to flush.
[1313073895] ndomod: Still unable to connect to data sink. 4872 items lost, 5000 queued items to flush.
[1313074807] ndomod: Still unable to connect to data sink. 9528 items lost, 5000 queued items to flush.

Does anyone knows how to solve this problem?

Rene Storm

Schüler

Beiträge: 100

Geschlecht: Männlich

Wohnort: Hamburg

Anzahl Nagios-Server: some

Hobbys: kitesurfing, buggykiting, snowboard,climbing,sleeping

Nagios-Version(en): 3

Verteiltes Monitoring: Ja

Redundantes Monitoring: Ja

Anzahl-Hosts: 600

Anzahl Services: 6000

Betriebssystem(e): Linux

Plugin-Version(en): latest

NagVis-Version: latest

NDO-Version: latest

7

12.08.2011, 07:18

Stupid Question:

Is the database started? Are you able to write to the database? Did you actually tested it?

Regards,
Rene

dnsmichi

Meister

Beiträge: 2 448

Geburtstag: 30.05.1983 (28)

Geschlecht: Männlich

Wohnort: Wien

Beruf: DNS & Monitoring Developer

Anzahl Nagios-Server: 4x Icinga prod, 2x test/dev

Nagios-Version(en): s/nagios/icinga/

Icinga-Version(en): 1.4.2 / GIT

Verteiltes Monitoring: Ja

Redundantes Monitoring: Ja

Anzahl-Hosts: 1000+

Anzahl Services: 15000+

Betriebssystem(e): RHEL 5.7 / 6 x64

Plugin-Version(en): 1.4.15

IDO-Version: 1.4.2 / GIT MySQL/Postgresql/Oracle

Sonstige Addon's: PNP 0.6.11, check_mk GIT

8

19.08.2011, 15:10

Quellcode

 
1

# ps aux | grep ndo
Icinga 1.5 MySQL,PGSQL,Oracle and IPv6

Demos

http://docs.icinga.org
https://wiki.icinga.org
https://dev.icinga.org

* egrep -v "^#|^$" configfile

Join us online!
irc.freenode.net #icinga-devel

Using Icinga? Tell us!


Fork me on

Ähnliche Themen