[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

pumpd filling message log



I'm running RH 6.2 on an old 486SX/25 with 3 NICs as a gateway for my home
network.  For the most part everything is working much better than I had
hoped for.  However, I noticed a problem with drive space on the system
rather rapidly disappearing.  Investigation lead me to the
"/var/log/message" file and it's numbered counterparts.  These files had
been filling very rapidly with entries similar to the following snip:

Sep 11 04:01:56 heimdall kernel: Packet log: input REJECT eth0 PROTO=17
192.168.0.1:1015 255.255.255.255:1015 L=176 S=0x00 I=4506 F=0x0000 T=128
(#18) 
Sep 11 04:01:56 heimdall kernel: Packet log: input REJECT eth0 PROTO=17
192.168.0.1:1015 255.255.255.255:1015 L=176 S=0x00 I=4762 F=0x0000 T=128
(#18) 
Sep 11 04:02:00 heimdall kernel: Packet log: input REJECT eth0 PROTO=17
192.168.0.1:1015 255.255.255.255:1015 L=176 S=0x00 I=8602 F=0x0000 T=128
(#18) 
Sep 11 04:02:00 heimdall kernel: Packet log: input REJECT eth0 PROTO=17
192.168.0.1:1015 255.255.255.255:1015 L=176 S=0x00 I=8858 F=0x0000 T=128
(#18)

I've traced this down to "pumpd" but have not been able to assess why it's
really happening.  I have two external NICs on the system however only eth0
seems to be getting these requests.  If I shut eth0 down the other NICs
continue working with no problem and no further entries of this nature in
the message log.  Additionally, according to these entries this is an input
request, but the source IP is that of eth1 on the system.  Wouldn't a
request from the system itself be an output?  Is there something I've missed
in configuration?  

Jamin W. Collins





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]