LVS
lvs-devel
Google
 
Web LinuxVirtualServer.org

[PATCH] ipvs: make "no destination available" message more informative

To: lvs-devel@xxxxxxxxxxxxxxx
Subject: [PATCH] ipvs: make "no destination available" message more informative
From: Patrick Schaaf <netdev@xxxxxx>
Date: Fri, 11 Feb 2011 14:01:12 +0100
When IP_VS schedulers do not find a destination, they output a terse
"WLC: no destination available" message through kernel syslog, which I
can not only make sense of because syslog puts them in a logfile
together with keepalived checker results.

This patch makes the output a bit more informative, by telling you which
virtual service failed to find a destination.

Example output:

kernel: [1539214.552233] IPVS: wlc: TCP 192.168.8.30:22 - no destination
available
kernel: [1539299.674418] IPVS: wlc: FWM 22 0x00000016 - no destination
available

I have tested the code for IPv4 and FWM services, as you can see from
the example; I do not have an IPv6 setup to test the third code path
with.

To avoid code duplication, I put a new function ip_vs_scheduler_err()
into ip_vs_sched.c, and use that from the schedulers instead of calling
IP_VS_ERR_RL directly.

The patch is against 2.6.36.2, as that's what I have running. It still
applies with two hunks shifted to 2.6.38-rc4, and builds there without
warnings.

Please review and consider for inclusion in upcoming kernels.

best regards
  Patrick


Attachment: ip_vs_scheduler_err.patch
Description: Text Data

<Prev in Thread] Current Thread [Next in Thread>