Errors on eth1

[RandomUsername]

Since getting my B3, munin and phpsysinfo have been reporting errors on my eth1 interface. eth1 is directly connected to my desktop PC which doesn't get much use these days. I've not seen any symptoms of this while using the PC, everything appears fine and the number of errors is not huge - phpsysinfo reports 31 errors during 17 days of uptime.

Just wondering if anyone else has seen anything similar. I can't see anything relevant in my logs but not really sure what I should be looking for.

Cheers.

Darren.

[Cheeseboy]

Hi Darren,

As you can see for yourself on Ubi's Munin page, I do not get the same behaviour, even though I sometimes have quite high loads of network traffic.
Makes me suspect either HW problems, or more likely a problem on the other end (your PC)?

I suspect you have more measurements in place for the B3 than the PC, and thus this is where you will notice anything, even though it doesn't even manifest itself as a real problem...

Eeeh, actually looking at all those stats, it looks like I have the most memory and CPU utilization. And most of the other un-understandable bits too. Perhaps that is why I have the shortest uptimes too?

[RandomUsername]

Hey Mr Cheese. Don't know why I didn't think of looking at other people's munin stats. D'oh!

The thing is, nothing has changed since I switched the B2 for a B3 except the server - same cable, same desktop etc. I will try to set up some more logging on the PC I 'spose.

Thanks.

[Cheeseboy]

Well, it does seem to have a lot of errors reported in that graph. I have no idea on what to look for in the logs.
Perhaps it is HW related, and you should ask the competent guys in Excito about it?

[pcrene]

Hello all,

I reported it earlier and they told me i should check the cable.
Since the update 10 dayes ago i have no errors but 31 dropped packages.

Rene

[RandomUsername]

Well I've been trying to track this down and these are the results so far.

When I first booted up my PC, errors in ifconfig were reported as 0 on the PC and 31 received dropped packets on B3.

I copied a 2GB file from the PC to B3 over samba and the error count increased by 4 on both machines.

PC:

Code: Select all

eth0      Link encap:Ethernet  HWaddr 00:11:d8:c6:16:7c  
          inet addr:192.168.10.98  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::211:d8ff:fec6:167c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1075448 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2162387 errors:0 dropped:0 overruns:4 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:188870039 (188.8 MB)  TX bytes:3078366463 (3.0 GB)
          Interrupt:17 Base address:0x9800 

B3:

Code: Select all

eth1      Link encap:Ethernet  HWaddr 00:22:02:00:20:57  
          inet6 addr: fe80::222:2ff:fe00:2057/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:18106479 errors:35 dropped:35 overruns:0 frame:0
          TX packets:18715584 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3552215915 (3.3 GiB)  TX bytes:1622196906 (1.5 GiB)
          Interrupt:15 

So at least the number of errors tally.

On the PC,

Code: Select all

cat /proc/net/dev

gives this:

Code: Select all

Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    4560      64    0    0    0     0          0         0     4560      64    0    0    0     0       0          0
  eth0: 197394367 1081629    0    0    0     0          0         0 3078643167 2165878    0    0    4     0       0          0
vboxnet0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0

(I'm anticipating that won't format well. It basically shows 4 fifo errors).

Both NICs are operating at full-duplex 100Mbps.

After this initial increase, I've been unable to reproduce. I copied the same file over ftp and over samba a second time and the errors haven't incremented. I'm not sure what this means, but as the B3 has experienced 35 dropped packets out of 18106479 I can't bring myself to worry too much about it.

Still, I'd be interested in hearing anyone's opinion.

Darren.

[Cheeseboy]

I'm sorry, I have no idea.
I'd just like to say one thing:
NFS.

[RandomUsername]

I'd just like to say one thing:
NFS.

PPPPffffffsssssssss.

[Cheeseboy]

PPPPffffffsssssssss.

Well, that is just my opinion, and perhaps not very helpful.
But you know what to do, you don't have to ask here really. Email the Excito crew; Do a pcap trace and find out what is happening; Buy a new swtich; etc.