Bug #2077
Input fails to start because REST endpoint in Splunkd failed to respond
Start date:
09/29/2017
Due date:
% Done:
100%
Related issues
Associated revisions
Made REST call resilient to transient Splunkd connection issues
Reference #2077
History
#1 Updated by Luke Murphey about 7 years ago
This happened right after upgrade.
Here was the error:
Unable to find the app configuration for the specified configuration
Followed by:
Execution failed
#2 Updated by Luke Murphey about 7 years ago
This blew up when attempting to get the app configuration.
Solutions so this include:- Trying the REST endpoint repeatedly until it succeeds
- Restarting the endpoint
#3 Updated by Luke Murphey about 7 years ago
- Subject changed from Input fails to start to Input fails to start because REST endpoint in Splunkd failed to respond
- Status changed from New to Closed
#4 Updated by Luke Murphey about 7 years ago
- % Done changed from 0 to 100
#5 Updated by Luke Murphey about 7 years ago
- Project changed from Website Input to Website Monitoring
- Category deleted (
Input: Web Spider) - Target version changed from 4.5.1 to 261
#6 Updated by Luke Murphey about 7 years ago
- Copied to Bug #2079: Input fails to start because REST endpoint in Splunkd failed to respond added
#7 Updated by Luke Murphey about 7 years ago
- Target version changed from 261 to 2.6