SDDT Scan hangs (reproducably scince yesterday)
Scince yesterday, "SDistTestSvc.ex" regularily hangs with 99% CPU usage after a few scans.
The GUI console shows:
(i) 25.10.2008 02:27 Queued tests:
(i) 25.10.2008 02:27 SDDT-Virtumonde.Dll-Yodama.sbi 4074 2008-10-24 11:33:32
(i) 25.10.2008 02:27 SDDT-new-micha.sbi 4089 2008-10-24 14:13:49
(i) 25.10.2008 02:27 SDDT-Virtumonde.sdn-Yodama.sbi 4075 2008-10-24 11:33:35
(i) 25.10.2008 02:27 SDDT-Smitfraud-C.gp_RG-rene.sbi 4094 2008-10-24 17:29:57
(i) 25.10.2008 02:27 SDDT-Win32.Agent.aec-micha.sbi 4078 2008-10-24 14:13:47
(i) 25.10.2008 02:27 SDDT-Netbus-micha.sbi 4079 2008-10-24 14:13:48
(i) 25.10.2008 02:27 SDDT-Win32.VB.bco-micha.sbi 4080 2008-10-24 14:13:48
(i) 25.10.2008 02:27 SDDT-Win32.Agent.wf-micha.sbi 4081 2008-10-24 14:13:48
(i) 25.10.2008 02:27 SDDT-PoisonIvy-micha.sbi 4082 2008-10-24 14:13:48
(i) 25.10.2008 02:27 SDDT-Joke.Password-micha.sbi 4083 2008-10-24 14:13:48
(i) 25.10.2008 02:27 SDDT-Win32.Autoit.p-micha.sbi 4084 2008-10-24 14:13:48
(i) 25.10.2008 02:27 SDDT-Win32.SdBot.aad-micha.sbi 4085 2008-10-24 14:13:49
(i) 25.10.2008 02:27 SDDT-Win32.VB.dn-micha.sbi 4086 2008-10-24 14:13:49
(i) 25.10.2008 02:27 SDDT-Win32.mIRC.603-micha.sbi 4087 2008-10-24 14:13:49
(i) 25.10.2008 02:27 SDDT-MSNFlood-micha.sbi 4088 2008-10-24 14:13:49
...then...
loading and testing the sbi's - all with "success"
...until SDDT-Virtumonde.sdn-Yodama.sbi (>> which has been tested at last, although it seems to be the first one to be tested according to the list above?!).
There's no "success" after testing SDDT-Virtumonde.sdn-Yodama.sbi
but
- playing a "ping"-sound (like if there would be a dialog box, however, there isn't one!)
- almost freezing CPU by 99% usage by the "SDistTestSvc.ex" process (OK, it's a Pentium III M at 1.1 GHz, however, it's been working fine so fare with all other SaferNW products inclunding SDDT.)
- no chance to stop the process, neither in GUI window ("stop service") nor in the win2K task manager ("stop process") - access denied; however, machine can be shot down w/o probs.
Here are some more details about the context:
SDistTestSvc.ex:
- 21 GDI objects
- 115 handles
- 8 threads
- 5.952 KB memory
- 6.320 KB max. memory
- 5.672 KB virtual memory
- CPU time: 99% usage starts after a few seconds of CPU time
System:
- Win2K SP4 with IE6 on a HP omnibook 6100 with PIIIM at 1.1GHz
- round about 35 other processes running (standard windows stuff, HP/Intel/ATI/Touchpad/deskjet-drivers, AtomiX TimeSync, RoboForm, SD TeaTimer - that's it.)
- NO other task bar applications running
Well, 'm sorry, but seem's to be a bug?? :sad:
_________
btw.: Plz, keep your comments about w2k/IE6 :P , as I MUST use it for my job!
p.s.: Messengers show'n in my profile are all disabled currently. However, feel free to drop me a line or call/chat me by GoogleTalk: logonautics@googlemail.com.
McAfee keeps catching a "virus" in the ini file
For about the past week McAfee keeps thinking that there is a virus in connection with the Distributed Testing Client.
Here is what McAfee reports each time:
McAfee has automatically blocked and removed a Virus.
About this Virus
Detected: Univ.script/99a (Virus)
Location: C:\Program Files\SDTest\sbsdscan.ini
And here is what appears to be culprit in the Testing Client:
(i) 10/28/2008 10:31 AM Queued tests:
(i) 10/28/2008 10:31 AM SDDT-PoisonIvy-micha.sbi 4082 2008-10-24 14:13:48
(i) 10/28/2008 10:31 AM Testing now: SDDT-PoisonIvy-micha.sbi...
(i) 10/28/2008 10:31 AM Downloading next: SDDT-PoisonIvy-micha.sbi
(i) 10/28/2008 10:31 AM File received.
(i) 10/28/2008 10:31 AM Wrote configuration file.
(!) 10/28/2008 10:31 AM The log file that should have been created (logs\4082.xml) was not found!
(!) 10/28/2008 10:31 AM Damn, could not upload results, will try again later!
(i) 10/28/2008 10:31 AM Failed, need to retest!
That same test shows up over and over again, always having failed (very likely because McAfee is snatching up part of it each time).
Since it seems that it is not able to upload results, I would guess that you all would never find out about this unless someone posted (like I am doing; I don't know if anyone else posted as I only checked this thread as this seemed to be the place to post such a thing).
I hope the above is helpful. Let me know if you all need more info.
Also, I do hope that it can be fixed at some point so that McAfee doesn't keep killing that test.
:)
SDDT-Virtumonde.sdnc-Yodama test never finishes
In a similar vien to Logonaut's posts a little earlier in this thread I am observing that the SDDT-Virtumonde.sdnc-Yodama test has run for about 12 hours now, consistently consuming about 50% of my dual-core processor. Surely the test should have finished by now?! :scratch:
Like Logonaut I am observing this with the SDistTestSvc.exe. As far as I know I am using the most current version.
This is the last entry (before I stop the service in a minute):
(i) 10/28/2008 7:14 PM
(i) 10/28/2008 7:14 PM Queued tests:
(i) 10/28/2008 7:14 PM SDDT-Virtumonde.sdn-Yodama.sbi 4130 2008-10-28 15:48:33
(i) 10/28/2008 7:14 PM SDDT-Smitfraud-C.-Yodama.sbi 4131 2008-10-28 15:48:33
(i) 10/28/2008 7:14 PM SDDT-Virtumonde.sci-Yodama.sbi 4129 2008-10-28 15:48:33
(i) 10/28/2008 7:14 PM SDDT-AdDestination-Yodama.sbi 4128 2008-10-28 15:48:33
(i) 10/28/2008 7:14 PM SDDT-PoisonIvy-micha.sbi 4082 2008-10-24 14:13:48
(i) 10/28/2008 7:14 PM SDDT-Virtumonde.scic-Yodama.sbi 4125 2008-10-28 15:48:31
(i) 10/28/2008 7:14 PM SDDT-Virtumonde.dllc-Yodama.sbi 4126 2008-10-28 15:48:31
(i) 10/28/2008 7:14 PM SDDT-Virtumonde.sdnc-Yodama.sbi 4127 2008-10-28 15:48:33
(i) 10/28/2008 7:14 PM Testing now: SDDT-Virtumonde.sdnc-Yodama.sbi...
(i) 10/28/2008 7:14 PM Downloading next: SDDT-Virtumonde.sdnc-Yodama.sbi
(i) 10/28/2008 7:14 PM File received.
(i) 10/28/2008 7:14 PM Wrote configuration file.
It is currently almost 8:00 am the next morning.
Thought you all would want to know.
Let me know what additional info you need from me.
:)