Forum Discussion
7 Replies
Sort By
- Deb_Allen_18Historic F5 AccountI don't see an alert or existing log message you could leverage, either.
when CLIENT_ACCEPTED { if { [active_members myPool] < 1 } { log local0. "No nodes available for virtual server [virtual name] at [IP::local_addr]:[TCP::local_port]" reject } }
- ken_wolff_10732NimbostratusWow, that was easy. Your suggestion worked like a champ. I'm getting tons of repeat log messages, however (only one email, fotunately). Can I limit the number of log messages? Thanks, Ken
- JRahmAdminYou could use the clock command to log the condition on the minute, or whatever interval you choose.
when CLIENT_ACCEPTED { if { [active_members myPool] < 1 } { if { [clock format [clock seconds] -format {%S} ] eq "00" } { log local0. "No nodes available for virtual server [virtual name] at [IP::local_addr]:[TCP::local_port]" } reject } }
- JRahmAdminupdated to move the reject statement out of the log condition.
- Deb_Allen_18Historic F5 AccountYou might also just try removing the local0. reference & use this log line instead:
Without the specific destination reference, you'll probably see the syslog summary messages instead:No nodes available for virtual server myVirtual at 1.1.1.1:80log "No nodes available for virtual server [virtual name] at [IP::local_addr]:[TCP::local_port]"
- ken_wolff_10732NimbostratusRemoving local0 didn't make any difference. Thanks, Ken
- ken_wolff_10732NimbostratusHow could I check for no nodes available for, say, a period of 5 minutes, rather than immediately? Thanks, Ken