Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #8493] Misleading ApiListener connection log messages on a master (Endpoint vs Zone) #2646

Closed
icinga-migration opened this issue Feb 20, 2015 · 4 comments
Labels
area/distributed Distributed monitoring (master, satellites, clients) bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/8493

Created by mfriedrich on 2015-02-20 13:59:11 00:00

Assignee: mfriedrich
Status: Resolved (closed on 2015-02-20 14:15:03 00:00)
Target Version: 2.3.0
Last Update: 2015-02-20 16:10:08 00:00 (in Redmine)

Icinga Version: v2.2.0-504-ge2815de
Backport?: Not yet backported
Include in Changelog: 1

The log output says that 'master' and 'sattelite' are my endpoints. Apparently they are the zones configured.

[2015-02-20 14:53:22  0100] debug/ApiListener: Not connecting to Endpoint 'master' because we're already connected to it.
[2015-02-20 14:53:22  0100] debug/ApiListener: Not connecting to Endpoint 'satellite' because we're already connected to it.

object Endpoint "icinga2a" {
  host = "localhost"
  port = 7000
}

object Endpoint "icinga2b" {
  host = "localhost"
  port = 8000
}

object Endpoint "icinga2c" {
  host = "localhost"
  port = 9500
}

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

}

object Zone "satellite" {
  endpoints = [ "icinga2c" ]
  parent = "master"
}

e.g.

                        if (my_zone != zone && my_zone != zone->GetParent() && zone != my_zone->GetParent()) {
                                Log(LogDebug, "ApiListener")
                                    << "Not connecting to Endpoint '" << zone->GetName() << "' because it's not in the same zone, a parent or a child zone.";
                                continue;
                        }

Changesets

2015-02-20 14:11:44 00:00 by mfriedrich ba77d7b

ApiListener: Fix misleading connection log messages

fixes #8493
@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-20 14:00:12 00:00

  • Subject changed from Misleading ApiListener connection log messages (Endpoint vs Zone) to Misleading ApiListener connection log messages on a master (Endpoint vs Zone)

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-20 14:07:58 00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich
  • Target Version set to 2.3.0

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-20 14:15:03 00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset ba77d7b.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-20 16:08:41 00:00

  • Estimated Hours set to 0.25

@icinga-migration icinga-migration added bug Something isn't working area/distributed Distributed monitoring (master, satellites, clients) labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.3.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/distributed Distributed monitoring (master, satellites, clients) bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant