Troubleshoot Predix Search

Authentication Errors

You may encounter the following authentication error conditions in Predix Search:

Token Expired


{    
  "error": "invalid_token",  
  "error_description": "Token is expired. Expiration date is [Thu Sep 14 02:19:35 UTC 2017]. 
                        Current date is [Thu Sep 14 06:31:55 UTC 2017]"
}

Token Missing


{     
  "error": "unauthorized",    
  "error_description": "Full authentication is required to access this resource"
}

Token Incorrect


{  
  "error": "invalid_token",
  "error_description": "Malformed Access Token" 
}

Zone ID Missing

 
{  
  "error": "invalid_request",
  "error_description": "No zone specified for zone specific request: /_cluster/health"
}

Zone Authorities Access Not Set Up in UAA


{ 
  "error": "invalid_token",
  "error_description": "Unauthorized zone access by principal: admin for zone: 8a350557-3f87-4222-84f9-b016cbe36fb1" 
}

Cloud Foundry CLI Errors

Cloud Foundry CLI commands related to Predix Search may produce the following error conditions:

Data Node Count Exceeds the Maximum Allowed Limit

Error: Server error
Error code: 10001
Status code: 502,
Message: Service broker error: data_node_count: X is outside the minimum and maximum limit

Enable Dedicated Master Set to False for Data Node Count > 10

Error: Server error
Error code: 10001
Status code: 502
Message: Service broker error: data_node_count: X is > 10 and masterNode disabled

Odd Value Specified for Data Node Count and Multi-AZ is Enabled

Error: Server error
Error code: 10001
Status code: 502
Message: Service broker error: data_node_count: X is odd and multiAZ enabled