Hi Michael, In var/log/icinga2 are any error... the logging was stopped and the only message was the segfault in dmesg. I will do the upgrade to the last stable version.
Many Thanks, Christian Am Dienstag, 13. Juni 2017 schrieb : > Send icinga-users mailing list submissions to > icinga-users@lists.icinga.org <javascript:;> > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.icinga.org/mailman/listinfo/icinga-users > or, via email, send a message with subject or body 'help' to > icinga-users-requ...@lists.icinga.org <javascript:;> > > You can reach the person managing the list at > icinga-users-ow...@lists.icinga.org <javascript:;> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of icinga-users digest..." > > > Today's Topics: > > 1. Renaming a host while keeping history in graphana / influxdb > (Alexander Reichle-Schmehl) > 2. segfault in one icinga2 node (Christian Moreno Moreno) > 3. Re: segfault in one icinga2 node (Michael Friedrich) > 4. Re: Renaming a host while keeping history in graphana / > influxdb (Michael Friedrich) > 5. Re: Renaming a host while keeping history in graphana / > influxdb (Alexander Reichle-Schmehl) > 6. icinga2 v. 2.6.3: downtime and acknowledgement lost upon > reload or restart - HA config (Diana Scannicchio) > 7. Re: icinga2 v. 2.6.3: downtime and acknowledgement lost upon > reload or restart - HA config (Michael Friedrich) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 12 Jun 2017 14:31:17 +0200 > From: Alexander Reichle-Schmehl <alexan...@alphamar.org <javascript:;>> > To: icinga-users@lists.icinga.org <javascript:;> > Subject: [icinga-users] Renaming a host while keeping history in > graphana / influxdb > Message-ID: <02a22837327145c8499bba541319b...@ssl.alphamar.org > <javascript:;>> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi! > > We are currently using Icinga 1 (migration to Icinga2 is being prepared) > with graphana and influx to visualize performance data. > > We used pnp4nagios for that, but where never happy with the performance. > Since the migration the performance is good, but we haven't figured out, > how we can rename a host object and still keep the history of the > performance data. > > We have for example several environmental sensors in our data centers. > As they where installed by two different people, they where named in > different ways. After two years, we now settled to rename the hosts to > avoid further confusion. Renaming the host in Icinga is trivial, but > what do we have to do with our influxdb? > > Granted, not strictly an Icinga questions. I'll gladly accept any > pointers to existing documentation. > > Best regards, > Alexander > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 13 Jun 2017 08:50:12 +0200 > From: Christian Moreno Moreno <christian.mor...@idealo.de <javascript:;>> > To: icinga-users@lists.icinga.org <javascript:;> > Subject: [icinga-users] segfault in one icinga2 node > Message-ID: > <CAHCD4S_Uz4UUbm+= > 3vxxw1gb2wfmnf+vgt7aipttdunuzvw...@mail.gmail.com <javascript:;>> > Content-Type: text/plain; charset="utf-8" > > Hi, > > We have one cluster with some Zones and one of the nodes got the last 2-3 > Weeks the next error: > > icinga2[11969]: segfault at 0 ip 00002b20a90fbaa3 sp 00002b20aa60db50 error > 4 in libicinga.so.2.6.1[2b20a9041000+2a1000] > > This node hat one load of more that 100% (not the rest of the nodes of the > same Zone) and was necesary one stop&start. > Icinga Cluster check were critical because the rest of the nodes cant > connect to this one. > > > We got this Problem only on this node, until now not in any other. > > Details: > Icinga2: (version: r2.6.1-1) > Debian 7.11 > > *all nodes have the same icinga2 Version and same HW/SO. > > Has someone one idea abot the reason? > > Regards, > Christian > > > Christian Moreno Moreno > System Engineer Offers > > idealo internet GmbH > Ritterstra?e 11 > 10969 Berlin, Deutschland > Tel.: +49 (0)30 40 30 10 33 > Fax: +49 (0)30 221 94 33 - 21 > E-Mail: christian.mor...@idealo.de <javascript:;> > Gesch?ftsf?hrer: > Dr. Albrecht von Sonntag, Dr. Philipp-Christopher Peitsch > HRB 76749 ? Amtsgericht Berlin-Charlottenburg > [image: idealo Logo] <http://www.idealo.de/> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.icinga.org/pipermail/icinga-users/ > attachments/20170613/5f11295a/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Tue, 13 Jun 2017 09:15:30 +0200 > From: Michael Friedrich <michael.friedr...@icinga.com <javascript:;>> > To: Icinga User's Corner <icinga-users@lists.icinga.org <javascript:;>> > Subject: Re: [icinga-users] segfault in one icinga2 node > Message-ID: <40f06028-9484-48c9-8428-ae57e3c2e...@icinga.com > <javascript:;>> > Content-Type: text/plain; charset=us-ascii > > > > On 13. Jun 2017, at 08:50, Christian Moreno Moreno < > christian.mor...@idealo.de <javascript:;>> wrote: > > > > Hi, > > > > We have one cluster with some Zones and one of the nodes got the last > 2-3 Weeks the next error: > > > > icinga2[11969]: segfault at 0 ip 00002b20a90fbaa3 sp 00002b20aa60db50 > error 4 in libicinga.so.2.6.1[2b20a9041000+2a1000] > > Any logs indicated what went wrong in /var/log/icinga2? > > > > > This node hat one load of more that 100% (not the rest of the nodes of > the same Zone) and was necesary one stop&start. > > Icinga Cluster check were critical because the rest of the nodes cant > connect to this one. > > > > > > We got this Problem only on this node, until now not in any other. > > > > Details: > > Icinga2: (version: r2.6.1-1) > > Debian 7.11 > > 2.6.1 is known to have some crash bugs. Try it with the latest stable > release. > > Kind regards, > Michael > > > > ------------------------------ > > Message: 4 > Date: Tue, 13 Jun 2017 09:19:40 +0200 > From: Michael Friedrich <michael.friedr...@icinga.com <javascript:;>> > To: Icinga User's Corner <icinga-users@lists.icinga.org <javascript:;>> > Subject: Re: [icinga-users] Renaming a host while keeping history in > graphana / influxdb > Message-ID: <6dadaf51-9764-4d34-ad04-fccb2cdc5...@icinga.com > <javascript:;>> > Content-Type: text/plain; charset=utf-8 > > > > On 12. Jun 2017, at 14:31, Alexander Reichle-Schmehl < > alexan...@alphamar.org <javascript:;>> wrote: > > > > Hi! > > > > We are currently using Icinga 1 (migration to Icinga2 is being prepared) > with graphana and influx to visualize performance data. > > > > We used pnp4nagios for that, but where never happy with the performance. > Since the migration the performance is good, but we haven't figured out, > how we can rename a host object and still keep the history of the > performance data. > > > > We have for example several environmental sensors in our data centers. > As they where installed by two different people, they where named in > different ways. After two years, we now settled to rename the hosts to > avoid further confusion. Renaming the host in Icinga is trivial, but what > do we have to do with our influxdb? > > > > Granted, not strictly an Icinga questions. I'll gladly accept any > pointers to existing documentation. > > ?influxdb rename measurement? leads to these feature request:s > > https://github.com/influxdata/influxdb/issues/4155 > https://github.com/influxdata/influxdb/issues/4156 > > The mentioned workarounds in the issue do not seem to work, as they seem > to reset all data to the current timestamp (don?t try this without a > backup, funny). > > Dunno what else to try. In terms of Graphite and Whisper, or PNP it is > fairly easy with file storage renaming. But here with InfluxDB .. oh well. > > Kind regards, > Michael > > > > > > Best regards, > > Alexander > > > > > > > > _______________________________________________ > > icinga-users mailing list > > icinga-users@lists.icinga.org <javascript:;> > > https://lists.icinga.org/mailman/listinfo/icinga-users > > > > ------------------------------ > > Message: 5 > Date: Tue, 13 Jun 2017 10:20:46 +0200 > From: Alexander Reichle-Schmehl <alexan...@alphamar.org <javascript:;>> > To: Icinga User's Corner <icinga-users@lists.icinga.org <javascript:;>> > Subject: Re: [icinga-users] Renaming a host while keeping history in > graphana / influxdb > Message-ID: <9c5b3d4752f9fd89352be55cc28e6...@ssl.alphamar.org > <javascript:;>> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Michael, > > Am 2017-06-13 09:19, schrieb Michael Friedrich: > > > ?influxdb rename measurement? leads to these feature request:s > > > > https://github.com/influxdata/influxdb/issues/4155 > > https://github.com/influxdata/influxdb/issues/4156 > > Your google foo seems to be better than mine. Many thanks! > > At least it clarifies, that it currently is not working out of the box. > Which means we can stop searching and test the mentioned workaround. > > Thanks again, > Alexander > > > > ------------------------------ > > Message: 6 > Date: Tue, 13 Jun 2017 10:57:06 +0200 > From: Diana Scannicchio <diana.scannicc...@gmail.com <javascript:;>> > To: icinga-users@lists.icinga.org <javascript:;> > Subject: [icinga-users] icinga2 v. 2.6.3: downtime and acknowledgement > lost upon reload or restart - HA config > Message-ID: <4f4e9a48-b351-4fcc-b6c4-979fd4cf6...@gmail.com <javascript:;> > > > Content-Type: text/plain; charset=windows-1252 > > Dear experts, > I am running Icinga2 version 2.6.3 in high availability mode using two > servers. > Since the previous version when reloading or restarting the icinga2 > service all the downtime or acknowledgemnt that we had set are lost. > This is of course affecting normal operations. > > The OS version is SLC 6.8 (kernel 2.6.32-642.15.1.el6.x86_6) see below > more info. > The icinga2web version used is 2.4.1. > > The files related to the downtime are for example written in > /var/lib/icinga2/api/packages/_api/conf.d/downtimes > but is seems they are not reloaded after a restart/reload of the service > and consequently we have to set them again. > > Would you have any hints about where/what to look or how to fix? > The issue appears only on the system configured in high availability, > while on a single standalone server with same icinga2 version (and same > nodes and checks) the downtime and acknowledgement survive a service reload > or restart. > > Thank you for any help or suggestion you could provide and best regards, > > Diana > > > - > Diana Scannicchio > University of California, Irvine > ATLAS TDAQ SysAdmin group > Mobile: +41 75 411 5855 > Office: +41 22 76 75240 > OnCall: 164851 > > [root@icinga-20 icinga2]# icinga2 object list --type Endpoint > Object 'icinga-21.cern.ch' of type 'Endpoint': > % declared in '/etc/icinga2/zones.conf', lines 18:1-18:42 > * __name = "icinga-21.cern.ch" > * host = "icinga-21.cern.ch" > % = modified in '/etc/icinga2/zones.conf', lines 19:5-19:37 > * log_duration = 86400 > * name = "icinga-21.cern.ch" > * package = "_etc" > * port = "5665" > % = modified in '/etc/icinga2/zones.conf', lines 20:5-20:17 > * templates = [ "icinga-21.cern.ch" ] > % = modified in '/etc/icinga2/zones.conf', lines 18:1-18:42 > * type = "Endpoint" > * zone = "" > > Object 'icinga-20.cern.ch' of type 'Endpoint': > % declared in '/etc/icinga2/zones.conf', lines 13:1-13:42 > * __name = "icinga-20.cern.ch" > * host = "icinga-20.cern.ch" > % = modified in '/etc/icinga2/zones.conf', lines 14:5-14:37 > * log_duration = 86400 > * name = "icinga-20.cern.ch" > * package = "_etc" > * port = "5665" > % = modified in '/etc/icinga2/zones.conf', lines 15:5-15:17 > * templates = [ "icinga-20.cern.ch" ] > % = modified in '/etc/icinga2/zones.conf', lines 13:1-13:42 > * type = "Endpoint" > * zone = ?" > > > [root@icinga-20 icinga2]# icinga2 --version > icinga2 - The Icinga 2 network monitoring daemon (version: v2.6.3) > > Copyright (c) 2012-2017 Icinga Development Team (https://www.icinga.com/) > License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl2. > html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > > Application information: > Installation root: /usr > Sysconf directory: /etc > Run directory: /var/run > Local state directory: /var > Package data directory: /usr/share/icinga2 > State path: /var/lib/icinga2/icinga2.state > Modified attributes path: /var/lib/icinga2/modified-attributes.conf > Objects path: /var/cache/icinga2/icinga2.debug > Vars path: /var/cache/icinga2/icinga2.vars > PID path: /var/run/icinga2/icinga2.pid > > System information: > Platform: Scientific Linux CERN SLC > Platform version: 6.8 (Carbon) > Kernel: Linux > Kernel version: 2.6.32-642.15.1.el6.x86_64 > Architecture: x86_64 > > Build information: > Compiler: GNU 4.8.2 > Build host: e6e3648876de > > > > [root@icinga-20 icinga2]# icinga2 feature list > Disabled features: debuglog gelf graphite influxdb livestatus opentsdb > perfdata syslog > Enabled features: api checker command compatlog ido-mysql mainlog > notification statusdata > > > > > > > > > > > > > > ------------------------------ > > Message: 7 > Date: Tue, 13 Jun 2017 11:21:58 +0200 > From: Michael Friedrich <michael.friedr...@icinga.com <javascript:;>> > To: Icinga User's Corner <icinga-users@lists.icinga.org <javascript:;>> > Subject: Re: [icinga-users] icinga2 v. 2.6.3: downtime and > acknowledgement lost upon reload or restart - HA config > Message-ID: <8e952b84-3c92-4e66-93b1-1d1ddaa13...@icinga.com > <javascript:;>> > Content-Type: text/plain; charset=utf-8 > > > > On 13. Jun 2017, at 10:57, Diana Scannicchio < > diana.scannicc...@gmail.com <javascript:;>> wrote: > > > > Dear experts, > > I am running Icinga2 version 2.6.3 in high availability mode using two > servers. > > Since the previous version when reloading or restarting the icinga2 > service all the downtime or acknowledgemnt that we had set are lost. > > This is of course affecting normal operations. > > > > The OS version is SLC 6.8 (kernel 2.6.32-642.15.1.el6.x86_6) see below > more info. > > The icinga2web version used is 2.4.1. > > > > The files related to the downtime are for example written in > > /var/lib/icinga2/api/packages/_api/conf.d/downtimes > > but is seems they are not reloaded after a restart/reload of the service > and consequently we have to set them again. > > Can you verify that the corresponding directory is loaded during > startup/config validation, i.e. > > icinga2 daemon -C -x notice | grep ?conf.d/downtimes? > > The acknowledgements are stored within /var/lib/icinga2/icinga2.state in a > different location, is that file actively updated by the icinga2 daemon > itself? > > Pick an example host and service, and illustrate the work flow on > > - create a downtime > - query it via API on /v1/objects/downtimes > - restart/reload > - icinga2 daemon -C -x notice | grep ?<hostname>? > - query via API /v1/objects/downtimes - is it there? > > Similar thing for acknowledgements, but querying the URL endpoint > /v1/objects/services and checking for ?acknowledgement? as attribute. > > Kind regards, > Michael > > > > > > Would you have any hints about where/what to look or how to fix? > > The issue appears only on the system configured in high availability, > while on a single standalone server with same icinga2 version (and same > nodes and checks) the downtime and acknowledgement survive a service reload > or restart. > > > > Thank you for any help or suggestion you could provide and best regards, > > > > Diana > > > > > > - > > Diana Scannicchio > > University of California, Irvine > > ATLAS TDAQ SysAdmin group > > Mobile: +41 75 411 5855 > > Office: +41 22 76 75240 > > OnCall: 164851 > > > > [root@icinga-20 icinga2]# icinga2 object list --type Endpoint > > Object 'icinga-21.cern.ch' of type 'Endpoint': > > % declared in '/etc/icinga2/zones.conf', lines 18:1-18:42 > > * __name = "icinga-21.cern.ch" > > * host = "icinga-21.cern.ch" > > % = modified in '/etc/icinga2/zones.conf', lines 19:5-19:37 > > * log_duration = 86400 > > * name = "icinga-21.cern.ch" > > * package = "_etc" > > * port = "5665" > > % = modified in '/etc/icinga2/zones.conf', lines 20:5-20:17 > > * templates = [ "icinga-21.cern.ch" ] > > % = modified in '/etc/icinga2/zones.conf', lines 18:1-18:42 > > * type = "Endpoint" > > * zone = "" > > > > Object 'icinga-20.cern.ch' of type 'Endpoint': > > % declared in '/etc/icinga2/zones.conf', lines 13:1-13:42 > > * __name = "icinga-20.cern.ch" > > * host = "icinga-20.cern.ch" > > % = modified in '/etc/icinga2/zones.conf', lines 14:5-14:37 > > * log_duration = 86400 > > * name = "icinga-20.cern.ch" > > * package = "_etc" > > * port = "5665" > > % = modified in '/etc/icinga2/zones.conf', lines 15:5-15:17 > > * templates = [ "icinga-20.cern.ch" ] > > % = modified in '/etc/icinga2/zones.conf', lines 13:1-13:42 > > * type = "Endpoint" > > * zone = ?" > > > > > > [root@icinga-20 icinga2]# icinga2 --version > > icinga2 - The Icinga 2 network monitoring daemon (version: v2.6.3) > > > > Copyright (c) 2012-2017 Icinga Development Team (https://www.icinga.com/ > ) > > License GPLv2+: GNU GPL version 2 or later < > http://gnu.org/licenses/gpl2.html> > > This is free software: you are free to change and redistribute it. > > There is NO WARRANTY, to the extent permitted by law. > > > > Application information: > > Installation root: /usr > > Sysconf directory: /etc > > Run directory: /var/run > > Local state directory: /var > > Package data directory: /usr/share/icinga2 > > State path: /var/lib/icinga2/icinga2.state > > Modified attributes path: /var/lib/icinga2/modified-attributes.conf > > Objects path: /var/cache/icinga2/icinga2.debug > > Vars path: /var/cache/icinga2/icinga2.vars > > PID path: /var/run/icinga2/icinga2.pid > > > > System information: > > Platform: Scientific Linux CERN SLC > > Platform version: 6.8 (Carbon) > > Kernel: Linux > > Kernel version: 2.6.32-642.15.1.el6.x86_64 > > Architecture: x86_64 > > > > Build information: > > Compiler: GNU 4.8.2 > > Build host: e6e3648876de > > > > > > > > [root@icinga-20 icinga2]# icinga2 feature list > > Disabled features: debuglog gelf graphite influxdb livestatus opentsdb > perfdata syslog > > Enabled features: api checker command compatlog ido-mysql mainlog > notification statusdata > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > icinga-users mailing list > > icinga-users@lists.icinga.org <javascript:;> > > https://lists.icinga.org/mailman/listinfo/icinga-users > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org <javascript:;> > https://lists.icinga.org/mailman/listinfo/icinga-users > > > ------------------------------ > > End of icinga-users Digest, Vol 42, Issue 5 > ******************************************* > -- Christian Moreno Moreno System Engineer Offers idealo internet GmbH Ritterstraße 11 10969 Berlin, Deutschland Tel.: +49 (0)30 40 30 10 33 Fax: +49 (0)30 221 94 33 - 21 E-Mail: christian.mor...@idealo.de Geschäftsführer: Dr. Albrecht von Sonntag, Dr. Philipp-Christopher Peitsch HRB 76749 – Amtsgericht Berlin-Charlottenburg [image: idealo Logo] <http://www.idealo.de/>
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
