Forums

Leon
Leon
Offline
Resolved
0 votes
Hi All

I have a strange one, server has been running for about a year now and for the past 4 weeks i have had the following issue where my WAN connection just goes down.
I contacted my ISP, and they confirm that the link is up.
Once i do a "Shutdown - Power-up" all is working again.

The only common denominator i can find is than this only happen during Raid re-build???
My re-build was always on Sunday, and on Sunday afternoon around 17:30 my WAN would go down.

I moved it to Monday - /etc/cron.d/raid-check - and now i get it on Monday.
Anyone that can shed some light as i have no idea where to look.
Monday, September 17 2018, 05:17 PM
Share this post:
Responses (9)
  • Accepted Answer

    Leon
    Leon
    Offline
    Monday, October 01 2018, 05:12 PM - #Permalink
    Resolved
    0 votes
    Hi Nick

    I did a check, and it is all working, even during the RAID re-build.

    Here is ifconfig, and as you can see, no errors on the LAN.
    # ifconfig
    enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 164.160.117.13 netmask 255.255.255.0 broadcast 164.160.117.255
    inet6 fe80::215:17ff:fef5:5771 prefixlen 64 scopeid 0x20<link>
    ether 00:15:17:f5:57:71 txqueuelen 1000 (Ethernet)
    RX packets 74474337 bytes 82638133167 (76.9 GiB)
    RX errors 0 dropped 1 overruns 0 frame 0
    TX packets 41924422 bytes 25104426035 (23.3 GiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xb1c00000-b1c20000

    enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.2.1 netmask 255.255.255.0 broadcast 192.168.2.255
    inet6 fe80::215:17ff:fef5:5770 prefixlen 64 scopeid 0x20<link>
    ether 00:15:17:f5:57:70 txqueuelen 1000 (Ethernet)
    RX packets 41344264 bytes 34793688661 (32.4 GiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 79039357 bytes 110368518897 (102.7 GiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xb1a00000-b1a20000

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1000 (Local Loopback)
    RX packets 1100883 bytes 451286454 (430.3 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1100883 bytes 451286454 (430.3 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    One thing i have seen, is that my LAN traffic had gone down, no tests, but just looking at my main switch, it seems to have a lot less traffic, if i look at the activity lights on the ports.
    I still don't know what the issue was, but deleting the NIC's and re-creating them seems to have solved my LAN issue.
    I still seem to have some issue as i see the WAN port NIC resetting - "e1000e 0000:00:19.0 enp0s25: Reset adapter unexpectedly"
    The reply is currently minimized Show
  • Accepted Answer

    Leon
    Leon
    Offline
    Saturday, September 29 2018, 08:29 AM - #Permalink
    Resolved
    0 votes
    Hi Nick

    Did not have any joy last night, so started fresh this morning.
    Had one issue with Samba not binding to my LAN, but i got that working.

    And now... Confusion - no dropped packets, the only thing that changed, is that i deleted the NIC's and created them again???
    As the RAID sync will run on Monday, i shall check again during the re-build and let you know

    [root@ZodiacTech ~]# ifconfig
    enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 164.160.117.13 netmask 255.255.255.0 broadcast 164.160.117.255
    inet6 fe80::215:17ff:fef5:5771 prefixlen 64 scopeid 0x20<link>
    ether 00:15:17:f5:57:71 txqueuelen 1000 (Ethernet)
    RX packets 3471333 bytes 3822962566 (3.5 GiB)
    RX errors 0 dropped 1 overruns 0 frame 0
    TX packets 2323257 bytes 692975463 (660.8 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xb1c00000-b1c20000

    enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.2.1 netmask 255.255.255.0 broadcast 192.168.2.255
    inet6 fe80::215:17ff:fef5:5770 prefixlen 64 scopeid 0x20<link>
    ether 00:15:17:f5:57:70 txqueuelen 1000 (Ethernet)
    RX packets 12123515 bytes 11054494493 (10.2 GiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 19648934 bytes 28737993325 (26.7 GiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xb1a00000-b1a20000

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1000 (Local Loopback)
    RX packets 33353 bytes 34555515 (32.9 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 33353 bytes 34555515 (32.9 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    The reply is currently minimized Show
  • Accepted Answer

    Friday, September 28 2018, 08:40 PM - #Permalink
    Resolved
    0 votes
    I think you can just delete the NIC's in the IP Settings screen or console then re-configure them.
    The reply is currently minimized Show
  • Accepted Answer

    Leon
    Leon
    Offline
    Friday, September 28 2018, 07:47 PM - #Permalink
    Resolved
    0 votes
    Hi Nick

    It seems that my tinkering has "Broken" my system, i am now unable to connect via LAN.
    How do i "Reset" my network settings to "Default"?

    It is two On-Board LAN ports on a Intel Server Board S3420GP
    The reply is currently minimized Show
  • Accepted Answer

    Friday, September 28 2018, 05:41 PM - #Permalink
    Resolved
    0 votes
    That looks horrible. Do you have a faulty NIC or cable?
    The reply is currently minimized Show
  • Accepted Answer

    Leon
    Leon
    Offline
    Friday, September 28 2018, 04:53 PM - #Permalink
    Resolved
    0 votes
    Hi Nick

    1st i disables all IPV6 traffic - How do i disable IPv6 on CentOS 7 / RHEL 7
    I used "Method 1"
    There was a decrease in the IPV6 traffic.

    I have done - ethtool -K enp2s0 tso off gso off - enp2S0 is my LAN interface, but using "?sbin/ifconfig" i still see a high amount of RX dropped packets.

    # /sbin/ifconfig
    enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 164.160.117.13 netmask 255.255.255.0 broadcast 164.160.117.255
    ether 00:15:17:f5:57:71 txqueuelen 1000 (Ethernet)
    RX packets 103280603 bytes 93656896628 (87.2 GiB)
    RX errors 0 dropped 8686 overruns 0 frame 0
    TX packets 73582983 bytes 33164990293 (30.8 GiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xb1c00000-b1c20000

    enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.2.1 netmask 255.255.255.0 broadcast 192.168.2.255
    ether 00:15:17:f5:57:70 txqueuelen 1000 (Ethernet)
    RX packets 92624763 bytes 47121247080 (43.8 GiB)
    RX errors 0 dropped 29238641 overruns 0 frame 0
    TX packets 74970205 bytes 92967305578 (86.5 GiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xb1a00000-b1a20000

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    loop txqueuelen 1000 (Local Loopback)
    RX packets 1784149 bytes 961081358 (916.5 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1784149 bytes 961081358 (916.5 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    The reply is currently minimized Show
  • Accepted Answer

    Monday, September 24 2018, 03:22 PM - #Permalink
    Resolved
    0 votes
    Can you have a look at this thread and try turning off "tso"? I am not sure if the setting will survive a reboot of if it needs to be set every time you boot.
    The reply is currently minimized Show
  • Accepted Answer

    Leon
    Leon
    Offline
    Monday, September 24 2018, 02:52 PM - #Permalink
    Resolved
    0 votes
    Hi Nick

    The RAID is part of ClearOS
    i have 10x 2TB drives setup as Raid6
    1 separate drive for the ClearOS
    1 separate drive for file transfers from Internet

    No the LAN traffic is low, it is a 1Gb LAN, and when it "freeze" the tragic i have seen is between 10 to 15Mb on the LAN.
    Here is the output
    lspci -k | grep Eth -A 3
    00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 05)
    Subsystem: Intel Corporation Device 34ec
    Kernel driver in use: e1000e
    Kernel modules: e1000e
    --
    02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    Subsystem: Intel Corporation Device 34ec
    Kernel driver in use: e1000e
    Kernel modules: e1000e

    The only error i see, and it is repeated a few times is:
    e1000e: enp0s25 NIC Link is Down
    [16957.265929] e1000e 0000:00:19.0: irq 33 for MSI/MSI-X
    [16957.366178] e1000e 0000:00:19.0: irq 33 for MSI/MSI-X
    [16957.366347] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready

    I don't have any IPv6 settings on my network... as far as i know and "enp0s25" is my WAN port to the internet.

    I have also seen this at the end of the report.

    e1000e 0000:00:19.0 enp0s25: Reset adapter unexpectedly
    [173637.874987] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx
    [173648.234370] e1000e 0000:00:19.0 enp0s25: Reset adapter unexpectedly
    [173649.891026] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx
    The reply is currently minimized Show
  • Accepted Answer

    Monday, September 17 2018, 07:13 PM - #Permalink
    Resolved
    0 votes
    Have a look in your log files at that time. Is the RAID in ClearOS or separate (i.e. is there much LAN traffic)?

    What is the output from:
    lspci -k | grep Eth -A 3


    If you get a chance, before you reboot, can you type the command "dmesg" and look for errors, probably near the bottom.
    The reply is currently minimized Show
Your Reply