Troubleshooting
Error messages provide information about why a manager cannot contact a member. This event occurs when trying to add the member to a pool, or after it has been added and another issue arises (for example, the member is not up, the REST API authentication code has been removed, and so on).
The system log for pool management is at the INFO level. Managers log messages before and after sending requests to members (but not the contents of the request). Members log requests from managers. You can filter for Pool Management to get relevant logs.
Example Logs
On a manager, a failed call to add a member to a pool:
Mar 13 17:48:13 kabar-vva39 webasd[6791]: [web.ERR]: web: restd: Pool Management API call - addMember. Result - failed. Error - This member is currently a part of a different pool.
A failed call to remove a member from a pool (the user had already manually removed the member):
Mar 13 18:21:31 kabar-vva39 webasd[5490]: [web.ERR]: web: restd: Pool Management API call - removeMember. Result - failed. Error - Error attempting to get data - Request sent from 'kabar39', but this box's pool name is 'Not Available'. Wrong pool.
A successful REST request to get the member’s status:
Mar 13 18:23:10 kabar-vva39 webasd[5490]: [web.INFO]: web: restd: Pool Management API call - memberStatus. Result - success
On a member, successful call examples:
Successful config query: Mar 17 15:48:40 kabar-vva15 restd[4218]: [web.INFO]: web: restd: Pool Management API Request Received. Request - getMgmtLocalChildrenNames. Request successful.
Successful config query: Mar 17 15:48:40 kabar-vva15 restd[4218]: [web.INFO]: web: restd: Pool Management API Request Received. Request - present. Request successful.