Shortlived.

Adding the additional clients resulted in core dump.

information/ConfigCompiler: Compiling config file:
/etc/icinga2/repository.dicinga2:
/usr/include/boost/smart_ptr/intrusive_ptr.hpp:162: T*
boost::intrusive_ptr<T>::operator->() const [with T = icinga::Type]:
Assertion `px != 0' failed.
/zones/uat-hq.zm.domain.com.conf

icinga2: /usr/include/boost/smart_ptr/intrusive_ptr.hpp:162: T*
boost::intrusive_ptr<T>::operator->() const [with T = icinga::Type]:
Assertion `px != 0' failed.
Caught SIGABRT.
Current time: 2015-09-03 12:02:32 +0200

icinga2: /usr/include/boost/smart_ptr/intrusive_ptr.hpp:162: T*
boost::intrusive_ptr<T>::operator->() const [with T = icinga::Type]:
Assertion `px != 0' failed.
icinga2: /usr/include/boost/smart_ptr/intrusive_ptr.hpp:162: T*
boost::intrusive_ptr<T>::operator->() const [with T = icinga::Type]:
Assertion `px != 0' failed.
Aborted (core dumped)

The config that caused the problem is not even one that I updated. Removing
the additional Host/Port statements, resolves the coredump issue.

H

On Thu, Sep 3, 2015 at 12:05 PM, Henti Smith <he...@geekware.co.za> wrote:

> After upgrading both Icinga2 servers to 2.3.9 I started connecting the
> Master to the Master of Masters (MoM) My configuration is :
>
>   MoM
>    |
>  Master
>    |
>  Clients
>
> The dashboard on the Master is working as expected. I have 6 clients
> connected, all working.
> The Dashboard on the MoM is showing 4 clients as expect with matching
> services.
> Two clients shows as not connected with log lag in access of 16000 days.
> All services pending.
>
> I've done a full reset of state on both clients and reconnected them, same
> situation.
>
> I connected a second master (also 2.39) to the MoM with 5 clients. Same
> situation. All clients show on the Master.
> Two clients shows as not connected with log lag in access of 16000 days.
> All services pending.
>
> The log files shows the following :
>
> [2015-09-03 11:44:09 +0200] debug/ApiListener: Not connecting to Endpoint '
> stg-qua-za-app01.int.domain.com' because the host/port attributes are
> missing.
>
> This is consistent for all clients not working as described above.
>
> The endpoint config are generated using update-config so all the configs
> are the same.
>
> If I go and add host and port attributes to the Endpoint, the hosts starts
> working again.
>
> Any ideas ?
>
> Regards
> Henti
>
>
> --
> --
>



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

Reply via email to