TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
I did, on 8/9, and was told that the process will fork additional processes
and that it was due to heavy traffic. I than confirmed with our network
people that traffic on that segment is always less than 10% capacity (100
Mbps). It does not appear that traffic was the issue. I do not use the
MU3.1 signature for CR, I will use the User Defined.
Kurt
"Lau, Jamie
(ISS To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
Atlanta)" cc:
<[EMAIL PROTECTED] Subject: RE:
HTTP_IIS_Index_Server_Overflow signature in MU 3.1 or
> User de fined?
08/15/2001
02:53 PM
I am the product manager for X-Press Updates and am not aware of this
issue.
Can you report this to [EMAIL PROTECTED] so it can be investigated?
Jamie Lau
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 12:10 PM
To: [EMAIL PROTECTED]
Subject: HTTP_IIS_Index_Server_Overflow signature in MU 3.1 or User
defined?
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------
Has anyone noticed that after the Code Red signature (included in MU 3.1)
is enabled on a Network Sensor 5.0 with SR1.1, the sensor will fork
additional processes and consume 100% CPU? This does not occur when I use
the pre-MU 3.1, User Defined signature for Code Red. I have tested this
over the last several days to confirm that it is a repeatable problem. I
have a Perl script that runs hourly to sync the Sensor logs to the Console
DB and have found an undesirable side effect. When the Engine Manager
attempts to do the sync, it will time-out and fail.
This is top with the User Defined signature enabled and the
HTTP_IIS_Index_Server_Overflow is disabled:
last pid: 29410; load averages: 0.04, 0.05, 0.05
10:41:46
32 processes: 30 sleeping, 1 running, 1 on cpu
CPU states: 94.8% idle, 3.8% user, 0.8% kernel, 0.6% iowait, 0.0% swap
Memory: 64M real, 9136K free, 31M swap in use, 2017M swap free
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
21672 root 14 58 0 100M 12M sleep 19:08 0.92% network_engine
This is top with the User Defined signature disabled and the
HTTP_IIS_Index_Server_Overflow is enabled:
last pid: 29516; load averages: 0.70, 0.25, 0.13
10:48:41
33 processes: 30 sleeping, 2 running, 1 on cpu
CPU states: 0.0% idle, 98.6% user, 1.4% kernel, 0.0% iowait, 0.0% swap
Memory: 64M real, 952K free, 31M swap in use, 2017M swap free
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
29510 root 1 0 0 102M 8224K run 1:02 92.81% network_engine
21672 root 14 58 0 102M 16M sleep 19:16 1.54% network_engine
I can enable both signatures to confirm that they are equally effective at
detecting CR (I and II) probes.
Kurt C Anderson
Deluxe Financial Services