icinga-devel | 19 Jun 18:14 2016
Picon
Picon

extremely good!

Hey,

 

When I found that extremely good stuff I thought you could like it, take a look here http://ltenkungymi.barnerquarterhorses.com/aehrkvo

 

icinga-devel

_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
Munzir Taha | 2 Jun 20:48 2016
Picon

Icinga Arabic Translation

Hi sirs,
I want to contribute Arabic translation. It's sponsored by freesystems.com.sa. 
I finished translating icinga.po and monitoring.po. However, when I compiled 
the translation, I still notice some strings which are not translated. Mainly, 
the drop-down menus are not fully translated. e.g

  <option value="host_acknowledged">Host Acknowledged</option>
  <option value="host_action_url">Host Action Url</option>
  <option value="host_active_checks_enabled">Host Active Checks Enabled</
option>
  <option value="host_address">Host Address</option>
  <option value="host_address6">Host Address6</option>

I copied the html source so you better know the context. So, where are these 
strings coming from?

Another thing is for Icinga to fully support Arabic, everything should be 
mirrored. I will be glad to help and test if you are willing to do this.

--

-- 
Telecommunications and Electronics Engineer (B.Sc.)
VMware Certified Associate - Data Center Virtualization (VCA-DCV)
Novell Data Center Technical Specialist (DC Tech Spec)
Linux Professional Institute Certified Level 1 (LPIC-1)
ITIL® Foundation Certificate in IT Service Management
Novell Certified Linux Administrator (Novell CLA)
International Computer Driving License (ICDL)
Solaris Certified System Administrator (SCSA)
Microsoft Office User Specialist (MOUS)
Red Hat Certified Engineer (RHCE)
IBM Certified for Power Systems
Linux+ Certified Professional
Master CIW Designer
SUSE 11 Tech Spec
Antony Stone | 2 Jun 13:14 2016
Picon

Version numbers?

Hi.

I've recently (about a month ago) installed Icinga2 on a Debian 7 machine, 
using debmon.org as the package repository to get Icinga from.

It installed Icinga version 2.4.7 and Icingaweb2 version 2.3.2

Today I upgraded the packages to current versions, and got Icinga version 
2.4.10.  I've restarted both Icinga and Apache since the upgrade.

The Icingaweb2 interface now shows me (under "System"):

"Program Version: r2.4.10-1" if I go to "Monitoring Health"
"Icinga Version 2.3.2" if I go to "About"

This seems rather confusing to me, and I wonder whether the "About" page could 
show both the icinga2 and the Icingaweb2 versions, to make it clear which the 
system is running?

Thanks,

Antony.

--

-- 
I thought I had type A blood, but it turned out to be a typo.

                                                   Please reply to the list;
                                                         please *don't* CC me.
hoermanntex | 17 Mar 22:40 2016
Picon
Picon

Fw: new important message

Hello!

 

New message, please read http://anna.business-system.net/street.php

 

hoermanntex-Mmb7MZpHnFY@public.gmane.org

_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
Picon

Character encoding at plugin boundaries

Hi,

 

I'm looking for some hints on how Icinga plugins are supposed to behave regarding character encoding. The docs at https://www.monitoring-plugins.org/doc/guidelines.html and http://docs.icinga.org/latest/en/pluginapi.html are very useful and accurate in many situations, but lack information about character encodig and allowed characters. Sorry if I've overlooked something, please point me to correct location and ignore the part below in that case.

 

From a plugin writers perspective you may want to receive command line arguments that are non-ASCII characters and apply some logic on them, and you may want to output characters that are above ASCII range. Say you want to ouput "OK - My environment temperature is 21°C" (or even the same in Cyrillic)
-is it possible at all?
-would you encode the degree sign to Latin-1, UTF-8, or the current locale settings (which may differ from default when the plugin is executed from a service started via init system), or some configured setting?

 

Afaik, Icinga (v1) and friends forward content mostly byte-wise. Sometimes they check for characters in the 7-bit ASCII range.
Passing UTF-8 and Latin-1 works, because the encoding is compatible in the 7-bit ASCII range. In our setup we can sucessfully deal with unicode characters, e.g. by strictly decoding from and encoding to UTF-8 at plugin boundaries and having the Icinga definitions safed as UTF-8 endoded text.

 

It would be helpful to have something about that in the guidelines, what do you think? Otherwise, people (like we) hack down their own solution that is not interchangeable with others.

 

Best regards,
Tobias



 
Telekom Mail: Ihre Daten bleiben in Deutschland.
Jetzt persönliche E-Mail-Adresse sichern!
www.t-online.de/email-kostenlos
_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
P Richards | 14 Apr 23:10 2015

Hello / Demo modules

Hello,

 

I've been trying to take a look at the 'hello' and 'demo' modules within icinga.

 

At the moment, I'm struggling to actually get these rather simple modules to work.

Could someone confirm the purpose of the demo/hello module's, and provide a config file that can be used with them?

 

For the demo module, I've opened a bug 9053 [https://dev.icinga.org/issues/9053] which has a patch to fix compilation issue. The commit to fix issue #8890 on 28th March <at> https://git.icinga.org/?p=icinga2.git;a=blobdiff;f=lib/demo/CMakeLists.txt;h

=92fa2bd22eff7782070e758302bda0a33d25dced;hp=2484d356acd556b8c93a1048d02f31d

86147fc55;hb=72a7b08480005444fb67cc5704a96b9edb95b8cc;hpb=0771c9755a73fe436a

6b928585664e15f75b1f1f;js=1 broke the build.

 

For the hello module, my attempts to work out a config file for it are only generating an assertion failure, so before raising another bug, would like to check I'm doing it right ;)

 

Thanks

Paul

 

 

_______________________________________________
icinga-devel mailing list
icinga-devel@...
https://lists.icinga.org/mailman/listinfo/icinga-devel
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

Gmane