Forums

Subscribe via email Subscribe via email
Subscribe via rss
Guest
or Ask a Question
Add a reply View Replies (5) →
NetForces
NetForces
Offline

System lockup when Bandwidth managment is enabled

Resolved
0 votes
I have a system where if I enable bandwidth management, the system will lock up. The only way to get it back is to boot in single user mode and set BANDWIDTH_QOS="off" in /etc/clearos/bandwidth.conf

Here are some system details:

ClearOS version: ClearOS Community release 6.5.0 (Final)

Kernel: 2.6.32-431.3.1.v6.x86_64

CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz

Network interfaces:
01:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

Bandwidth related rules:
Merling_Data_Down||0x10001000|0|10.1.0.0/24||eth0:0:1:3:0:0:2048:2048 \
BANDWIDTH_UPSTREAM="eth0:10240"
BANDWIDTH_DOWNSTREAM="eth0:20480"

Any ideas ?
In Bandwidth and QoS
Friday, February 14 2014, 01:42 PM
Subscribe via email
Share this post:
Responses (5)

  • Accepted Answer

    Tim Burgess
    Tim Burgess
    Offline
    Wednesday, March 12 2014, 08:02 AM - #Permalink
    Resolved
    0 votes
    I have the same problem too still with the updated snort version

    You can work around by blacklisting the nfnetlink_queue module in /etc/modprobe.d/blacklist.conf

    To see if the fix works you can run 'modprobe -r nfnetlink_queue' after restarting snort
    The reply is currently minimized Show

  • Accepted Answer

    NetForces
    NetForces
    Offline
    Wednesday, March 12 2014, 12:58 AM - #Permalink
    Resolved
    0 votes
    Ok, on site now. Tried that update of snort (had to install IDS from marketplace first) and still froze.

    In /var/log/messages, the last entries are:

    Mar 11 20:31:52 system kernel: IMQ driver loaded successfully.
    Mar 11 20:31:52 system kernel: Hooking IMQ after NAT on PREROUTING.
    Mar 11 20:31:52 system kernel: Hooking IMQ before NAT on POSTROUTING.
    Mar 11 20:31:52 system kernel: HTB: quantum of class 10001 is big. Consider r2q change.
    Mar 11 20:31:52 system kernel: u32 classifier
    Mar 11 20:31:52 system kernel: Performance counters on
    Mar 11 20:31:52 system kernel: input device check on
    Mar 11 20:31:52 system kernel: Actions configured
    The reply is currently minimized Show

  • Accepted Answer

    Legacy Disabled
    Legacy Disabled
    Offline
    Tuesday, February 25 2014, 04:28 PM - #Permalink
    Resolved
    0 votes
    Hello NetForces,

    It sounds like you are running into the Intrusion Detection (Snort) netfilter issue. Snort will come along and stomp internal data structures used by the Bandwidth and QoS system. Very rude! It's hard to duplicate this problem and we're looking for opportunities to verify that the bug fix resolves the issue. If you want to give the fix a try, run:

    yum --enablerepo=clearos-updates-testing upgrade snort daq


    The fix is simple - it merely disables an unused feature in Snort/Daq. That unused feature is what is causing the data corruption.
    The reply is currently minimized Show

  • Accepted Answer

    NetForces
    NetForces
    Offline
    Tuesday, February 25 2014, 01:46 PM - #Permalink
    Resolved
    0 votes
    Ok, we tried updating kmod-e1000e and kmod-igb, but as soon as I enabled QoS, the system locked-up. It would not reboot to a functional state. Had to boot in single user, disable QoS in /etc/clearos/bandwidth.conf and only then it would boot back normally.

    Any other hints ?
    The reply is currently minimized Show

  • Accepted Answer

    Nick Howitt
    Nick Howitt
    Offline
    Friday, February 14 2014, 03:42 PM - #Permalink
    Resolved
    0 votes
    It might not be your problem but the 82574L has known issues and I believe later drivers are better. I suggest you install the latest kmod-e1000e driver from here. While you're at it you may as well also install the kmod-igb driver for your I350 NIC. It is probably then best to reboot to make them take effect but it can be done from the console without taking the machine down if necessary.
    The reply is currently minimized Show
Your Reply