Re: [icinga-users] Icinga 2.4 does not start after update

2015-11-20 Thread Daniel Guillermo Bareiro
Hi, Michael. Thanks for your reply. >> I just upgraded to Icinga 2.4 using debmon.org packages. But it does not >> start. There seems to be a problem in the configuration files: >> >> (...) >> >> Although I'm not sure what is the problem because the syntax in this >> file looks correct. >> >> I w

Re: [icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Awesome! This seems the easiest way then as I only have around 30 nodes. Thanks! On 11/20/2015 06:16 PM, Michael Friedrich wrote: > Yep :-) > >> Am 20.11.2015 um 17:55 schrieb NOC : >> > But basically I can create new certificates with: > > * pk

Re: [icinga-users] Icinga 2.4 does not start after update

2015-11-20 Thread Michael Friedrich
> On 20 Nov 2015, at 19:54, Daniel Bareiro wrote: > > Hi all! > > I just upgraded to Icinga 2.4 using debmon.org packages. But it does not > start. There seems to be a problem in the configuration files: > > --- > root@icinga2:~#

[icinga-users] Icinga 2.4 does not start after update

2015-11-20 Thread Daniel Bareiro
Hi all! I just upgraded to Icinga 2.4 using debmon.org packages. But it does not start. There seems to be a problem in the configuration files: --- root@icinga2:~# systemctl status icinga2 ● icinga2.service - Icinga host/service/

Re: [icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread Michael Friedrich
Yep :-) > Am 20.11.2015 um 17:55 schrieb NOC : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > But basically I can create new certificates with: > > * pki new-ca (sets up a new CA) > * pki new-cert (creates a new CSR) > * pki request (requests a certificate) > > and run 'node wizard' on

Re: [icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 But basically I can create new certificates with: * pki new-ca (sets up a new CA) * pki new-cert (creates a new CSR) * pki request (requests a certificate) and run 'node wizard' on all nodes to fix it and make it work with the new certificates? On

Re: [icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks for explaining what the problem seems to be. Your explanation makes sense. On 11/20/15 5:34 PM, Michael Friedrich wrote: > openssl x509 -in mbmif.int.netways.de.crt -text The headers are: Certificate: Data: Version: 1 (0x0)

Re: [icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread Michael Friedrich
> On 20 Nov 2015, at 15:07, NOC wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > When calling the API of Icinga 2.4 on CentOS 6.7 with the command > (curl -k -s -u root:icinga 'https://localhost:5665/v1') I get the > following error in icinga2.log: > > [2015-11-20 15:03:38 +0100]

Re: [icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Do you mean of the ca.crt which is used by the API? The API should be reachable by only using a password too right? OpenSSL on CentOS does not seem to support -text when issuing the command without parameters: # openssl -text openssl:Error: '-text'

Re: [icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread Jean-Marcel Flach
Hello, please provide an openssl -text of the certificate in question. Kind regards, Jean On 11/20/2015 03:07 PM, NOC wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When calling the API of Icinga 2.4 on CentOS 6.7 with the command (curl -k -s -u root:icinga 'https://localhost:5665/v1'

[icinga-users] API TLS error which was fixed in previous version

2015-11-20 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When calling the API of Icinga 2.4 on CentOS 6.7 with the command (curl -k -s -u root:icinga 'https://localhost:5665/v1') I get the following error in icinga2.log: [2015-11-20 15:03:38 +0100] warning/TlsStream: OpenSSL error: error:14094413:SSL rout

[icinga-users] Problem with Icingaweb2

2015-11-20 Thread Peltokangas Mikko
Hello, I added new user to my Icingaweb2 to watch monitoring and all my dashlets are gone. So when I log in adminuser, there isn't anything but application log and about under System-page. It give in log only this: Stacktrace: #0 /usr/share/icingaweb2/application/controllers/ConfigController.ph

Re: [icinga-users] Downtime notifications behavior

2015-11-20 Thread Michael Friedrich
> On 20 Nov 2015, at 10:52, Bancal Samuel wrote: > > Hi, > > I’m not sure to understand Icinga2's behavior with downtimes. > > I would say this should prevents notifications to be sent to the admins > during a period that is planned for maintenance. > Let's see a concrete case : We reboot a serv

[icinga-users] Downtime notifications behavior

2015-11-20 Thread Bancal Samuel
Hi, I’m not sure to understand Icinga2's behavior with downtimes. I would say this should prevents notifications to be sent to the admins during a period that is planned for maintenance. Let's see a concrete case : We reboot a server and make a cold image (Clonezilla). a) we declare a downtim

Re: [icinga-users] Group notification messages

2015-11-20 Thread Michael Friedrich
> On 20 Nov 2015, at 10:06, Romaneev Vasily wrote: > > Hello, i want to ask is there're any plans on grouping similar messages: > > use cases: > * Any configuration manager add firewall rule, that blocks icinga checks - we > won't receive num_hosts*num_services messages(4500 services on our > i

[icinga-users] Group notification messages

2015-11-20 Thread Romaneev Vasily
Hello, i want to ask is there're any plans on grouping similar messages: use cases: * Any configuration manager add firewall rule, that blocks icinga checks - we won't receive num_hosts*num_services messages(4500 services on our installation). It can be simply grouped - Service XXX failed on 15