java.lang.IllegalArgumentException: endpoint with id :default does not appear in configuration for service :puppetlabs.services.master.master-service/master-service

JIRA | Jeremy Barlow | 1 year ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Per code changes committed for SERVER-1071, if the "master-service" entry in the web-router-service config has an "invalid-in-puppet-4" key in it, the server will fail to startup with an error like the following: {noformat} 2016-01-28 07:59:31,285 INFO [main] [p.s.m.master-service] Master Service adding ring handlers 2016-01-28 07:59:31,292 ERROR [main] [p.t.internal] Error during service init!!! java.lang.IllegalArgumentException: endpoint with id :default does not appear in configuration for service :puppetlabs.services.master.master-service/master-service at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invoke(webrouting_service_core.clj:55) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$compute_common_elements.invoke(webrouting_service_core.clj:68) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$eval11614$add_ring_handler_BANG___11621$fn__11622.invoke(webrouting_service_core.clj:114) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$eval11614$add_ring_handler_BANG___11621.invoke(webrouting_service_core.clj:110) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service$reify__11980$service_fnk__5056__auto___positional$reify__11988.add_ring_handler(webrouting_service.clj:51) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval11756$fn__11933$G__11730__11941.invoke(webrouting_service.clj:10) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval11756$fn__11933$G__11729__11950.invoke(webrouting_service.clj:10) ~[na:na] at clojure.core$partial$fn__4527.invoke(core.clj:2494) ~[clojure-1.7.0.jar:na] at puppetlabs.services.master.master_service$reify__18484$service_fnk__5056__auto___positional$reify__18501.init(master_service.clj:63) ~[na:na] {noformat} The failure does not occur if the "invalid-in-puppet-4" key is removed from the configuration. Even though it is no longer used in Puppet Server 2.1 and later, "invalid-in-puppet-4" was a valid key at the time Puppet Server 2.0 was released. For backward compatibility, it would be best for Puppet Server to continue to tolerate the presence of this key, still booting to ready but just ignoring the value for the key as Puppet Server 2.2.0 does.

    JIRA | 1 year ago | Jeremy Barlow
    java.lang.IllegalArgumentException: endpoint with id :default does not appear in configuration for service :puppetlabs.services.master.master-service/master-service
  2. 0

    Per code changes committed for SERVER-1071, if the "master-service" entry in the web-router-service config has an "invalid-in-puppet-4" key in it, the server will fail to startup with an error like the following: {noformat} 2016-01-28 07:59:31,285 INFO [main] [p.s.m.master-service] Master Service adding ring handlers 2016-01-28 07:59:31,292 ERROR [main] [p.t.internal] Error during service init!!! java.lang.IllegalArgumentException: endpoint with id :default does not appear in configuration for service :puppetlabs.services.master.master-service/master-service at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invoke(webrouting_service_core.clj:55) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$compute_common_elements.invoke(webrouting_service_core.clj:68) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$eval11614$add_ring_handler_BANG___11621$fn__11622.invoke(webrouting_service_core.clj:114) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$eval11614$add_ring_handler_BANG___11621.invoke(webrouting_service_core.clj:110) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service$reify__11980$service_fnk__5056__auto___positional$reify__11988.add_ring_handler(webrouting_service.clj:51) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval11756$fn__11933$G__11730__11941.invoke(webrouting_service.clj:10) ~[na:na] at puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval11756$fn__11933$G__11729__11950.invoke(webrouting_service.clj:10) ~[na:na] at clojure.core$partial$fn__4527.invoke(core.clj:2494) ~[clojure-1.7.0.jar:na] at puppetlabs.services.master.master_service$reify__18484$service_fnk__5056__auto___positional$reify__18501.init(master_service.clj:63) ~[na:na] {noformat} The failure does not occur if the "invalid-in-puppet-4" key is removed from the configuration. Even though it is no longer used in Puppet Server 2.1 and later, "invalid-in-puppet-4" was a valid key at the time Puppet Server 2.0 was released. For backward compatibility, it would be best for Puppet Server to continue to tolerate the presence of this key, still booting to ready but just ignoring the value for the key as Puppet Server 2.2.0 does.

    JIRA | 1 year ago | Jeremy Barlow
    java.lang.IllegalArgumentException: endpoint with id :default does not appear in configuration for service :puppetlabs.services.master.master-service/master-service

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      endpoint with id :default does not appear in configuration for service :puppetlabs.services.master.master-service/master-service

      at puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invoke()
    2. puppetlabs.trapperkeeper.services
      webrouting_service$eval11756$fn__11933$G__11729__11950.invoke
      1. puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invoke(webrouting_service_core.clj:55)[na:na]
      2. puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$compute_common_elements.invoke(webrouting_service_core.clj:68)[na:na]
      3. puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$eval11614$add_ring_handler_BANG___11621$fn__11622.invoke(webrouting_service_core.clj:114)[na:na]
      4. puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$eval11614$add_ring_handler_BANG___11621.invoke(webrouting_service_core.clj:110)[na:na]
      5. puppetlabs.trapperkeeper.services.webrouting.webrouting_service$reify__11980$service_fnk__5056__auto___positional$reify__11988.add_ring_handler(webrouting_service.clj:51)[na:na]
      6. puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval11756$fn__11933$G__11730__11941.invoke(webrouting_service.clj:10)[na:na]
      7. puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval11756$fn__11933$G__11729__11950.invoke(webrouting_service.clj:10)[na:na]
      7 frames
    3. Clojure
      core$partial$fn__4527.invoke
      1. clojure.core$partial$fn__4527.invoke(core.clj:2494)[clojure-1.7.0.jar:na]
      1 frame
    4. puppetlabs.services.master
      master_service$reify__18484$service_fnk__5056__auto___positional$reify__18501.init
      1. puppetlabs.services.master.master_service$reify__18484$service_fnk__5056__auto___positional$reify__18501.init(master_service.clj:63)[na:na]
      1 frame