LB_FAILED. Specific reasons for the failure

Is it possible to see what triggers an LB_FAILED event.

when LB_FAILED {

log0. "LB Failed because of [::ERRORS::XYZ] "

}

I see nothing in the documentation to support troubleshooting in this way. Is there anything we can use?

In 11.0+ you can use [event info]:

event info

Returns a string describing why this event was fired (v11+ only). Added to support LB::queue/LB_QUEUED so limited to LB_FAILED currently, but is anticipated that this will become more generalized in the future.

Aaron

Thanks Aaron. Sadly we are track 10. I’ll test this out in the lab though.

i tried this and nothing came back log local0. “load balance error: [event info]”. any ideas?? I had set the member through a ‘node 11.22.33.44 443’ command. it has worked until today.

more info.. the message I got was: Load balance FAILED!? node: 52.36.150.63:443 reason: -- for the command in LB_FAILED: log local0. “Load balance FAILED!? node: [LB::server addr]:[LB::server port] reason: -[event info]-” so it has a server and port but still fails.

Any other suggestions on this one? It is very frustrating not being able to determine why the LB_Failed event was raised. event info is not returning anything for me either and I am in version 12.x. What is more, I am printing the status of the selected LB Node on the LB_Failed event and is coming back as up. Any help would be REALLY appreciated.