Solved: Getting deployment error code "application.bootstr... - Page 2

adevegowda · 12-24-2017 10:57 PM

When we are trying to deploy one of our API Proxies, we are getting the following error:

Error in deployment for environment dev.The revision is deployed, but traffic cannot flow. com.apigee.kernel.exceptions.spi.UncheckedException{ code = application.bootstrap.FailedToConfigure, message = Configuration failed, associated contexts = []}

screen-shot-2017-12-25-at-122513-pm.png

adevegowda

1. Checked the Message Processor logs and noticed that the following error occurred during deployment of the API Proxy:

2017-12-22 00:13:49,057  Apigee-Main-87446 INFO  MESSAGING.CONFIGURATION - MessageProcessorServiceImpl.configure() : configuring [DeployEvent{organization='myorg', application='myapi', applicationRevision='42', deploymentSpec=basepath=/;env=dev;, deploymentID=null}]

2017-12-22 00:13:49,263  Apigee-Main-87446 INFO  MESSAGING.RUNTIME - AbstractConfigurator.loadXMLConfigurations() : loading entities [] for class class com.apigee.messaging.config.beans.TargetServerBean

2017-12-22 00:13:49,318  Apigee-Main-87446 ERROR c.a.p.h.d.DNSCachedAddress - DNSCachedAddress.refresh() : Unable to resolve host : input-prd-sps.cloud.splunk.com: Name or service not known

2017-12-22 00:13:49,323  Apigee-Main-87446 ERROR MESSAGING.RUNTIME - AbstractConfigurator.handleUpdate() : Fatal error deploying proxy: {}

com.apigee.rest.framework.ValidationException: Invalid syslog config: Invalid HostName 'input-prd-sps.cloud.splunk.com' for Syslog handler
        at com.apigee.messaging.runtime.destinations.SyslogDestination.<init>(SyslogDestination.java:44) ~[message-processor-1.0.0.jar:na]
        at com.apigee.messaging.runtime.destinations.SysLoggerFactory.getInstance(SysLoggerFactory.java:39) ~[message-processor-1.0.0.jar:na]
        at com.apigee.messaging.runtime.destinations.DestinationRegistry.newDestination(DestinationRegistry.java:44) ~[message-processor-1.0.0.jar:na]
        at com.apigee.steps.messagelogging.MessageLoggingStepDefinition.populateDestinations(MessageLoggingStepDefinition.java:118) ~[message-logging-1.0.0.jar:na]
        at com.apigee.steps.messagelogging.MessageLoggingStepDefinition.handleAdd(MessageLoggingStepDefinition.java:99) ~[message-logging-1.0.0.jar:na]
...<snipped>

2. Tried to telnet to the host name from the Message Processor and got the following error:

[adevegowda@rmp1 ~]$ telnet input-prd-sps.cloud.splunk.com
telnet: input-prd-sps.cloud.splunk.com: Name or service not known
input-prd-sps.cloud.splunk.com: Unknown host
[adevegowda@rmp1 ~]$

3. Checked the API Proxy and found that the host name "input-prd-sps.cloud.splunk.com" was used in one of the MessageLogging policy.

4. Replaced the Host name "input-prd-sps.cloud.splunk.com" with the proper host name. Saved the changes, undeployed and deployed the API Proxy successfully without any errors.

We need to ensure that we are using the proper/valid host name and port # in MessageLogging, ServiceCallout or any other policies to avoid this type of errors.

View solution in original post

Getting deployment error code "application.bootstrap.FailedToConfigure"