Nicolás del Río | 26 Mar 15:57 2015
Picon

Log Parser or REST API

Hello, I'm trying to access compat.log from a PHP application running on the same server that Iginga2 runs. I did not find any REST interface to get compat.log into my php app. Anybody knows how can I do?
Another possibility is to read the compat.log file. Anybody knows a good parser written in php?

Thanks!
_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
Markus Bettsteller | 18 Feb 08:44 2015
Picon

Icingaweb2 LDAP "Critical extension is unavailable"

Hi,
I have an issue with the LDAP authentication and IcingaWeb2 (IcingaWeb1
is working fine, just the version"2" is giving me trouble). There is a
LDAP directory used here that seems to have an extension missing that is
being used by the icingaweb2 code. Any pointers on what extension is
missing is very welcome, so I can request it at the hosters servcice desk.

Error message:
Feb 18 07:59:20 XXXXXXXXXXXX icingaweb2[14306]:
Icinga\Exception\AuthenticationException in
/var/www/icingaweb2/library/Icinga/Authentication/Backend/LdapUserBackend.php:180
with message: Authentication against backend "XX" not possible. <-
Icinga\Exception\AuthenticationException in
/var/www/icingaweb2/library/Icinga/Authentication/Backend/LdapUserBackend.php:84
with message: Connection not possible. <- Icinga\Protocol\Ldap\Exception
in /var/www/icingaweb2/library/Icinga/Protocol/Ldap/Connection.php:378
with message: LDAP query "(objectClass=inetorgperson)" (root
dc=XXXXXXXXXXXXXXXX,dc=XXX) failed: Critical extension is unavailable

It is breaking at the exception point in this code part:

        $base = $query->hasBase() ? $query->getBase() : $this->root_dn;
        $results =  <at> ldap_search(
            $this->ds,
            $base,
            $query->create(),
            empty($fields) ? $query->listFields() : $fields,
            0, // Attributes and values
            $query->hasLimit() ? $query->getOffset() +
$query->getLimit() : 0 // No limit - at least where possible
        );

        if ($results === false) {
            if (ldap_errno($this->ds) === self::LDAP_NO_SUCH_OBJECT) {
                return false;
            }
            throw new LdapException(
                sprintf(
                    'LDAP query "%s" (root %s) failed: %s',
                    $query->create(),
                    $this->root_dn,
                    ldap_error($this->ds)
                )
            );
        }

I also did an ldapsearch from the machine hosting the Icingaweb2 and it
is working fine:
ldapsearch -D "uid=XXXXXX,ou=People,dc=XXXXXXXXXXXXXXXXXXXX,dc=com" -w
XXXXXXXXXXXXXXXX -p 389 -h XXXXXXXXXXXXXXXXXXXX -b
"dc=XXXXXXXXXXXXXXXXXXXXX,dc=com" -s sub "(objectClass=inetorgperson)"

# extended LDIF
#
# LDAPv3
# base <dc=XXXXXXXXXXXXXXXXXXXX,dc=com> with scope subtree
# filter: (objectClass=inetorgperson)
# requesting: ALL
#

# XXXXXX, People, XXXXXXXXXXXXXXXXXXXX
dn: uid=XXXXXX, ou=People,dc=XXXXXXXXXXXXXXXXXXXX,dc=com
mobile: 1727300543
cn: letzas
sn: Letzas
objectClass: inetorgperson
objectClass: organizationalPerson
objectClass: person
objectClass: top
givenName: XXX
displayName: XXXXXXXXXXXXX
uid: XXXXXX
mail: XXX
.
.
.
.
.
# search result
search: 2
result: 0 Success

# numResponses: 95
# numEntries: 94

LDIF of the Server Capabilities:

enabledSSLCiphers: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
enabledSSLCiphers: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
enabledSSLCiphers: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
enabledSSLCiphers: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA
enabledSSLCiphers: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
enabledSSLCiphers: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
enabledSSLCiphers: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
enabledSSLCiphers: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
enabledSSLCiphers: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
enabledSSLCiphers: TLS_RSA_WITH_AES_256_CBC_SHA
enabledSSLCiphers: TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
enabledSSLCiphers: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
enabledSSLCiphers: TLS_ECDHE_RSA_WITH_RC4_128_SHA
enabledSSLCiphers: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
enabledSSLCiphers: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
enabledSSLCiphers: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA
enabledSSLCiphers: TLS_DHE_DSS_WITH_RC4_128_SHA
enabledSSLCiphers: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
enabledSSLCiphers: TLS_DHE_DSS_WITH_AES_128_CBC_SHA
enabledSSLCiphers: TLS_ECDH_RSA_WITH_RC4_128_SHA
enabledSSLCiphers: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
enabledSSLCiphers: TLS_ECDH_ECDSA_WITH_RC4_128_SHA
enabledSSLCiphers: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
enabledSSLCiphers: TLS_RSA_WITH_SEED_CBC_SHA
enabledSSLCiphers: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
enabledSSLCiphers: SSL_RSA_WITH_RC4_128_MD5
enabledSSLCiphers: SSL_RSA_WITH_RC4_128_SHA
enabledSSLCiphers: TLS_RSA_WITH_AES_128_CBC_SHA
enabledSSLCiphers: TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: SSL_RSA_WITH_3DES_EDE_CBC_SHA
enabledSSLCiphers: SSL_DHE_RSA_WITH_DES_CBC_SHA
enabledSSLCiphers: SSL_DHE_DSS_WITH_DES_CBC_SHA
enabledSSLCiphers: SSL_RSA_FIPS_WITH_DES_CBC_SHA
enabledSSLCiphers: SSL_RSA_WITH_DES_CBC_SHA
enabledSSLCiphers: TLS_RSA_EXPORT1024_WITH_RC4_56_SHA
enabledSSLCiphers: TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA
enabledSSLCiphers: SSL_RSA_EXPORT_WITH_RC4_40_MD5
enabledSSLCiphers: SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
enabledSSLCiphers: SSL_CK_RC4_128_WITH_MD5
enabledSSLCiphers: SSL_CK_RC2_128_CBC_WITH_MD5
enabledSSLCiphers: SSL_CK_DES_192_EDE3_CBC_WITH_MD5
enabledSSLCiphers: SSL_CK_DES_64_CBC_WITH_MD5
enabledSSLCiphers: SSL_CK_RC4_128_EXPORT40_WITH_MD5
enabledSSLCiphers: SSL_CK_RC2_128_CBC_EXPORT40_WITH_MD5
supportedControl: 2.16.840.1.113730.3.4.2
supportedControl: 2.16.840.1.113730.3.4.3
supportedControl: 2.16.840.1.113730.3.4.4
supportedControl: 2.16.840.1.113730.3.4.5
supportedControl: 1.2.840.113556.1.4.473
supportedControl: 2.16.840.1.113730.3.4.9
supportedControl: 2.16.840.1.113730.3.4.16
supportedControl: 2.16.840.1.113730.3.4.15
supportedControl: 2.16.840.1.113730.3.4.17
supportedControl: 2.16.840.1.113730.3.4.19
supportedControl: 1.3.6.1.4.1.42.2.27.9.5.2
supportedControl: 1.3.6.1.4.1.42.2.27.9.5.6
supportedControl: 1.3.6.1.4.1.42.2.27.9.5.8
supportedControl: 1.3.6.1.4.1.42.2.27.8.5.1
supportedControl: 2.16.840.1.113730.3.4.14
supportedControl: 1.3.6.1.4.1.1466.29539.12
supportedControl: 2.16.840.1.113730.3.4.12
supportedControl: 2.16.840.1.113730.3.4.18
supportedControl: 2.16.840.1.113730.3.4.13
supportedExtension: 2.16.840.1.113730.3.5.7
supportedExtension: 2.16.840.1.113730.3.5.8
supportedExtension: 1.3.6.1.4.1.4203.1.11.1
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.25
supportedExtension: 2.16.840.1.113730.3.5.3
supportedExtension: 2.16.840.1.113730.3.5.5
supportedExtension: 2.16.840.1.113730.3.5.6
supportedExtension: 2.16.840.1.113730.3.5.4
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.1
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.2
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.3
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.4
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.5
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.6
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.7
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.8
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.9
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.23
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.11
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.12
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.13
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.14
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.15
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.16
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.17
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.18
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.19
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.21
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.22
supportedExtension: 1.3.6.1.4.1.42.2.27.9.6.24
supportedExtension: 1.3.6.1.4.1.1466.20037
supportedExtension: 1.3.6.1.4.1.4203.1.11.3
supportedSSLCiphers: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
supportedSSLCiphers: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
supportedSSLCiphers: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA
supportedSSLCiphers: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA
supportedSSLCiphers: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
supportedSSLCiphers: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
supportedSSLCiphers: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
supportedSSLCiphers: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
supportedSSLCiphers: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA
supportedSSLCiphers: TLS_RSA_WITH_AES_256_CBC_SHA
supportedSSLCiphers: TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
supportedSSLCiphers: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
supportedSSLCiphers: TLS_ECDHE_RSA_WITH_RC4_128_SHA
supportedSSLCiphers: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
supportedSSLCiphers: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
supportedSSLCiphers: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA
supportedSSLCiphers: TLS_DHE_DSS_WITH_RC4_128_SHA
supportedSSLCiphers: TLS_DHE_RSA_WITH_AES_128_CBC_SHA
supportedSSLCiphers: TLS_DHE_DSS_WITH_AES_128_CBC_SHA
supportedSSLCiphers: TLS_ECDH_RSA_WITH_RC4_128_SHA
supportedSSLCiphers: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
supportedSSLCiphers: TLS_ECDH_ECDSA_WITH_RC4_128_SHA
supportedSSLCiphers: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
supportedSSLCiphers: TLS_RSA_WITH_SEED_CBC_SHA
supportedSSLCiphers: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA
supportedSSLCiphers: SSL_RSA_WITH_RC4_128_MD5
supportedSSLCiphers: SSL_RSA_WITH_RC4_128_SHA
supportedSSLCiphers: TLS_RSA_WITH_AES_128_CBC_SHA
supportedSSLCiphers: TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: SSL_RSA_WITH_3DES_EDE_CBC_SHA
supportedSSLCiphers: SSL_DHE_RSA_WITH_DES_CBC_SHA
supportedSSLCiphers: SSL_DHE_DSS_WITH_DES_CBC_SHA
supportedSSLCiphers: SSL_RSA_FIPS_WITH_DES_CBC_SHA
supportedSSLCiphers: SSL_RSA_WITH_DES_CBC_SHA
supportedSSLCiphers: TLS_RSA_EXPORT1024_WITH_RC4_56_SHA
supportedSSLCiphers: TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA
supportedSSLCiphers: SSL_RSA_EXPORT_WITH_RC4_40_MD5
supportedSSLCiphers: SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
supportedSSLCiphers: TLS_ECDHE_ECDSA_WITH_NULL_SHA
supportedSSLCiphers: TLS_ECDHE_RSA_WITH_NULL_SHA
supportedSSLCiphers: TLS_ECDH_RSA_WITH_NULL_SHA
supportedSSLCiphers: TLS_ECDH_ECDSA_WITH_NULL_SHA
supportedSSLCiphers: SSL_RSA_WITH_NULL_SHA
supportedSSLCiphers: SSL_RSA_WITH_NULL_MD5
supportedSSLCiphers: SSL_CK_RC4_128_WITH_MD5
supportedSSLCiphers: SSL_CK_RC2_128_CBC_WITH_MD5
supportedSSLCiphers: SSL_CK_DES_192_EDE3_CBC_WITH_MD5
supportedSSLCiphers: SSL_CK_DES_64_CBC_WITH_MD5
supportedSSLCiphers: SSL_CK_RC4_128_EXPORT40_WITH_MD5
supportedSSLCiphers: SSL_CK_RC2_128_CBC_EXPORT40_WITH_MD5
objectClass: top
dataversion: 020150203114556020150203114556
namingContexts: dc=XXXXXXXXXXXXXXXXXXXX,dc=com
namingContexts: dc=XXXXXXXXXXXXXXXXXXXX,dc=sip
netscapemdsuffix: cn=ldap://dc=ds02:389
subschemaSubentry: cn=schema
supportedLDAPVersion: 2
supportedLDAPVersion: 3
supportedSASLMechanisms: DIGEST-MD5
supportedSASLMechanisms: EXTERNAL
vendorName: Sun Microsystems, Inc.
vendorVersion: Sun-Directory-Server/7.0

_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
Florian Kluender | 3 Feb 08:28 2015

Cannot start ido2db

Hi all,

 

i have a big problem. I cannot start ido2db so I have no connection to the database since July 2014 L.

The error message is: “Starting Ido2db:Error processing config file ‘/usr/local/icinga/etc/ido2db.cfg.

Attached are the ido2db.cfg and the idomod.cfg. The service user is icinga.

 

I hope anybody can help me please.

 

 

Florian Klünder
IT Officer

NOVALED GmbH
Tatzberg 49
01307 Dresden
Germany

phone  +49 351 796 5816
fax       +49 351 796 5829

e-mail Florian.Kluender-f5eVQN30ZdtBDgjK7y7TUQ@public.gmane.org
web
http://www.novaled.com

May happiness and prosperity be with you throughout the New Year 2015!
Be invited to view our e-card here:

 

 

Novaled GmbH, Registered Office: 01307 Dresden, Companies Register: Amtsgericht Dresden, HRB 32931, Board of Directors: Gerd Guenther; JinWook Lee, PhD; Chairwoman of the Supervisory Board: BongOk Kim, PhD

------------------------------------------------------------------------------------------
Disclaimer
This e-mail is from Novaled GmbH and may contain information that is confidential or privileged. If you are not the intended recipient, do not read, copy or distribute the e-mail or any attachments. Instead, please notify the sender and delete the e-mail and any attachments. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, lost, destroyed, incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission.

 

 

 

Attachment (ido2db.cfg): application/octet-stream, 8 KiB
Attachment (idomod.cfg): application/octet-stream, 8 KiB
_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
Gerd v. Egidy | 13 Jul 16:40 2014
Picon

interest in sms notification scripts?

Hi,

I finally had the time to set up sms notification for my icinga 2 installation. 
I'm using smstools http://smstools3.kekekasvi.com/ to connect my gsm terminal. 

Icinga2 currently does not come with scripts & configuration to send short 
messages. I uploaded the scripts I wrote into the feature/sms-notification-
scripts branch, see e.g.
https://dev.icinga.org/projects/i2/repository?rev=feature%2Fsms-notification-scripts

Is there any interest in including these scripts with Icinga2?

There is some stuff, like cmake installation and documentation, missing in the 
branch. I'll add this of course before submitting it for merge.

Kind regards,

Gerd
Thomas Dressler | 20 Jun 21:07 2014
Picon

Re: [icinga-core] v1.11.5: Version 1.11.5

Hi,

Am 20.06.2014 13:25, schrieb Michael Friedrich:


View it on GitHub.

I am just dealing with the new version to upgrade from 1.11.1. While updating i found these commits to mysql.sql 

commit a84b72ff40b104c7a84eb012d69f5b6fd612e430
Author: Michael Friedrich <Michael.Friedrich-1vhwlxDiY8OELgA04lAiVw@public.gmane.org>
Date:   Sat May 10 20:49:26 2014 +0200

    IDOUtils: Add is_reachable columns for {host,service}status tables.

commit 0766acbc59c55faf35d62a434dd5e3d5b69a7595
Author: Michael Friedrich <michael.friedrich-1vhwlxDiY8OELgA04lAiVw@public.gmane.org>
Date:   Thu Apr 24 14:38:17 2014 +0200

    Add {host,service}{groups,status] columns: notes, notes_url, action_url, is_
   
    Refs #6060

oracle upgrade sql to 1.11.3 doesn't contain similar changes. Only the version update is in.
Also the create objects sql missed the changes. Are these features not oracle relevant?

Thomas

_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
Michael Friedrich | 2 Jun 10:22 2014
Picon

Icinga 2 Development Week 22/14


Summary for Icinga 2 Development Week 22/14:

Target version: 2.0.0 Beta 2 (6.6.2014)

https://dev.icinga.org/projects/i2/issues?query_id=22

26.-28.5.: workhours
27.5.: 2.0.0 Beta 1 Release:
https://www.icinga.org/2014/05/27/icinga-2-beta-released/

Follow the activity stream at https://dev.icinga.org/projects/i2/activity

-----------------------------------------------------------
Work done:
-----------------------------------------------------------

* Fix Icinga fails to start when IPv6 support is not available #6375
* Require at least Vagrant 1.2.x in Vagrantfile #6365
* Documentation: add DB IDO to monitoring basics (config, status health
checks, etc) #6358
* Documentation: explain how to enable checks/notifications #6357
* Documentation: mention and explain livestatus in monitoring basics
chapter #6356
* Fix icinga_programstatus table is empty after RESTART_PROCESS #6349
* Logging: change library name into class name ("base/critical") #6346
* Remove thread names from log messages #6345
* Change Vagrant VM welcome page to a more friendly one. #6334
* Prepare release: 2.0.0 Beta 1 #5791
* Documentation: Fix migration script documentation. #6326
* Fix Debian package installs logrotate/icinga2.cmake file #6322
* Fix Scheduled downtimes aren't removed by the cleanup timer #6321
* Documentation: add configuration best practice introduction #6318
* Documentation: Add advanced apply services with custom command
arguments example. #6317
* Fix check statistics are mixing host/service checks. #6313
* Add icinga2-enable-feature support for multiple modules #6315
* Documentation: Import missing Livestatus tables and attributes #6314

-----------------------------------------------------------
Ongoing
-----------------------------------------------------------

* add systemd support #4794
* Improve error messages #6070
** add --info with additional application information #6347
* Documentation
** Migration Hints #6380
* CLI Config Migration #5929
* Bugs, Bugs, Bugs
* Packages
** First FreeBSD Port
** split sample config into a separate package #6355
* add syntax highlight files for editors (vim, nano, etc) #3199
* 2.0 Beta2 release preparations

-----------------------------------------------------------
Changes
-----------------------------------------------------------

* Logging: change library name into class name ("base/critical") #6346
* Remove thread names from log messages #6345
* Add icinga2-enable-feature support for multiple modules #6315

-----------------------------------------------------------
Feedback/Tests required
-----------------------------------------------------------

* Documentation
* Packages, Installation, Features
* Notifications, Dependencies, Alerts, etc
* Cluster: Load Balancing, HA, Config Sync
* Which problem does Icinga 2 solve in your opinion?

-- 
Michael Friedrich, DI (FH)
Application Developer

NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | Michael.Friedrich <at> netways.de

** Open Source Backup Conference 2014 - September - osbconf.org **
** Puppet Camp Duesseldorf 2014 - Oktober - netways.de/puppetcamp **
** OSMC 2014 - November - netways.de/osmc **
** OpenNebula Conf 2014 - Dezember - opennebulaconf.com **
_______________________________________________
icinga-devel mailing list
icinga-devel <at> lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-devel
Michael Friedrich | 26 May 10:17 2014
Picon

Icinga 2 Development Week 21/14


Summary for Icinga 2 Development Week 21/14:

Target version: 2.0.0 Beta 1.(27.5.2014)

https://dev.icinga.org/projects/i2/issues?query_id=21

19.-23.5.: workhours
24.-25.5.: weekend

Follow the activity stream at https://dev.icinga.org/projects/i2/activity

-----------------------------------------------------------
Work done:
-----------------------------------------------------------

* Cluster Freshness Check: Implement the "cluster-zone" check task. #6204
* Fix incorrect state change states logged for hosts. #6290
* Fix Child zone configurations are not synced to members of the parent
zone. #6212
* ThreadPool: Spawn one thread per CPU #6279
* Improve error messages. #6070
* Implement command-line option to specify log level for the console log
(-x|--log-level). #6276
* Documentation: add missing addons. #6275
* Documentation: Add troubleshooting chapter, fix addon chapter. #5611 #6276
* Documentation: Emphasize on apply rules in example config. #6266
* Move local node/zone config from features-available/api.conf and
constants.conf to seperate include. #6208
* Documentation: update migration docs. #6271
* Documentation: add a dependency example for agent based health checks.
#6272
* Plugins: Add generic nrpe, by_ssh command definition. #6225
* Documentation: Update what's new for 2.0.0 Beta 1. #5820
* Fix initscript error message on checkconfig is wrong. #6269
* Documentation: Explain config validation with errors and reload. #6259
* Documentation: explain how to pass arguments from host/service to
check command. #6267
* Change the most chatting log messages to 'notice' severity. #6070
* Make critical connection errors readable in ApiListener. #6070
* Add 'notice' severity to *Logger. #6070
* Fix Config file parse order. #5854
* Fix Logrotate config doesn't work. #6229
* Fix compiler warnings. #5823
* Fix Notification commands use the wrong CheckResult object. #6260
* Fix Multiple assign in apply Dependency. #6257
* Fix Config validation broken for PerfdataWriter. #6255
* Documentation: Fix "display_name" missing in Service attributes table.
#6253
* Documentation: add apply best practices. #5877
* Fix Build on Fedora fails. #6250
* Documentation: mention the demo vm in the about chapter. #6248
* Documentation: Fix Cluster config examples. #6247
* Fix EL5 rpm postgresql buildrequires version conflict. #5847
* Documentation: Move ITL/Plugin Commands into Icinga 2 configuration
(chapter 5). #6245
* Fix cluster check shows error when it is OK. #6244
* Fix log message 'current master' is confusing. #6241
* Fix compatibility with older versions of CMake. #6240
* Verify interface output attributes and values. #5807
* Documentation: additional plugins require a check command. #6239
* Use CustomVarObject instead of DynamicObject for all libicinga
objects. #6187
* Update cluster documentation. #6243
* Fix Command timeout doesn't work. #6232
* Fix Deadlock in db_ido. #6230

-----------------------------------------------------------
Ongoing
-----------------------------------------------------------

* add systemd support #4794
* Improve error messages #6070
* Documentation
* Bugs, Bugs, Bugs
* 2.0 Beta1 release preparations

-----------------------------------------------------------
Changes
-----------------------------------------------------------

* Implement command-line option to specify log level for the console log
(-x|--log-level) #6276
* Add 'notice' severity to *Logger. #6070
* ThreadPool: Spawn one thread per CPU #6279
* Cluster Freshness Check: Implement the "cluster-zone" check task. #6204

-----------------------------------------------------------
Feedback/Tests required
-----------------------------------------------------------

* Documentation
* Packages, Installation, Features
* Notifications, Dependencies, Alerts, etc
* Cluster: Load Balancing, HA, Config Sync
* Which problem does Icinga 2 solve in your opinion?

-- 
Michael Friedrich, DI (FH)
Application Developer

NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
Tel: +49 911 92885-0 | Fax: +49 911 92885-77
GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
http://www.netways.de | Michael.Friedrich <at> netways.de

** Open Source Backup Conference 2014 - September - osbconf.org **
** Puppet Camp Duesseldorf 2014 - Oktober - netways.de/puppetcamp **
** OSMC 2014 - November - netways.de/osmc **
** OpenNebula Conf 2014 - Dezember - opennebulaconf.com **
_______________________________________________
icinga-devel mailing list
icinga-devel <at> lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-devel
Michael Friedrich | 19 May 13:44 2014
Picon

Icinga 2 Development Week 20/14


Summary for Icinga 2 Development Week 20/14:

Target version: 0.0.11

https://dev.icinga.org/projects/i2/issues?query_id=21

12.-16.5.: workhours
15.+16.5.: Monitoring Portal Workshop
17.-18.5.: weekend

Feature freeze has happened with 0.0.11 release. Next version: 2.0.0 Beta 1.

-----------------------------------------------------------
Work done:
-----------------------------------------------------------

* reloading icinga2 doesn't work when run as a native systemd service #6118
* Parallellize restoring objects from the state file #6226
* Evaluate apply rules in parallel #6223
* Fix Icinga crashes when zones.d directory doesn't exist #6224
* Cluster: Zone configuration sync #6191
* Implement shared API primitives for the cluster & agent #6107
* Fix assign operator #6198
* Documentation: Add a note on unreachable preventing notifications 
being sent. #4789
* Creating a dependency of services on the same host using the apply 
keyword requires parent_host_name attribute #6197
* Documentation: external command list broken #6128
* execvp error on files/directories #6160

-----------------------------------------------------------
Ongoing
-----------------------------------------------------------

* add systemd support #4794
* Documentation
* Bugs, Bugs, Bugs
* 2.0 Beta1 release preparations

-----------------------------------------------------------
Changes
-----------------------------------------------------------

* Cluster: Zone configuration sync #6191

Zones are managed below /etc/icinga2/zones.d/≤zonename>. This prefix can 
be changed, but it is explicitely included by the Icinga 2 daemon (no 
include_recursive required).

The ApiListener object must have set 'accept_config = true' in order to 
receive configuration from the parent zone.

The zone attribute is set for all files included from those directories. 
Apply rules also set the attribute accordingly.

If the local configuration is newer than the received update the 
synchronisation process is skipped.

-----------------------------------------------------------
Feedback/Tests required
-----------------------------------------------------------

* Documentation
* Packages, Installation, Features
* Notifications, Dependencies, Alerts, etc
* Cluster: Load Balancing, HA, Config Sync
* Which problem does Icinga 2 solve in your opinion?

--

-- 
DI (FH) Michael Friedrich

michael.friedrich@...  || icinga open source monitoring
https://twitter.com/dnsmichi || lead core developer
dnsmichi@...       || https://www.icinga.org/team
irc.freenode.net/icinga      || dnsmichi
Michael Friedrich | 19 May 13:08 2014
Picon

Icinga 2 Development Week 20/14


Summary for Icinga 2 Development Week 19/14:

Target version: 0.0.11

https://dev.icinga.org/projects/i2/issues?query_id=21

3.+4.5.: "weekend"
5.-9.5.: work on cluster changes & open issues
10.+11.5.: "weekend"

-----------------------------------------------------------
Work done:
-----------------------------------------------------------

*
*
*
*
*
*

-----------------------------------------------------------
Ongoing
-----------------------------------------------------------

* Cluster changes #6192
** Implement shared API primitives for the cluster #6107
** Reimplement load-balancing for checks.#6107
** Implement HA for IDO connections. #6107 #4739
** Zone configuration sync #6191
* migration script #5821
* Everything else: https://dev.icinga.org/projects/i2/issues?query_id=21

-----------------------------------------------------------
Changes
-----------------------------------------------------------

* add 'is_reachable' to host and service state tables requires Classic 
UI 1.11.3

* Cluster version 3: ClusterListener and Domains are gone. New: 
ApiListener and Zones. #6192

There's a generic ApiListener object defining the ssl certificates 
required for this instance. The new default bind port is '5665'. This 
feature is called 'api' and can be enabled through

# icinga2-enable-feature api

object ApiListener "api" {
   cert_path = SysconfDir + "/icinga2/pki/" + NodeName + ".crt"
   key_path = SysconfDir + "/icinga2/pki/" + NodeName + ".key"
   ca_path = SysconfDir + "/icinga2/pki/ca.crt"
}

For now, this is being used for the cluster functionality only, but 
serves us as solid base for future implementations ("agent", "api", etc) 
for 2.1+ (Icinga 2 development doesn't stop with 2.0!).

The Endpoint objects still exist, but they do not control the 
configuration sync anymore. We've played around with the view based 
configuration and it just did not feel right. Therefore these endpoints 
are the same on all involved nodes, but must be kept in sync/available 
wherever required.
The new default port is '5665' and is now optional.

object Endpoint "icinga2a" {
   host = "icinga2a.localdomain"
}

Additionally the keep_alive for connections can be configured, as well 
as the log_duration for keeping relay logs on connection loss. Defaults 
to 5m and 1d.

That way, the connection stuff for the cluster is "basically" like it 
has been before, but with one difference: Zones.

Zones in Icinga 2 declare a trusted zone among multiple nodes. All nodes 
are considered running in a high availability active/active setup which 
means they elect one active master at runtime.
If the active master dies, the ongoing heartbeat messages will garantuee 
failover detection and make the remaining instances elect a new active 
master.

object Zone "ha-master" {
   endpoints = [ "icinga2a", "icinga2b" ]
}

object Zone "check-satellite" {
   endpoints = [ "icinga2c", "icinga2d", "icinga2e" ]
   parent "ha-master"
}

Communication between zones may happen between all involved nodes, but 
if a "passive" node gets a checkresult, it will forward it to the active 
master which then processes the result (replication to other nodes or 
zones, notifications, backend features like ido).

High availability also means that features like IDO should only run on 
the active node, while the passive ones remain in standby (feature is 
paused). If there's a split brain situation, both (or multiple) 
instances will attempt to write for example ido, or fire notifications.

Load distribution for checks and notifciations works like before - all 
acitve checkers will share the check load. If you're planning to check a 
specific zone on only one satellite, just assign it like that.

Multiple zones can be stacked into a parent-child-tree whereas the 
configuration sync should then happen too. Zone configuration will be
done like

   /etc/icinga2/zones.d/≤zonename>

(to be implemented in #6191). Additional permissions will be required to
receive the configuration.

Currently, the following already works:

* APiListener, Endpoints, Zones.
* HA for IDO connections
* Load Balancing for Checks
* active master election in zones

To-do:

* configuration sync in/between zones
* additional permissions

-----------------------------------------------------------
Feedback/Tests required
-----------------------------------------------------------

* Documentation: Read through, try getting started. Everything clear, 
what's missing/unclear/could get a better phrasing?

This is clearly a call to native English speakers (which I am not). Help 
us shaping the documentation! Git patches or github pull requests preferred

* Backends: Install IDO, Livestatus, Status files. Use your favourite 
GUI/addon and test the functionality.

* Command arguments: Try them out. How does it feel to optionally add 
arguments to check_http and such?

* Apply rules: Use them. Tell us what you think.

* Cluster: It's still work in progress, but keep an eye on that, and try 
the current state of the art.

--

-- 
DI (FH) Michael Friedrich

michael.friedrich@...  || icinga open source monitoring
https://twitter.com/dnsmichi || lead core developer
dnsmichi@...       || https://www.icinga.org/team
irc.freenode.net/icinga      || dnsmichi
Michael Friedrich | 12 May 10:54 2014
Picon

Icinga 2 Development Week 19/14

Summary for Icinga 2 Development Week 19/14:

Target version: 0.0.11

https://dev.icinga.org/projects/i2/issues?query_id=21

3.+4.5.: "weekend"
5.-9.5.: work on cluster changes & open issues
10.+11.5.: "weekend"

-----------------------------------------------------------
Work done:
-----------------------------------------------------------

* rename Dependency 'state_filter' to 'states' #6113
* Documentation: Apply new structure. #6115
* Don't allow "managed" downtimes to be deleted by users #5980
* Livestatus: test host comments with joins #5937
* Dependencies: Service states changes to critical instead of 
unknown/unreachable #5872
* StatusDataWriter only supports host->host, service->service 
dependencies #6131
* Decrease default check intervals. #6107
* Remove the ZlibStream class and the stream_bio functionality #6119
* Apply: Inherit zone from parent object. #6107
* Reimplement load-balancing for checks.#6107
* Implement HA for IDO connections. #6107
* Fix an issue where expired Timer pointers caused other timers to be 
delayed. #6179
* Config validator: Make sure that objects are not abstract. #6148
* Implement support for arrays for the indexer operator #6182
* enable/disable commands do not update status tables #6151
* Check if livestatus log functionality still works #6161
* ITL: Move monitoring plugin commands into a separate config file #6130
* Documentation: add developers section #6184
* DB IDO/Livestatus/Status files: add 'is_reachable' to host and service 
state tables #6094
* Livestatus:  add check_source to host table #6185
* Documentation & Feature: command argument conditionals #5933
* rename host.total_* runtime macros to host.num_* #6189
* Documentation: migration: runtime macros renamed #6149
* Documentation: explain how macro resolving works #6010
* Non sticky acknowledgements won't be removed once the host/service 
recovers #5363
* Remove unnecessary includes #6189

-----------------------------------------------------------
Ongoing
-----------------------------------------------------------

* Cluster changes #6192
** Implement shared API primitives for the cluster #6107
** Reimplement load-balancing for checks.#6107
** Implement HA for IDO connections. #6107 #4739
** Zone configuration sync #6191
* migration script #5821
* Everything else: https://dev.icinga.org/projects/i2/issues?query_id=21

-----------------------------------------------------------
Changes
-----------------------------------------------------------

* add 'is_reachable' to host and service state tables requires Classic 
UI 1.11.3

* Cluster version 3: ClusterListener and Domains are gone. New: 
ApiListener and Zones. #6192

There's a generic ApiListener object defining the ssl certificates 
required for this instance. The new default bind port is '5665'. This 
feature is called 'api' and can be enabled through

# icinga2-enable-feature api

object ApiListener "api" {
   cert_path = SysconfDir + "/icinga2/pki/" + NodeName + ".crt"
   key_path = SysconfDir + "/icinga2/pki/" + NodeName + ".key"
   ca_path = SysconfDir + "/icinga2/pki/ca.crt"
}

For now, this is being used for the cluster functionality only, but 
serves us as solid base for future implementations ("agent", "api", etc) 
for 2.1+ (Icinga 2 development doesn't stop with 2.0!).

The Endpoint objects still exist, but they do not control the 
configuration sync anymore. We've played around with the view based 
configuration and it just did not feel right. Therefore these endpoints 
are the same on all involved nodes, but must be kept in sync/available 
wherever required.
The new default port is '5665' and is now optional.

object Endpoint "icinga2a" {
   host = "icinga2a.localdomain"
}

Additionally the keep_alive for connections can be configured, as well 
as the log_duration for keeping relay logs on connection loss. Defaults 
to 5m and 1d.

That way, the connection stuff for the cluster is "basically" like it 
has been before, but with one difference: Zones.

Zones in Icinga 2 declare a trusted zone among multiple nodes. All nodes 
are considered running in a high availability active/active setup which 
means they elect one active master at runtime.
If the active master dies, the ongoing heartbeat messages will garantuee 
failover detection and make the remaining instances elect a new active 
master.

object Zone "ha-master" {
   endpoints = [ "icinga2a", "icinga2b" ]
}

object Zone "check-satellite" {
   endpoints = [ "icinga2c", "icinga2d", "icinga2e" ]
   parent "ha-master"
}

Communication between zones may happen between all involved nodes, but 
if a "passive" node gets a checkresult, it will forward it to the active 
master which then processes the result (replication to other nodes or 
zones, notifications, backend features like ido).

High availability also means that features like IDO should only run on 
the active node, while the passive ones remain in standby (feature is 
paused). If there's a split brain situation, both (or multiple) 
instances will attempt to write for example ido, or fire notifications.

Load distribution for checks and notifciations works like before - all 
acitve checkers will share the check load. If you're planning to check a 
specific zone on only one satellite, just assign it like that.

Multiple zones can be stacked into a parent-child-tree whereas the 
configuration sync should then happen too. Zone configuration will be
done like

   /etc/icinga2/zones.d/≤zonename>

(to be implemented in #6191). Additional permissions will be required to
receive the configuration.

Currently, the following already works:

* APiListener, Endpoints, Zones.
* HA for IDO connections
* Load Balancing for Checks
* active master election in zones

To-do:

* configuration sync in/between zones
* additional permissions

-----------------------------------------------------------
Feedback/Tests required
-----------------------------------------------------------

* Documentation: Read through, try getting started. Everything clear, 
what's missing/unclear/could get a better phrasing?

This is clearly a call to native English speakers (which I am not). Help 
us shaping the documentation! Git patches or github pull requests 
preferred :)

* Backends: Install IDO, Livestatus, Status files. Use your favourite 
GUI/addon and test the functionality.

* Command arguments: Try them out. How does it feel to optionally add 
arguments to check_http and such?

* Apply rules: Use them. Tell us what you think.

* Cluster: It's still work in progress, but keep an eye on that, and try 
the current state of the art.

--

-- 
DI (FH) Michael Friedrich

michael.friedrich@...  || icinga open source monitoring
https://twitter.com/dnsmichi || lead core developer
dnsmichi@...       || https://www.icinga.org/team
irc.freenode.net/icinga      || dnsmichi
Thomas Dressler | 4 May 13:44 2014
Picon

icinga2.spec pandoc dependency for el5

icinga2.spec v0.0.10 introduced a new dependency on pandoc, which i cant 
resolve on EL5. Looks there are only packages for EL6 available 
http://rpmfind.net/linux/rpm2html/search.php?query=pandoc. Where can i 
get a matching pandoc rpm (and probably nesessary dependencies) for EL5?

Thomas

Gmane