Having issues with my ClearOS setup - every 24-48 hours or so I have to reboot the server in order for it to pass traffic to the internet again. I've tried removing packages that are not needed/used - so no SAMBA, IPS, Proxy, etc. Basically it's all of the sudden, traffic just drops to nothing. Also the logs are not much help - other than the traffic logs showing me that zero packets are being sent. It's getting pretty annoying to reboot every day or two. I've seen some posts related to issues with Intel NIC's / drivers so not sure if that's the issue. Pretty sure my motherboard is running Intel I211AT chipset. For reference it's a Jetway NF9N motherboard plus the 4 port NIC daughter board. Using the onboard NIC as the WAN interface and one the daughter board NIC's as the inside interface. Any assistance troubleshooting would be helpful. I don't know much about linux commands, so if you want me to post logs, output's, whatever, you'll have to give me the exact command to run.
Using the latest ClearOS 7.1.0
Thanks!
Using the latest ClearOS 7.1.0
Thanks!
In Hardware
Share this post:
Responses (4)
-
Accepted Answer
In the past the 82574L has had a problem driver which later versions appeared to fix. I am not sure at which point they were fixed, but I have later kmod one compiled here. Please can you download it, install it then reboot. Then check if it is being used by doing a "modinfo e1000e". It should give you a version number containing 3.1.0.2.
I'm afraid I can't test the driver myself as I have neither a ClearOS 7 installation not an e1000e card. -
Accepted Answer
Nick -
It's the Intel chipset.
Last login: Thu Feb 11 00:22:20 2016 from zeus.foo.local
[root@gateway ~]# lspci -k | grep Eth -A 3
02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
Subsystem: Intel Corporation Device 0000
Kernel driver in use: igb
04:00.0 PCI bridge: ASMedia Technology Inc. Device 1184
--
06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Device 0000
Kernel driver in use: e1000e
07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Device 0000
Kernel driver in use: e1000e
08:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Device 0000
Kernel driver in use: e1000e
09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Device 0000
Kernel driver in use: e1000e
[root@gateway ~]#
Ben -
When it craters, yes, I can ping the LAN side and get to the web interface. I haven't tried SSH when it happens, so can't say for sure. No, I can't ping anything on the Internet.
Here is the output - it went down around 8:15 or so last night.
Wed Feb 10 18:01:18 2016 info: system - heartbeat...
Wed Feb 10 18:11:19 2016 info: system - heartbeat...
Wed Feb 10 18:21:19 2016 info: system - heartbeat...
Wed Feb 10 18:31:20 2016 info: system - heartbeat...
Wed Feb 10 18:41:20 2016 info: system - heartbeat...
Wed Feb 10 18:51:20 2016 info: system - heartbeat...
Wed Feb 10 19:01:21 2016 info: system - heartbeat...
Wed Feb 10 19:11:21 2016 info: system - heartbeat...
Wed Feb 10 19:21:22 2016 info: system - heartbeat...
Wed Feb 10 19:31:22 2016 info: system - heartbeat...
Wed Feb 10 19:41:22 2016 info: system - heartbeat...
Wed Feb 10 19:51:23 2016 info: system - heartbeat...
Wed Feb 10 19:55:25 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 19:55:28 2016 info: enp2s0 - ping check on server #2 passed - 54.152.208.245
Wed Feb 10 19:56:28 2016 info: enp2s0 - ping check on server #1 passed - 8.8.8.8
Wed Feb 10 20:01:28 2016 info: system - heartbeat...
Wed Feb 10 20:11:29 2016 info: system - heartbeat...
Wed Feb 10 20:13:31 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:13:36 2016 info: enp2s0 - ping check on server #2 failed - 54.152.208.245
Wed Feb 10 20:13:36 2016 warn: enp2s0 - connection warning
Wed Feb 10 20:13:48 2016 info: enp2s0 - ping check on gateway failed - 67.11.224.1
Wed Feb 10 20:13:50 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:13:55 2016 info: enp2s0 - ping check on server #2 failed - 54.152.208.245
Wed Feb 10 20:13:55 2016 warn: enp2s0 - connection warning
Wed Feb 10 20:14:05 2016 info: enp2s0 - ping check on server #1 passed - 8.8.8.8
Wed Feb 10 20:17:00 2016 info: system - syswatch terminated
Wed Feb 10 20:19:37 2016 info: system - syswatch started
Wed Feb 10 20:19:37 2016 info: config - IP referrer tool is installed
Wed Feb 10 20:19:37 2016 info: config - debug level - 0
Wed Feb 10 20:19:37 2016 info: config - retries - 5
Wed Feb 10 20:19:37 2016 info: config - heartbeat - 10
Wed Feb 10 20:19:37 2016 info: config - interval - 60 seconds
Wed Feb 10 20:19:37 2016 info: config - offline interval - 10 seconds
Wed Feb 10 20:19:37 2016 info: config - referrer IP detection - enabled
Wed Feb 10 20:19:37 2016 info: config - ping server auto-detect - enabled
Wed Feb 10 20:19:37 2016 info: config - try pinging gateway - yes
Wed Feb 10 20:19:37 2016 info: config - number of external networks - 1
Wed Feb 10 20:19:37 2016 info: config - monitoring external network - enp2s0
Wed Feb 10 20:19:37 2016 info: info - loading network configuration
Wed Feb 10 20:19:37 2016 info: info - network configuration for enp2s0 - config: ifcfg-enp2s0
Wed Feb 10 20:19:37 2016 info: info - network configuration for enp2s0 - onboot: enabled
Wed Feb 10 20:19:37 2016 info: info - network configuration for enp2s0 - type: dhcp
Wed Feb 10 20:19:37 2016 info: info - network configuration for enp2s0 - wifi: disabled
Wed Feb 10 20:19:37 2016 info: enp2s0 - network - IP address - 67.11.227.125
Wed Feb 10 20:19:37 2016 info: enp2s0 - network - gateway - 67.11.224.1
Wed Feb 10 20:19:37 2016 info: enp2s0 - network - type - public IP range
Wed Feb 10 20:19:38 2016 info: system - changing active WAN list - enp2s0 (was startup)
Wed Feb 10 20:19:38 2016 info: system - current WANs in use - enp2s0
Wed Feb 10 20:19:38 2016 info: system - restarting firewall
Wed Feb 10 20:19:38 2016 info: system - updating intrusion prevention whitelist
Wed Feb 10 20:19:38 2016 info: system - adding ping server 54.152.208.245
Wed Feb 10 20:19:38 2016 info: system - adding ping server 8.8.8.8
Wed Feb 10 20:19:38 2016 info: system - adding DNS server 209.18.47.61
Wed Feb 10 20:19:38 2016 info: system - adding DNS server 209.18.47.62
Wed Feb 10 20:19:38 2016 info: system - reloading intrusion prevention system
Wed Feb 10 20:21:01 2016 warn: system - dynamic DNS update failed - see system log
Wed Feb 10 20:21:01 2016 info: system - DNS update will try again on next heartbeat
Wed Feb 10 20:22:03 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:22:06 2016 info: enp2s0 - ping check on server #2 passed - 54.152.208.245
Wed Feb 10 20:23:06 2016 info: enp2s0 - ping check on server #1 passed - 8.8.8.8
Wed Feb 10 20:24:08 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:24:13 2016 info: enp2s0 - ping check on server #2 failed - 54.152.208.245
Wed Feb 10 20:24:13 2016 warn: enp2s0 - connection warning
Wed Feb 10 20:24:25 2016 info: enp2s0 - ping check on gateway failed - 67.11.224.1
Wed Feb 10 20:24:27 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:24:32 2016 info: enp2s0 - ping check on server #2 failed - 54.152.208.245
Wed Feb 10 20:24:32 2016 warn: enp2s0 - connection warning
Wed Feb 10 20:24:44 2016 info: enp2s0 - ping check on gateway failed - 67.11.224.1
Wed Feb 10 20:24:46 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:24:51 2016 info: enp2s0 - ping check on server #2 failed - 54.152.208.245
Wed Feb 10 20:24:51 2016 warn: enp2s0 - connection warning
Wed Feb 10 20:25:03 2016 info: enp2s0 - ping check on gateway failed - 67.11.224.1
Wed Feb 10 20:25:05 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:25:10 2016 info: enp2s0 - ping check on server #2 failed - 54.152.208.245
Wed Feb 10 20:25:10 2016 warn: enp2s0 - connection warning
Wed Feb 10 20:25:22 2016 info: enp2s0 - ping check on gateway failed - 67.11.224.1
Wed Feb 10 20:25:24 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 20:25:29 2016 info: enp2s0 - ping check on server #2 failed - 54.152.208.245
Wed Feb 10 20:25:29 2016 warn: enp2s0 - connection is down
Wed Feb 10 20:25:31 2016 info: enp2s0 - restarting DHCP connection
Wed Feb 10 20:26:15 2016 info: system - changing active WAN list - none (was enp2s0)
Wed Feb 10 20:26:15 2016 info: system - current WANs in use - none
Wed Feb 10 20:26:15 2016 info: system - restarting firewall
Wed Feb 10 20:26:16 2016 info: system - updating intrusion prevention whitelist
Wed Feb 10 20:26:16 2016 info: system - adding ping server 54.152.208.245
Wed Feb 10 20:26:16 2016 info: system - adding ping server 8.8.8.8
Wed Feb 10 20:26:16 2016 info: system - adding DNS server 209.18.47.61
Wed Feb 10 20:26:16 2016 info: system - adding DNS server 209.18.47.62
Wed Feb 10 20:26:26 2016 info: enp2s0 - ping check on server #1 passed - 8.8.8.8
Wed Feb 10 20:26:26 2016 info: system - changing active WAN list - enp2s0 (was none)
Wed Feb 10 20:26:26 2016 info: system - current WANs in use - enp2s0
Wed Feb 10 20:26:26 2016 info: system - restarting firewall
Wed Feb 10 20:26:27 2016 info: system - updating intrusion prevention whitelist
Wed Feb 10 20:26:27 2016 info: system - adding ping server 54.152.208.245
Wed Feb 10 20:26:27 2016 info: system - adding ping server 8.8.8.8
Wed Feb 10 20:26:27 2016 info: system - adding DNS server 209.18.47.61
Wed Feb 10 20:26:27 2016 info: system - adding DNS server 209.18.47.62
Wed Feb 10 20:26:29 2016 info: system - dynamic DNS updated
Wed Feb 10 20:28:30 2016 info: system - heartbeat...
Wed Feb 10 20:38:30 2016 info: system - heartbeat...
Wed Feb 10 20:48:30 2016 info: system - heartbeat...
Wed Feb 10 20:58:31 2016 info: system - heartbeat...
Wed Feb 10 21:04:33 2016 info: enp2s0 - ping check on server #1 failed - 8.8.8.8
Wed Feb 10 21:04:36 2016 info: enp2s0 - ping check on server #2 passed - 54.152.208.245
Wed Feb 10 21:05:36 2016 info: enp2s0 - ping check on server #1 passed - 8.8.8.8
Wed Feb 10 21:08:36 2016 info: system - heartbeat...
Wed Feb 10 21:18:37 2016 info: system - heartbeat...
I don't see anything specific in the dmesg output, but not sure what I'm looking for either. But nothing that says error or failed.
Thanks. -
Accepted Answer
-
Accepted Answer
You need to narrow things down...
For example, during an 'outage':
1. Can you ping the LAN IP of the server?
2. Can you ssh to the ClearOS server?
3. Can you ping googe.com from the server CLI?
4. Can you ping 8.8.8.8 from the server CLI?
5. What is the status of your network (according to syswatch)..."cat /var/log/syswatch"
6. Anything interesting in dmesg output?
B
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »