diff options
author | mboelen <michael@cisofy.com> | 2015-07-14 01:31:59 +0300 |
---|---|---|
committer | mboelen <michael@cisofy.com> | 2015-07-14 01:31:59 +0300 |
commit | e8111a124feff0cbacfdc7ae2f62b58a776f0fbe (patch) | |
tree | 3992274ad0307863fbd46c4e89c460144fa5cba2 | |
parent | 7d3053831195a1a700e079ea1373d17a5510866b (diff) |
Increase default minimum amount of connections before alerting
-rw-r--r-- | include/tests_networking | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/include/tests_networking b/include/tests_networking index ac0d3c43..4188c440 100644 --- a/include/tests_networking +++ b/include/tests_networking @@ -447,16 +447,17 @@ # Test : NETW-3028 # Description : Checking for many waiting connections # Type : Performance + # Notes : It is common to see a healthy web server seeing to have several thousands of TCP connections in WAIT state if [ ! "${NETSTATBINARY}" = "" ]; then PREQS_MET="YES"; else PREQS_MET="NO"; fi Register --test-no NETW-3028 --preqs-met ${PREQS_MET} --weight L --network NO --description "Checking connections in WAIT state" if [ ${SKIPTEST} -eq 0 ]; then logtext "Test: Using netstat for check for connections in WAIT state" FIND=`${NETSTATBINARY} -an | grep WAIT | wc -l | awk '{ print $1 }'` - if [ "${OPTIONS_CONN_MAX_WAIT_STATE}" = "" ]; then OPTIONS_CONN_MAX_WAIT_STATE="100"; fi + if [ "${OPTIONS_CONN_MAX_WAIT_STATE}" = "" ]; then OPTIONS_CONN_MAX_WAIT_STATE="5000"; fi logtext "Result: currently ${FIND} connections are in a waiting state (max configured: ${OPTIONS_CONN_MAX_WAIT_STATE})." if [ ${FIND} -gt ${OPTIONS_CONN_MAX_WAIT_STATE} ]; then Display --indent 2 --text "- Checking waiting connections" --result WARNING --color YELLOW - ReportWarning ${TEST_NO} "H" "Found too much connections in WAIT state (${FIND})" + ReportSuggestion "${TEST_NO}" "Determine why system has many connections in WAIT state (${FIND})" else Display --indent 2 --text "- Checking waiting connections" --result OK --color GREEN logtext "Result: ${FIND} connections are in WAIT state" |