Michael,
We use HAPROXY and configuration are pasted below for your reference.
Here is the curl command which crashes one of the Icinga api server node - curl
-k -s -u icingaadmin:icinga
'https://192.168.67.4:5665/v1/objects/hostgroup?cascade=1' -H "accept:
application/json" -X DELETE
Regarding crash log - /var/log/icinga2/crash directory is empty. However
application logs is pasted in earlier email thread
HAPRoxy Configuration
----------------------
frontend icinga_web_frontend
bind 192.168.67.4:80
option forwardfor
acl is_icinga url_beg -i /icingaweb2
acl is_pnp url_beg -i /pnp4nagios
use_backend icinga_web_backend if is_icinga
use_backend icinga_web_backend if is_pnp
frontend icinga_api_frontend
bind 192.168.67.4:5665
mode tcp
default_backend icinga_api_backend
backend icinga_api_backend
mode tcp
server icingaapi1 192.168.67.5:5665 maxconn 2048 weight 100 check
server icingaapi2 192.168.67.6:5665 maxconn 2048 weight 1 check backup
backend icinga_web_backend
balance source
hash-type consistent
option forwardfor
server icingaweb1 192.168.67.5:80 maxconn 2048 weight 100 check
server icingaweb2 192.168.67.6:80 maxconn 2048 weight 1 check backup
Please let us know if any other information is required for further analysis
>----------------------------------------------------------------------
>
>Message: 1
>Date: Wed, 16 Dec 2015 19:54:46 +0100
>From: Michael Friedrich <[email protected]>
>To: <[email protected]>
>Subject: Re: [icinga-users] icinga api error
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="utf-8"; format=flowed
>
>Am 15.12.2015 um 02:44 schrieb Madhusmita Gochhait:
>> Hello All ,
>>
>>
>> I have a 2 node active-active setup for icinga , with a vip address
>> which points to these nodes .
>>
>> For Ex :
>>
>> icinga1 : icinga-cluster-3.englab.juniper.net
>> icinga2 :icinga-cluster-5.englab.juniper.net
>> VIP: icinga-cluster-6.englab.juniper.net
>
>How does that virtual ip determine which node is in charge?
>Undeterminstic DNS entries?
>
>>
>> In log , I see both nodes syncing :
>>
>> [2015-12-14 17:39:22 -0800] information/ApiListener: New client
>> connection for identity 'icinga-cluster-3.englab.juniper.net'
>> [2015-12-14 17:39:22 -0800] information/ApiListener: Sending updates
>> for endpoint 'icinga-cluster-3.englab.juniper.net'.
>> [2015-12-14 17:39:22 -0800] information/ApiListener: Syncing runtime
>> objects to endpoint 'icinga-cluster-3.englab.juniper.net'.
>> [2015-12-14 17:39:22 -0800] information/ApiListener: Finished sending
>> updates for endpoint 'icinga-cluster-3.englab.juniper.net'.
>>
>>
>> But When I am sending PUT/DELETE requests through the VIP , like :
>>
>> curl -k -s -u icingaadmin:icinga 'https://
>> <https://localhost:5665/v1/objects/hosts/10.102.58.77>icinga-cluster-6.englab.juniper.net:5665/v1/objects/hosts/10.102.58.77
>> <https://localhost:5665/v1/objects/hosts/10.102.58.77>' -H "Accept:
>> application/json" -X PUT -d '{ "templates": [ "generic-host" ],
>> "attrs": { "address": ?10.102.58.77?}}
>>
>> curl -k -s -u icingaadmin:icinga 'https://
>> <https://localhost:5665/v1/objects/hosts/10.102.58.77>icinga-cluster-6.englab.juniper.net:5665/v1/objects/hosts/10.102.58.77
>> <https://localhost:5665/v1/objects/hosts/10.102.58.77>' -H "Accept:
>> application/json" -X DELETE
>>
>>
>> This is causing the Icinga process on one of the icinga node to crash .
>
>Any logs or details on that crash?
>
>Kind regards,
>Michael
>
>
>> And I see the log in the other node :
>>
>> [2015-12-14 17:15:55 -0800] warning/JsonRpcConnection: Error while
>> reading JSON-RPC message for identity
>> ?icinga-cluster-5.englab.juniper.net': Error: std::exception
>>
>> (0) libbase.so: void
>> boost::throw_exception<icinga::openssl_error>(icinga::openssl_error
>> const&) (+0x97) [0x7fc324760c67]
>> (1) libbase.so: void
>> boost::exception_detail::throw_exception_<icinga::openssl_error>(icinga::openssl_error
>> const&, char const*, char const*, int) (+0x40) [0x7fc324760d10]
>> (2) libbase.so: icinga::TlsStream::HandleError() const (+0xbc)
>> [0x7fc3246fdd2c]
>> (3) libbase.so: icinga::TlsStream::Read(void*, unsigned long, bool)
>> (+0x83) [0x7fc3246fdeb3]
>> (4) libbase.so:
>> icinga::StreamReadContext::FillFromStream(boost::intrusive_ptr<icinga::Stream>
>> const&, bool) (+0x7c) [0x7fc32470d9ac]
>> (5) libbase.so:
>> icinga::NetString::ReadStringFromStream(boost::intrusive_ptr<icinga::Stream>
>> const&, icinga::String*, icinga::StreamReadContext&, bool) (+0xce)
>> [0x7fc32471c0ce]
>> (6) libremote.so:
>> icinga::JsonRpc::ReadMessage(boost::intrusive_ptr<icinga::Stream>
>> const&, boost::intrusive_ptr<icinga::Dictionary>*,
>> icinga::StreamReadContext&, bool) (+0x3d) [0x7fc321c24cad]
>> (7) libremote.so: icinga::JsonRpcConnection::ProcessMessage() (+0x65)
>> [0x7fc321c459f5]
>> (8) libremote.so: icinga::JsonRpcConnection::DataAvailableHandler()
>> (+0x38) [0x7fc321c62848]
>> (9) libbase.so: boost::signals2::detail::signal_impl<void
>> (boost::intrusive_ptr<icinga::Stream> const&),
>> boost::signals2::optional_last_value<void>, int, std::less<int>,
>> boost::function<void (boost::intrusive_ptr<icinga::Stream> const&)>,
>> boost::function<void (boost::signals2::connection const&,
>> boost::intrusive_ptr<icinga::Stream> const&)>,
>> boost::signals2::mutex>::operator()(boost::intrusive_ptr<icinga::Stream>
>> const&) (+0x1cc) [0x7fc324794f2c]
>> (10) libbase.so: icinga::Stream::SignalDataAvailable() (+0x30)
>> [0x7fc324743620]
>> (11) libbase.so: icinga::TlsStream::OnEvent(int) (+0x3a8) [0x7fc324743b08]
>> (12) libbase.so: icinga::SocketEvents::ThreadProc() (+0x23a)
>> [0x7fc3247406aa]
>> (13) libboost_thread.so.1.54.0: <unknown function> (+0xba4a)
>> [0x7fc3250a9a4a]
>> (14) libpthread.so.0: <unknown function> (+0x8182) [0x7fc324a16182]
>> (15) libc.so.6: clone (+0x6d) [0x7fc32388347d]
>>
>>
>>
>>
>> I am using ubuntu with these versions:
>>
>> ii icinga2 2.4.1-1~ppa1~trusty1 amd64 host and
>> network monitoring system
>> ii icinga2-bin 2.4.1-1~ppa1~trusty1 amd64 host and
>> network monitoring system - daemon
>> ii icinga2-common 2.4.1-1~ppa1~trusty1 all host and
>> network monitoring system - common files
>> ii icinga2-doc 2.4.1-1~ppa1~trusty1 all host and
>> network monitoring system - documentation
>> ii icinga2-ido-mysql 2.4.1-1~ppa1~trusty1 amd64 host
>> and network monitoring system - MySQL support
>> ii icingaweb2 2.1.0-2~~ppa1
>> all simple and responsive web interface for Icinga
>> ii icingaweb2-module-doc 2.1.0-2~~ppa1
>> all simple and responsive web interface for Icinga -
>> documentation module
>> ii icingaweb2-module-monitoring 2.1.0-2~~ppa1
>> all simple and responsive web interface for Icinga -
>> monitoring module
>> ii libicinga2 2.4.1-1~ppa1~trusty1 amd64 host and
>> network monitoring system - internal libraries
>> ii php-icinga 2.1.0-2~~ppa1
>> all PHP library to communicate with and use Icinga
>>
>> Please help , am I missing anything .
>>
>>
>> Thanks,
>> mgochhait
>>
>>
>>
>> _______________________________________________
>> icinga-users mailing list
>> [email protected]
>> https://lists.icinga.org/mailman/listinfo/icinga-users
>
>
>--?
>Michael Friedrich, DI (FH)
>Senior Developer
>
>NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
>Tel: +49 911 92885-0 | Fax: +49 911 92885-77
>CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
>http://www.netways.de | [email protected]
>
>** OSDC 2016 - April - netways.de/osdc **
>** OSBConf 2016 - September - osbconf.org **
>
>
>------------------------------
>
>Message: 2
>Date: Wed, 16 Dec 2015 19:57:52 +0100
>From: Michael Friedrich <[email protected]>
>To: <[email protected]>
>Subject: Re: [icinga-users] Filer hosts by user_name on icingaweb2
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="utf-8"; format=flowed
>
>Am 14.12.2015 um 13:36 schrieb Jorge Ferrando:
>> Hello
>>
>> When we were using nagios the hosts and services shown on the web
>> interface where those that had the logged in user as a contact.
>
>That's fairly ugly as it requires to (ab)use contacts for notifications
>also for web auth.
>
>>
>> Is it possible to do this with icinga2? We have a big number of hosts
>> and services and we'd like to see only those ones each person is
>> responsible of.
>
>I'd personally throw that strategy away, and go for a better permission
>model, e.g. on hostgroups, host names or custom variables/attributes
>which is pretty feature-rich in Icinga Web 2 imho.
>
>Kind regards,
>Michael
>
>--?
>Michael Friedrich, DI (FH)
>Senior Developer
>
>NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
>Tel: +49 911 92885-0 | Fax: +49 911 92885-77
>CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
>http://www.netways.de | [email protected]
>
>** OSDC 2016 - April - netways.de/osdc **
>** OSBConf 2016 - September - osbconf.org **
>
>
>------------------------------
>
>Message: 3
>Date: Wed, 16 Dec 2015 19:59:44 +0100
>From: Michael Friedrich <[email protected]>
>To: <[email protected]>
>Subject: Re: [icinga-users] Icinga 2.4 does not start after update
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="utf-8"; format=flowed
>
>Am 24.11.2015 um 12:25 schrieb Daniel Guillermo Bareiro:
>>> Hi,
>> Hi, Michael. Thanks for your reply.
>>
>>>> -------------------------------------------------------------------------------
>>>> root@icinga2:~# /etc/init.d/icinga2 checkconfig
>>>> (...)
>>>> information/ConfigItem: Committing config items
>>>> critical/config: Error: An object with type 'Service' and name
>>>> 'localhost!ssh' already exists (in
>>>> /etc/icinga2/conf.d/hosts/localhost/ssh.conf: 6:1-6:20), new declaration:
>>>> in /etc/icinga2/conf.d/services.conf: 47:1-47:19
>>>> Location: in /etc/icinga2/conf.d/services.conf: 47:1-47:19
>>>> /etc/icinga2/conf.d/services.conf(45): * the custom attribute `os` set to
>>>> `Linux`.
>>>> /etc/icinga2/conf.d/services.conf(46): */
>>>> /etc/icinga2/conf.d/services.conf(47): apply Service "ssh" {
>>>> ^^^^^^^^^^^^^^^^^^^
>>>> /etc/icinga2/conf.d/services.conf(48): import "generic-service"
>>>> /etc/icinga2/conf.d/services.conf(49):
>>>>
>>>> critical/config: 1 error
>>>> [FAIL] checking Icinga2 configuration. Check
>>>> '/var/log/icinga2/startup.log' for details. ... failed!
>>>> -------------------------------------------------------------------------------
>>>>
>>>> There seems to be a double definition of the ssh service check. But I
>>>> think the
>>>> definitions in /etc/icinga 2/conf.d/hosts/localhost are standard
>>>> definitions
>>>> provided with Icinga, right? I think I did not add any of these.
>>> Nope. Afaik we had that with versions older than 2.2 but changed that using
>>> apply rules.
>>> Probably you've upgraded from a rather old version, and missed the
>>> Changelog entries.
>> Can be, but honestly I do not remember to have installed any package from a
>> previous version to Icinga2.
>>
>>> The current tree is also described on the docs, you can safely move away
>>> the hosts directory.
>> I've been reviewing this [1] documentation and see it mentions only the
>> "conf.d" directory but not a directory tree. If I'm missing something, could
>> you please tell me what part of the documentation do you mean?
>
>
>http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/configuring-icinga2-first-steps#configuring-icinga2-overview
>
>Anyways, it does not really matter. It is up to *you* organizing your
>configuration tree. Best idea for a good learning curve - throw it all
>away and start from scratch.
>
>Kind regards,
>Michael
>
>>
>> Currently I was using these files in the "host" directory:
>>
>> -------------------------------------------------------------------------------
>> root@icinga2:/etc/icinga2/conf.d/hosts# ll
>> total 20
>> -rw-r--r-- 1 root root 322 sep 18 2014 localhost.conf
>> -rw-r--r-- 1 root root 13657 mar 22 2015 local-network.conf
>> -------------------------------------------------------------------------------
>>
>> Where local-network.conf has the definitions of the hosts and services to be
>> monitored on the local network. Perhaps the suggestion is to move these
>> files to the root of "conf.d" and delete the "hosts" directory?
>>
>> After having removed the "localhost" directory I was able to make Icinga2 is
>> up and running.
>>
>>> Have a nice weekend,
>> Thank you. I hope you also had a good weekend :-)
>>
>> Best regards,
>> Daniel
>>
>> [1] http://docs.icinga.org/icinga2/latest/doc/module/icinga2/toc
>> _______________________________________________
>> icinga-users mailing list
>> [email protected]
>> https://lists.icinga.org/mailman/listinfo/icinga-users
>
>
>--?
>Michael Friedrich, DI (FH)
>Senior Developer
>
>NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
>Tel: +49 911 92885-0 | Fax: +49 911 92885-77
>CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
>http://www.netways.de | [email protected]
>
>** OSDC 2016 - April - netways.de/osdc **
>** OSBConf 2016 - September - osbconf.org **
>
>
>------------------------------
>
>Message: 4
>Date: Wed, 16 Dec 2015 20:00:38 +0100
>From: Michael Friedrich <[email protected]>
>To: <[email protected]>
>Subject: Re: [icinga-users] Help with pnp4nagios graph in icingaweb2
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="utf-8"; format=flowed
>
>Am 13.12.2015 um 10:00 schrieb Madhusmita Gochhait:
>>
>> Hi ,
>>
>>
>> I am stuck with a issue , where pnp4nagios graph are not getting
>> displayed .It says "could not load image"
>>
>Screenshot?
>
>> I see rrd files getting updated frequently with no issues . Cannot
>> find anything in the logs also . I have pnp4nagios running in npcd
>> mode . Please suggest if i am missing anything .
>>
>
>Are these graphs accessible from /pnp4nagios in your browser?
>
>Kind regards,
>Michael
>
>
>--?
>Michael Friedrich, DI (FH)
>Senior Developer
>
>NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
>Tel: +49 911 92885-0 | Fax: +49 911 92885-77
>CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
>http://www.netways.de | [email protected]
>
>** OSDC 2016 - April - netways.de/osdc **
>** OSBConf 2016 - September - osbconf.org **
>
>
>------------------------------
>
>Message: 5
>Date: Wed, 16 Dec 2015 20:01:41 +0100
>From: Michael Friedrich <[email protected]>
>To: <[email protected]>
>Subject: Re: [icinga-users] Icinga Server address macro
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="utf-8"; format=flowed
>
>Am 11.12.2015 um 13:47 schrieb Jorge Ferrando:
>> Hi there
>>
>> Is there any runtime macro to use in the commands that contains the
>> Icinga server IP address?
>
>No, but what's wrong with using Linux commands >:-)
>
>You might open a feature request, since we already resolve dns with
>NodeName if not set by the user (using FQDN).
>
>Kind regards,
>Michael
>
>
>--?
>Michael Friedrich, DI (FH)
>Senior Developer
>
>NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
>Tel: +49 911 92885-0 | Fax: +49 911 92885-77
>CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
>http://www.netways.de | [email protected]
>
>** OSDC 2016 - April - netways.de/osdc **
>** OSBConf 2016 - September - osbconf.org **
>
>
>------------------------------
>
>Message: 6
>Date: Wed, 16 Dec 2015 20:02:50 +0100
>From: Michael Friedrich <[email protected]>
>To: <[email protected]>
>Subject: Re: [icinga-users] Alert History not show schedule downtime
> comments
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="utf-8"; format=flowed
>
>Am 11.12.2015 um 13:10 schrieb Renato Pinheiro:
>> Hello,
>>
>> I have one server with icinga2 + classic ui, and before update for
>> icinga2 my server
>
>Which update from x to y?
>
>> that was icinga show the comments of old schedules
>> downtimes in Alert History.
>
>Please add a screenshot, I cannot follow.
>
>Kind regards,
>Michael
>
>> How i can see the comments again?
>>
>> Example:
>> NOW icinga2: [12-11-2015 11:25:52] SERVICE DOWNTIME ALERT:
>> host1;cpu;STARTED; Checkable has entered a period of scheduled downtime.
>> OLD icinga : [12-11-2015 11:25:52] SERVICE DOWNTIME ALERT:
>> host1;cpu;STARTED; My comment
>>
>> Regards.
>>
>
>
>--?
>Michael Friedrich, DI (FH)
>Senior Developer
>
>NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
>Tel: +49 911 92885-0 | Fax: +49 911 92885-77
>CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
>http://www.netways.de | [email protected]
>
>** OSDC 2016 - April - netways.de/osdc **
>** OSBConf 2016 - September - osbconf.org **
>
>
>------------------------------
>
>Message: 7
>Date: Wed, 16 Dec 2015 20:06:57 +0100
>From: Michael Friedrich <[email protected]>
>To: <[email protected]>
>Subject: Re: [icinga-users] Dependencies, disable checks on service
> state
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset="utf-8"; format=flowed
>
>Am 08.12.2015 um 07:51 schrieb Ronny Becker:
>> Hello,
>> I am searching for a config example to disable all child checks (Host
>> and Services) if a service is not in "OK" state.
>>
>> for example:
>> NET -> Router1 -> Internet -> Router2 -> Switches -> Hosts
>>
>> Router2 has a ping service. If the rtt is >200ms, then this service
>> enters warning state and all Host and Service checks behind Router2
>> should be suspended.
>> In the documentation I only find Host dependencies and Service to
>> Service dependencies?!
>Though it's not limited, just try it, for example.
>
>apply Dependency "router1" to Service {
> parent_host_name = "router1"
>
> states = [ Up ]
>
> ...
>
> assign where host.name == "NET-host" && service.name == "NET"
>}
>
>Kind regards,
>Michael
>
>>
>> Thanks
>> Ronny
>>
>>
>> _______________________________________________
>> icinga-users mailing list
>> [email protected]
>> https://lists.icinga.org/mailman/listinfo/icinga-users
>
>
>--?
>Michael Friedrich, DI (FH)
>Senior Developer
>
>NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
>Tel: +49 911 92885-0 | Fax: +49 911 92885-77
>CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
>http://www.netways.de | [email protected]
>
>** OSDC 2016 - April - netways.de/osdc **
>** OSBConf 2016 - September - osbconf.org **
>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>icinga-users mailing list
>[email protected]
>https://lists.icinga.org/mailman/listinfo/icinga-users
>
>
>------------------------------
>
>End of icinga-users Digest, Vol 24, Issue 22
>********************************************
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
