troubleshooting syslog traffic from thin clients to server

[john]

To (sort of) answer my own question. By adding -vv to my tcpdump I see
that this error seems to be part of the venerable "nbd0: Attempted
send on closed socket" which seems to happen whenever the server is
restarted but the client stays up. So maybe my question is two-fold:

1) could lots (approx 4000 packet/s of this sort of traffic be causing
my network issues that would impact end user performance
2) is there a way to  alleviate or at least "turn off" this complaint?

Thanks!

John

On Mon, Nov 16, 2009 at 2:47 PM, john <lists.john at gmail.com> wrote:
> Hi all,
>
> As I flail around looking for reasons why teachers are reporting
> general badness with the LTSP experience on Hardy, I note that there
> is a lot of
> traffic complaining about no syslog server on the servers LTSP facing
> interface e.g. 192.168.0.254
>
> I gathered this with:
>
>  tcpdump -i eth4
>
> 14:39:19.204412 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.warning, length: 73
> 14:39:19.205245 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.error, length: 64
> 14:39:19.206023 IP 192.168.0.227.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.error, length: 64
> 14:39:19.206160 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.warning, length: 73
> 14:39:19.206590 IP 192.168.0.202.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.info, length: 51
> 14:39:19.207638 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.error, length: 36
> 14:39:19.207919 IP 192.168.0.227.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.warning, length: 73
> 14:39:19.209731 IP 192.168.0.227.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.error, length: 64
> 14:39:19.210179 IP 192.168.0.175.syslog > 192.168.0.254.syslog: SYSLOG
> kernel.error, length: 118
>
> My understanding was that syslog from thin client to server was an
> option under hardy, but not on by default. Can anyone help me decipher
> this?
>
> Thanks!
>
> John
>