Forum Discussion

Ken_B_50116's avatar
Ken_B_50116
Icon for Cirrostratus rankCirrostratus
Nov 25, 2015
Solved

Pool member not found error for a node that doesn't exist in the config

I am running LTM 11.4.1 HF7. I am getting this in the LTM log 4 to 6 times a minute: Nov 25 09:22:02 F5-LTM-TMC-01 err mcpd[7840]: 01020036:3: The requested pool member (/WebTeam/pool_webextorg /...
application delivery
LTM
  • Ken_B_50116's avatar
    Ken_B_50116
    May 18, 2016

    This was finally resolved after 4 months with F5 tech support. Ultimately F5 had to reproduce the issue on a test system. F5 was able to tell me the name of the user account associated with the error being logged. I contacted that person. They were running a .net app using iControl that was monitoring pools statuses. The config in the app had some bad data and was triggering the error messages.

     

Ken_B_50116's avatar
Ken_B_50116
Icon for Cirrostratus rankCirrostratus

I ended up contacting F5 support for this issue. The advice so far is based around article SOL13030. The theory is (from the article), "The text configuration files (such as /config/bigip.conf) and the running configuration loaded in the mcpd process from the binary configuration image are out of synchronization" and, "In cases where the system is unable to load the binary configuration, or where the binary image is no longer accurate, you can correct the situation by forcibly reloading the configuration."

 

The claimed fix is a simple command line operation and a reboot of each unit in the cluster. I am planning to carry this out later this week and will follow up here with the results.

 

Ken_B_50116's avatar
Ken_B_50116
Icon for Cirrostratus rankCirrostratus
Jun 02, 2016
I finally got this resolved. Thanks for F5 support for seeing this through. The problem was caused by someone in our internal development department who was running a .net app using iControl to query the LTMs to get pool status. Their app was querying for objects that did not exist. F5 support was able to tell me the user ID of the person involved with the odd errors, and talking to that person turned up the app and misconfigured query.