|
Home > Archive > alt.os.linux > November 2002 > Neighbour Table Overflow Error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Neighbour Table Overflow Error
|
|
| Dand Blackman 2002-11-25, 8:25 am |
| I'm new to linux and running Apache on RedHat 7.3 for a web server at
our high school. So far have managed to make this work pretty well
but lately when I go to the server console it has line after line of
'Neighbour Table Overflow' I've checked my usual sources and didn't
find anything related to this. Would apprediate any help finding the
source of this error....
David Blackman
| |
| Michael Heiming 2002-11-25, 9:24 am |
| Dand Blackman wrote:
> I'm new to linux and running Apache on RedHat 7.3 for a web server at
> our high school. So far have managed to make this work pretty well
> but lately when I go to the server console it has line after line of
> 'Neighbour Table Overflow' I've checked my usual sources and didn't
> find anything related to this. Would apprediate any help finding the
> source of this error....
Common reason, you have no loopback device configured.
Try:
# ifconfig lo
Michael Heiming
--
Remove +SIGNS, if you expect an answer
| |
| Dand Blackman 2002-11-25, 12:24 pm |
| On Mon, 25 Nov 2002 15:57:40 +0100, Michael Heiming
<michael+usenet@heiming.de> wrote:
>Dand Blackman wrote:
>
>> I'm new to linux and running Apache on RedHat 7.3 for a web server at
>> our high school. So far have managed to make this work pretty well
>> but lately when I go to the server console it has line after line of
>> 'Neighbour Table Overflow' I've checked my usual sources and didn't
>> find anything related to this. Would apprediate any help finding the
>> source of this error....
>
>Common reason, you have no loopback device configured.
>Try:
># ifconfig lo
>
>Michael Heiming
Loopback seems to be running on 127.0.0.1 and it has worked since the
server was set up. This server has been running since August and just
started getting the neighbour table overflow the past two weeks...
| |
| Michael Heiming 2002-11-25, 2:24 pm |
| Dand Blackman wrote:
[..]
> Loopback seems to be running on 127.0.0.1 and it has worked since the
$ cat /etc/sysconfig/network-scripts/ifcfg-lo
> server was set up. This server has been running since August and just
> started getting the neighbour table overflow the past two weeks...
You can find this message in the kernel source.
/usr/src/linux/net/ipv4/route.c
if (net_ratelimit())
printk(KERN_WARNING "Neighbour table overflow.\n");
rt_drop(rt);
return -ENOBUFS;
Looks like, one should enable martian source logging:
# for i in /proc/sys/net/ipv4/conf/*/log_martians; do echo 1 > $i;done
Could provide some more logging, you don't have iptables running and
recently changed your config? There may be other (new) boxes on your
net, or just new NICs, hard to tell, from here. You have to take a
look, for sure, running 'tcpdump' might offer more info/help, try 'man
tcpdump', it has more then a few options.
Good luck
Michael Heiming
--
Remove +SIGNS, if you expect an answer
| |
| Dand Blackman 2002-11-27, 10:25 am |
| On Mon, 25 Nov 2002 20:51:35 +0100, Michael Heiming
<michael+usenet@heiming.de> wrote:
>Dand Blackman wrote:
>
>
>[..]
>> Loopback seems to be running on 127.0.0.1 and it has worked since the
>
>$ cat /etc/sysconfig/network-scripts/ifcfg-lo
>
>> server was set up. This server has been running since August and just
>> started getting the neighbour table overflow the past two weeks...
>
>You can find this message in the kernel source.
>/usr/src/linux/net/ipv4/route.c
>
> if (net_ratelimit())
> printk(KERN_WARNING "Neighbour table overflow.\n");
> rt_drop(rt);
> return -ENOBUFS;
>
>Looks like, one should enable martian source logging:
>
># for i in /proc/sys/net/ipv4/conf/*/log_martians; do echo 1 > $i;done
>
>Could provide some more logging, you don't have iptables running and
>recently changed your config? There may be other (new) boxes on your
>net, or just new NICs, hard to tell, from here. You have to take a
>look, for sure, running 'tcpdump' might offer more info/help, try 'man
>tcpdump', it has more then a few options.
>
>Good luck
>
>Michael Heiming
Thanks...I'm not runnignIP tables and haven't made any configuration
changes lately. Did check out the loop back and got information about
ARP cache and looked at some of those things but did not make any
changes, but the problem has disappeared since my first posting and as
I have plenty of other things to spend time on I won't fix what isn't
broke at the present time...
David Blackman
|
|
|
|
|