Sunday, May 19th 2013, 12:42pm UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to Monitoring-Portal.
Although this is a german monitoring forum, please don't hesitate to post in English. Nearly everybody here understands you and will answer in English as well.
If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form to register here or read more information about the registration process. If you are already registered, please login here.

ceramicx

Beginner

Posts: 20

Birthday: Sep 8th

Number of monitoring servers: 2

Nagios Version: 3.2

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 350

Number of services: >3500

OS: MS Windows Server 2000, 2003, 2008, 2008 R2 / Debian 5.0 Lenny / Windows 2k, XP, Vista, 7

Plugin Version: 1.4.x

1

Wednesday, January 18th 2012, 5:46pm

IDOMOD schreibt keine Daten in Unixsocket

Hallo liebe Gemeinde,

ich komme nicht weiter, ich habe von Nagios 3 nach Icinga 1.6.1 migriert.
Die ältere Oberfläche funktioniert tadellos, Icinga selber auch.
Ich habe nun zusätzlich Icinga Web und PostgreSQL installiert.
Das Problem ist, IDOMOD schreibt mir keinerlei Daten in die sock noch schreibt es etwas in die debug Datei, legt diese aber an.
WOran liegt das?

Hier mal Configs:

icinga.cfg (Teil davon)

Source code

1
2
3
event_broker_options=-1
broker_module=/usr/local/icinga/bin/idomod.o config_file=/usr/local/icinga/etc/idomod.cfg
cfg_dir=/usr/local/icinga/etc/modules/


idomod.cfg

Source code

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
instance_name=default


output_type=unixsocket

output=/usr/local/icinga/var/ido.sock



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

tcp_port=5668



# ENCRYPTION
# This option determines if the module will use SSL to encrypt the 
# network traffic between module and ido2db daemon.
# Both sides have to enable this feature which depends on SSL Libraries
# like openssl or kerberos 
# This option is only valid if the output type
# option specified above is "tcpsocket".
#
# A value of '1' will enable this feature

use_ssl=0



# 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 IDO2DB daemon
# before Icinga shuts down.  Prior to shutting down, the IDO NEB module
# will write all buffered data to this file for later processing.  When
# Icinga (re)starts, the IDO NEB module will read the contents of this
# file and send it to the IDO2DB daemon for processing.

buffer_file=/usr/local/icinga/var/idomod.tmp



# FILE ROTATION INTERVAL
# This option determines how often (in seconds) the output file is
# rotated by Icinga.  File rotation is handled by Icinga 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 Icinga) 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_ido_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 IDO NEB
# module will attempt to re-connect to the output file or socket if
# a connection to it is lost.

reconnect_interval=15



# RECONNECT WARNING INTERVAL
# This option determines how often (in seconds) a warning message will
# be logged to the Icinga 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 IDO NEB module will process. 
# Do not mess with this option unless you know what you're doing!!!!
#
# Read the source code (module/idoutils/include/idomod.h) and look for 
# "IDOMOD_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. 

# Basically you have to calculate from the following values
#
#define IDOMOD_PROCESS_PROCESS_DATA                   1
#define IDOMOD_PROCESS_TIMED_EVENT_DATA               2
#define IDOMOD_PROCESS_LOG_DATA                       4
#define IDOMOD_PROCESS_SYSTEM_COMMAND_DATA            8
#define IDOMOD_PROCESS_EVENT_HANDLER_DATA             16
#define IDOMOD_PROCESS_NOTIFICATION_DATA              32
#define IDOMOD_PROCESS_SERVICE_CHECK_DATA             64
#define IDOMOD_PROCESS_HOST_CHECK_DATA                128
#define IDOMOD_PROCESS_COMMENT_DATA                   256
#define IDOMOD_PROCESS_DOWNTIME_DATA                  512
#define IDOMOD_PROCESS_FLAPPING_DATA                  1024
#define IDOMOD_PROCESS_PROGRAM_STATUS_DATA            2048
#define IDOMOD_PROCESS_HOST_STATUS_DATA               4096
#define IDOMOD_PROCESS_SERVICE_STATUS_DATA            8192
#define IDOMOD_PROCESS_ADAPTIVE_PROGRAM_DATA          16384
#define IDOMOD_PROCESS_ADAPTIVE_HOST_DATA             32768
#define IDOMOD_PROCESS_ADAPTIVE_SERVICE_DATA          65536
#define IDOMOD_PROCESS_EXTERNAL_COMMAND_DATA          131072
#define IDOMOD_PROCESS_OBJECT_CONFIG_DATA             262144
#define IDOMOD_PROCESS_MAIN_CONFIG_DATA               524288
#define IDOMOD_PROCESS_AGGREGATED_STATUS_DATA         1048576
#define IDOMOD_PROCESS_RETENTION_DATA                 2097152
#define IDOMOD_PROCESS_ACKNOWLEDGEMENT_DATA           4194304
#define IDOMOD_PROCESS_STATECHANGE_DATA               8388608
#define IDOMOD_PROCESS_CONTACT_STATUS_DATA            16777216
#define IDOMOD_PROCESS_ADAPTIVE_CONTACT_DATA          33554432
#
#define IDOMOD_PROCESS_EVERYTHING                     67108863
#
# You may use the Online Calculator by Gerhard Lausser:
# http://labs.consol.de/nagios/ndo-data-processing-options/
# (please note that there is a checkbox for everything!)
#
# The default setting will remove everything not used by default.
#	TIMED_EVENT_DATA 	(-2)
#	SERVICE_CHECK_DATA 	(-64)
#	HOST_CHECK_DATA 	(-128)
#
# 67108863-(2+64+128) = 67108863-194 = 67108669

data_processing_options=67108669

# If you are planning to use NagVis you may want to use the following setting:
#
#data_processing_options=4061953
#
# You may have to experiment in your environment and find the best value yourself!


# CONFIG OUTPUT OPTION
# This option determines what types of configuration data the IDO
# NEB module will dump from Icinga.  Values can be OR'ed together.
# Hint: 2 is the preferred value, doing a restart after initial startup.
#
# 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=2



# 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=-2



# 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=1



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

debug_file=/usr/local/icinga/var/idomod.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.

# 100M
max_debug_file_size=100000000


idoutils.cfg

Source code

1
2
3
4
5
6
7
8
9
10
11
12
# ICINGA CONFIG FOR IDOUTILS
#
# In order to have Icinga run the IDOMOD event broker module, you'll need
# to place a file like this into modules/ by default, and include that
# directory in your icinga.cfg

define module{
        module_name     idomod
        module_type     neb
        path            /usr/local/icinga/bin/idomod.o
        args            config_file=/usr/local/icinga/etc/idomod.cfg
	}



Bitte helft mir ich weiß echt nicht mehr weiter :(
:cursing:

Liebe Grüße

dnsmichi

Super Moderator

Posts: 5,976

Birthday: May 30th 1983 (29)

Gender: male

Location: Nürnberg

Occupation: Consultant / Developer beim besten Arbeitgeber der Welt @netways

Number of monitoring servers: Icinga: 4x dev, 10++ prod, Icinga2: 2x dev

Nagios Version: s/nagios/icinga/

Icinga Version: 1.9.0 / GIT

Distributed monitoring: Ja

Redundant monitoring: Ja

Number of hosts: 1000+

Number of services: 15000+

OS: RHEL, Debian, SUSE

Plugin Version: 1.4.16

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

Other Addons: Icinga Web, PNP, check_multi, inGraph, EventDB, LConf

2

Wednesday, January 18th 2012, 6:07pm

und diese idoutils.cfg liegt in etc/modules?

falls ja, wieso inkludierst du dann 2x idomod als event broker modul? in der doku stehts als alternative, aber nicht als aufforderung das doppelt einzutragen. alte methode (icinga.cfg:broker_module) oder neu (module definition).
+++ Icinga / LConf Developer +++ Senior Consultant at []NETWAYS> +++
+++ Icinga 1.9 || Icinga 2 +++ Icinga Support || IRC +++

ceramicx

Beginner

Posts: 20

Birthday: Sep 8th

Number of monitoring servers: 2

Nagios Version: 3.2

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 350

Number of services: >3500

OS: MS Windows Server 2000, 2003, 2008, 2008 R2 / Debian 5.0 Lenny / Windows 2k, XP, Vista, 7

Plugin Version: 1.4.x

3

Wednesday, January 18th 2012, 6:09pm

Jepp liegt sie, da war ich mir nicht sicher, habe aber schon alle Kombinationen ausprobiert, hilft alles nichts :(

dnsmichi

Super Moderator

Posts: 5,976

Birthday: May 30th 1983 (29)

Gender: male

Location: Nürnberg

Occupation: Consultant / Developer beim besten Arbeitgeber der Welt @netways

Number of monitoring servers: Icinga: 4x dev, 10++ prod, Icinga2: 2x dev

Nagios Version: s/nagios/icinga/

Icinga Version: 1.9.0 / GIT

Distributed monitoring: Ja

Redundant monitoring: Ja

Number of hosts: 1000+

Number of services: 15000+

OS: RHEL, Debian, SUSE

Plugin Version: 1.4.16

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

Other Addons: Icinga Web, PNP, check_multi, inGraph, EventDB, LConf

4

Wednesday, January 18th 2012, 6:17pm

entscheide dich fuer eine version und restarte den core. dann gibts auch keine race condition um denselben socket.
+++ Icinga / LConf Developer +++ Senior Consultant at []NETWAYS> +++
+++ Icinga 1.9 || Icinga 2 +++ Icinga Support || IRC +++

ceramicx

Beginner

Posts: 20

Birthday: Sep 8th

Number of monitoring servers: 2

Nagios Version: 3.2

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 350

Number of services: >3500

OS: MS Windows Server 2000, 2003, 2008, 2008 R2 / Debian 5.0 Lenny / Windows 2k, XP, Vista, 7

Plugin Version: 1.4.x

5

Thursday, January 19th 2012, 9:00am

Guten Morgen,

hab ich gemacht, jeweils die Alte und die Neue Methode aber es hilft nichts idomod.debug, ido.sock und idomod.tmp bleiben einfach leer :'( :cursing:

dnsmichi

Super Moderator

Posts: 5,976

Birthday: May 30th 1983 (29)

Gender: male

Location: Nürnberg

Occupation: Consultant / Developer beim besten Arbeitgeber der Welt @netways

Number of monitoring servers: Icinga: 4x dev, 10++ prod, Icinga2: 2x dev

Nagios Version: s/nagios/icinga/

Icinga Version: 1.9.0 / GIT

Distributed monitoring: Ja

Redundant monitoring: Ja

Number of hosts: 1000+

Number of services: 15000+

OS: RHEL, Debian, SUSE

Plugin Version: 1.4.16

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

Other Addons: Icinga Web, PNP, check_multi, inGraph, EventDB, LConf

6

Thursday, January 19th 2012, 10:38am

zeigen.

wie sieht das icinga.log zu dem thema aus - welche idomod wird geladen (log paste).
wie sieht das am fileystem aus (ls)
+++ Icinga / LConf Developer +++ Senior Consultant at []NETWAYS> +++
+++ Icinga 1.9 || Icinga 2 +++ Icinga Support || IRC +++

ceramicx

Beginner

Posts: 20

Birthday: Sep 8th

Number of monitoring servers: 2

Nagios Version: 3.2

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 350

Number of services: >3500

OS: MS Windows Server 2000, 2003, 2008, 2008 R2 / Debian 5.0 Lenny / Windows 2k, XP, Vista, 7

Plugin Version: 1.4.x

7

Friday, January 20th 2012, 10:26am

Hey,

also dieses Problem konnte ich nun lösen, es lag an der nagios.lock die es noch gab. :rolleyes: Diese war vorhanden und idomod.o konnte diese nicht entfernen.
Habe sie manuell entfernt und nun fließen Daten in die Datenbank "icinga" jaaaaaa :). :love:
Dafür hab ich 2 neue Probleme, 1. in der alten Weboberfläche werden sporadisch alte Ergebnisse immer wieder angezeigt, wie kann das denn passieren?
und 2. die neue Oberfläche meldet nach wie vor nur:

Source code

1
[Fri Jan 20 09:23:28 2012] [error] Fetch failed with message SQLSTATE[42P01]: Undefined table: 7 FEHLER:  Relation »objects« existiert nicht

Source code

1
[Fri Jan 20 09:23:27 2012] [debug] QUERY::CREATE Obtain doctrine connection: icinga


Was tun? ;(

Liebe Grüße

Und Edit, ich hab lustigerweise unter /icinga/var/ eine nagios.log und eine icinga.log, warum?

This post has been edited 1 times, last edit by "ceramicx" (Jan 20th 2012, 10:57am)


dnsmichi

Super Moderator

Posts: 5,976

Birthday: May 30th 1983 (29)

Gender: male

Location: Nürnberg

Occupation: Consultant / Developer beim besten Arbeitgeber der Welt @netways

Number of monitoring servers: Icinga: 4x dev, 10++ prod, Icinga2: 2x dev

Nagios Version: s/nagios/icinga/

Icinga Version: 1.9.0 / GIT

Distributed monitoring: Ja

Redundant monitoring: Ja

Number of hosts: 1000+

Number of services: 15000+

OS: RHEL, Debian, SUSE

Plugin Version: 1.4.16

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

Other Addons: Icinga Web, PNP, check_multi, inGraph, EventDB, LConf

8

Friday, January 20th 2012, 1:21pm

ad nagios => icinga

wenn du die nagios.cfg einfach in icinga.cfg umbenannt hast, koennten noch alte bezeichnen vorhanden sein (nagios.lock, nagios.log). wenn du brav warst und nur einzelnen konfigs 1:1 adaptiert hast, wirst du im system noch alte ueberbleibsel finden, die du ausraeumen solltest.

wichtig an dieser stelle - icinga.cfg:lock_file und /etc/init.d/icinga:IcingaRunFile muessen gleich lauten.

ad web
der sql error laesst 3 schluesse zu

* encoding kaputt, files wurden mit windows (dos) gespeichert, und auf die linuxkiste (unix) scp'd und da ging dann das encoding schief
* das schema ist nicht importiert.
* das schema ist da, aber die table objects gibts nicht

sicher dass icinga-web seine eigene datenbank verwendet, sowie als datenbackend die idoutils db konfiguriert ist? vgl databases.xml https://wiki.icinga.org/display/howtos/databases.xml
+++ Icinga / LConf Developer +++ Senior Consultant at []NETWAYS> +++
+++ Icinga 1.9 || Icinga 2 +++ Icinga Support || IRC +++

ceramicx

Beginner

Posts: 20

Birthday: Sep 8th

Number of monitoring servers: 2

Nagios Version: 3.2

Distributed monitoring: Nein

Redundant monitoring: Nein

Number of hosts: 350

Number of services: >3500

OS: MS Windows Server 2000, 2003, 2008, 2008 R2 / Debian 5.0 Lenny / Windows 2k, XP, Vista, 7

Plugin Version: 1.4.x

9

Monday, January 23rd 2012, 10:29am

Also meine Database.xml sieht jetzt so aus:

Source code

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
<?xml version="1.0" encoding="UTF-8"?>
<!--
    databases.xml
    Defines which databases to use to store internal icinga-data and where to request icinga monitoring status from
-->

	
<databases xmlns:db="http://agavi.org/agavi/config/parts/databases/1.0" xmlns:ae="http://agavi.org/agavi/config/global/envelope/1.0">


    <!-- 
    Overwrite the icinga-web database (where users, roles, views, etc are stored 
    -->
    
    <db:database name="icinga_web" class="AppKitDoctrineDatabase">
         <ae:parameter name="dsn">pgsql://icinga_web:icinga_web@localhost:5432/icinga_web</ae:parameter>

        <ae:parameter name="charset">utf8</ae:parameter>
        <ae:parameter name="manager_attributes">
            <ae:parameter name="Doctrine_Core::ATTR_MODEL_LOADING">CONSERVATIVE</ae:parameter>
        </ae:parameter>
        
        <ae:parameter name="load_models">%core.module_dir%/AppKit/lib/database/models/generated</ae:parameter>
        <ae:parameter name="models_directory">%core.module_dir%/AppKit/lib/database/models</ae:parameter>				
        <ae:parameter name="date_format"><![CDATA[YYYY-MM-DD HH24:MI:SS]]></ae:parameter>
    

        <ae:parameter name="caching">
            <ae:parameter name="enabled">false</ae:parameter>
            <ae:parameter name="driver">apc</ae:parameter>
            <ae:parameter name="use_query_cache">true</ae:parameter>
            <ae:parameter name="use_result_cache">true</ae:parameter>
            <ae:parameter name="result_cache_lifespan">60</ae:parameter>
        </ae:parameter>		
        
    </db:database>
    

    <!-- 
        Overwrite the default database conneciton for icinga data retrieval
        Make sure to use IcingaDoctrineDatabase, otherwise the use_retained parameter will be ignored
        EXAMPLE (oracle needs icingaOracle as the db driver) 
    -->
    
    <db:database xmlns="http://agavi.org/agavi/config/parts/databases/1.0" name="icinga" class="IcingaDoctrineDatabase">
        <ae:parameter name="dsn">pgsql://icinga:icinga@localhost:5432/icinga</ae:parameter>
        <ae:parameter name="prefix">icinga_</ae:parameter>
        <ae:parameter name="charset">utf8</ae:parameter>
        <ae:parameter name="use_retained">true</ae:parameter>
        <ae:parameter name="date_format"><![CDATA[YYYY-MM-DD HH24:MI:SS]]></ae:parameter>
        <ae:parameter name="manager_attributes">
            <ae:parameter name="Doctrine_Core::ATTR_MODEL_LOADING">CONSERVATIVE</ae:parameter>
        </ae:parameter>
        <ae:parameter name="load_models">%core.module_dir%/Api/lib/database/models/generated</ae:parameter>
        <ae:parameter name="models_directory">%core.module_dir%/Api/lib/database/models</ae:parameter>				
        <ae:parameter name="caching">  
            <ae:parameter name="enabled">false</ae:parameter>
            <ae:parameter name="driver">apc</ae:parameter>
            <ae:parameter name="use_query_cache">true</ae:parameter>
        </ae:parameter>

    </db:database>

    
    
</databases>


Bearbeitet habe ich sie immer unter Debian also schließe ich das Encoding mal aus. Habe eben noch einen Fehler gefunden, vor meinen db Definitionen waren noch die <-- Auskommentierzeichen *facepalm* :rolleyes:
Danach hab ich die entfernt und Apache reloaded und Icinga neugestartet, hilft aber nix der selbe Fehler kommt immer noch.

Meine DB sieht so aus:

Source code

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
Tabelle Besitzer Geschätzte Anzahl von Datensätzen
 icinga_acknowledgements icinga  0 
 icinga_commands icinga  108 
 icinga_commenthistory icinga  195 
 icinga_comments icinga  114 
 icinga_configfiles icinga  0 
 icinga_configfilevariables icinga  494 
 icinga_conninfo icinga  0 
 icinga_contact_addresses icinga  0 
 icinga_contact_notificationcommands icinga  228 
 icinga_contactgroup_members icinga  0 
 icinga_contactgroups icinga  0 
 icinga_contactnotificationmethods icinga  96 
 icinga_contactnotifications icinga  99 
 icinga_contacts icinga  0 
 icinga_contactstatus icinga  0 
 icinga_customvariables icinga  0 
 icinga_customvariablestatus icinga  0 
 icinga_dbversion icinga  0 
 icinga_downtimehistory icinga  0 
 icinga_eventhandlers icinga  0 
 icinga_externalcommands icinga  89531 
 icinga_flappinghistory icinga  110 
 icinga_host_contactgroups icinga  246 
 icinga_host_contacts icinga  384 
 icinga_host_parenthosts icinga  259 
 icinga_hostchecks icinga  0 
 icinga_hostdependencies icinga  0 
 icinga_hostescalation_contactgroups icinga  213 
 icinga_hostescalation_contacts icinga  142 
 icinga_hostescalations icinga  180 
 icinga_hostgroup_members icinga  408 
 icinga_hostgroups icinga  0 
 icinga_hosts icinga  397 
 icinga_hoststatus icinga  205 
 icinga_instances icinga  0 
 icinga_logentries icinga  1000042 
 icinga_notifications icinga  311 
 icinga_objects icinga  3845 
 icinga_processevents icinga  0 
 icinga_programstatus icinga  0 
 icinga_runtimevariables icinga  0 
 icinga_scheduleddowntime icinga  0 
 icinga_service_contactgroups icinga  3685 
 icinga_service_contacts icinga  1473 
 icinga_servicechecks icinga  0 
 icinga_servicedependencies icinga  0 
 icinga_serviceescalation_contactgroups icinga  1726 
 icinga_serviceescalation_contacts icinga  147 
 icinga_serviceescalations icinga  1678 
 icinga_servicegroup_members icinga  3509 
 icinga_servicegroups icinga  0 
 icinga_services icinga  3276 
 icinga_servicestatus icinga  3275 
 icinga_slahistory icinga  0 
 icinga_statehistory icinga  4292 
 icinga_systemcommands icinga  11674 
 icinga_timedeventqueue icinga  0 
 icinga_timedevents icinga  0 
 icinga_timeperiod_timeranges icinga  0 
 icinga_timeperiods icinga  0

dnsmichi

Super Moderator

Posts: 5,976

Birthday: May 30th 1983 (29)

Gender: male

Location: Nürnberg

Occupation: Consultant / Developer beim besten Arbeitgeber der Welt @netways

Number of monitoring servers: Icinga: 4x dev, 10++ prod, Icinga2: 2x dev

Nagios Version: s/nagios/icinga/

Icinga Version: 1.9.0 / GIT

Distributed monitoring: Ja

Redundant monitoring: Ja

Number of hosts: 1000+

Number of services: 15000+

OS: RHEL, Debian, SUSE

Plugin Version: 1.4.16

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

Other Addons: Icinga Web, PNP, check_multi, inGraph, EventDB, LConf

10

Monday, January 23rd 2012, 2:20pm

wenn du xmls von icinga-web configs editierst, musst du den cache leeren. die docs und howtos sind mittlerweile vollgepflastert mit diesem hinweis.
+++ Icinga / LConf Developer +++ Senior Consultant at []NETWAYS> +++
+++ Icinga 1.9 || Icinga 2 +++ Icinga Support || IRC +++