cancel
Showing results for 
Search instead for 
Did you mean: 

debugging LB_FAILED event

Guillaume_Rouss
Nimbostratus
Nimbostratus

Hello list.

 

I'm using this irule in order to deliver a user-friendly error page to users when a service is down:

when LB_FAILED {    log local0.debug "LB_FAILED for [virtual name]"    snatpool server_snat_pool    LB::reselect pool fallback_https_pool    persist none }

 

Following suggestion from https://devcentral.f5.com/s/feed/0D51T00006i7Q1cSAE, I added a call to [event info] in the log message, in order to get a better idea of unexplained such events. However, this isn't really useful, as:

  • 50% of log messages have no reason
  • 50% of log messages have "connection limit" as reason, whereas I don't have any explicit limit defined at virtual server level, pool level or node level

 

So, is there any other place I should check for connection limits, and is there any better way to identify LB_FAILED event reasons ?

 

0 REPLIES 0