Distributed Testing, updated to 1.6 and leaving beta status

Problem with test target

Hi,

I noticed one of my machines running distributed testing was using 100% of the processors of my dual core machine (50% CPU) for over a day. I stopped and restarted the service a few times and the download queue was getting longer and it seemed stuck on one entry:-

Testing now: SDDT-Win32.Hidden.RTK-Yodama.sbi

To check, I installed the client on my other machine, a quad core, with the same effects. It has been also stuck testing this item overnight and is using 25% cpu (100% of 1 processor core)

Could you look into this please? The queued test list is getting quite long and I would hate the alternative of shutting down the service as the excessive cpu use is hindering my normal use of the machines.

Can you email me with your response as I am unwilling to commit so much constant cpu resource to testing one possibly faulty rule test and will be forced to terminate my involvement in the testing program if this problem persists.

Thank you
Tamxir

Ps - I am using the current version 1.6 of the S/W and the OS on my machines is 1. XP Pro SP3 2. Vista Ult SP1
 
Last edited:
Further to my previous post, I have sent my sbsdscan.ini as suggested in an earlier thread post.

Sorry for the multiple post. I get a bit crabby when I wake up for my first coffee and I see both my babies (2 nice PC's) are using up cpu on I what don't know.

:crazy: :laugh:

I've had my coffee now and I'm settled.

tamxir

PS again. Maybe I should go back to bed. Normally I can say what I need to in one post with zero edits :laugh:

I've had no virus checker or firwall issues with any testing (Avast and OutPost Pro). Also, the client runs fine otherwise.
 
Last edited:
This issue sound like the one PepiMK mentioned with the expired license file.
You will need to install the new version of the distributed testing client, the installer can be manually downloaded here
 
anyone know yet......

about the post i made along with other people on the last page?

"I have downloaded and installed the latest update for the testing console, however, even though i have the latest update installed, when i click "about" in the program (which seems to go straight to the updater for some reason) I get the following: There's a new version, 1.6.1, available. Update to 1.6.1 is required to run after November 23rd, 2008. Do you want to download it? And when i click no, (as i have already did the update) it brings me to the about screen and says the following info: spybot s&d distributed testing console 1.6.1.15 Which is the latest version.....yet it keeps telling me a new update is available, and yet i already have it. Just thought i would let you know of this. Uninstall and install again does not help. So ya, little bug ;) "
 
Update re McAfee and PoisonIvy-micha

ispycookies said:
Thanks for the reply.

I have restarted sddt and it ran through everything fine, EXCEPT that McAfee is still finding a "virus" on the same test:
Code: 
(i) 11/3/2008 10:28 AM Testing now: SDDT-PoisonIvy-micha.sbi...
(i) 11/3/2008 10:28 AM Downloading next: SDDT-PoisonIvy-micha.sbi
(i) 11/3/2008 10:28 AM File received.
(i) 11/3/2008 10:28 AM Wrote configuration file.
(!) 11/3/2008 10:28 AM The log file that should have been created (logs\4082.xml) was not found!
(!) 11/3/2008 10:28 AM Damn, could not upload results, will try again later!
(i) 11/3/2008 10:28 AM Failed, need to retest!
Code: 
(Service stopped successfully.)
(Service started successfully.)
(i) 11/3/2008 10:38 AM 
(i) 11/3/2008 10:38 AM Queued tests:
(i) 11/3/2008 10:38 AM SDDT-PoisonIvy-micha.sbi        4082 2008-10-24 14:13:48
(i) 11/3/2008 10:38 AM Testing now: SDDT-PoisonIvy-micha.sbi...
(i) 11/3/2008 10:38 AM Downloading next: SDDT-PoisonIvy-micha.sbi
(i) 11/3/2008 10:38 AM File received.
(i) 11/3/2008 10:38 AM Wrote configuration file.
(!) 11/3/2008 10:38 AM The log file that should have been created (logs\4082.xml) was not found!
(!) 11/3/2008 10:38 AM Damn, could not upload results, will try again later!
(i) 11/3/2008 10:38 AM Failed, need to retest!
And McAfee snatches up and quarantine's the ini for the above test, same as before.

But at least all of the other tests ran successfully. :)

Hopefully a update to McAfee in the near future will fix this; otherwise that test is never going to complete! :sad:
Click to expand...

sddt had been running well and without any McAfee warnings since maybe a week after my last post (which was the beginning of November). However, the recent PoisonIvy-micha test is again triggering McAfee the same as before, only this time when McAfee quarantine's the ini file it causes sddt to crash, but sddt stays at 50% CPU usage until I click on the window that tells Windows whether or not to send an error report. Below is the info from the log:
(i) 12/9/2008 2:20 PM Testing now: SDDT-Win32.PoisonIvy.j-micha.sbi...
(i) 12/9/2008 2:20 PM Downloading next: SDDT-Win32.PoisonIvy.j-micha.sbi
(i) 12/9/2008 2:20 PM File received.
(i) 12/9/2008 2:20 PM Wrote configuration file.
(i) 12/9/2008 2:22 PM Exception EFOpenError in module sbsdscan.exe at 0001FD03.
(i) 12/9/2008 2:22 PM Cannot open file "C:\Program Files\SDistTest\sbsdscan.ini". Access is denied.
(i) 12/9/2008 2:22 PM
(!) 12/9/2008 2:22 PM The log file that should have been created (logs\4452.xml) was not found!
(!) 12/9/2008 2:22 PM Damn, could not upload results, will try again later!
(i) 12/9/2008 2:22 PM Failed, need to retest!
Click to expand...
Unfortunately I do not have the time right now to do any troubleshooting, but I wanted to at least pass on this information which I hope will be helpful. I'll need to disable sddt for the time being. :sad: But I'll try it periodically over the next weeks/months to see if the issue has somehow gotten resolve either on McAfee's end or with sddt.

:)
 
Yodama said:
This issue sound like the one PepiMK mentioned with the expired license file.
You will need to install the new version of the distributed testing client, the installer can be manually downloaded here
Click to expand...

Thanks Yodama. I've been a bit too busy to revisit the issue but I just downloaded the new client as you recommended and all is fixed now and running well. The 2nd machine should be up and testing also soon.

Regards
Tamxir
 
SDDT-Sec-Test.gen-Buster.sbi

I got a problem on this detection it's been running for more than 4 day without result...
Got any advise to start the next one?
 
Help new S&D not working

I uninstalled my older S&D because my computer is a mess with the spyware 2009. Have to get to that nexxt. For now I need to use the new version and I have doanloaded with out auto updates checked as read about in post. I also disabled the firewall while doing so, just in case. On my desk top but I still can't open it. Please help :sad:


Edit -tashi
Malware forum topic:
http://forums.spybot.info/showthread.php?t=42436&page=4
 
Hello, I'm french and I find Sbsd is a very good idea^^

I use it a lot but i'ts not very Practice. It would be nice, to can send sbsd in the task bar in a very next version like folding@home or lot's of software. ! ;)
 
Hi! Started using this on my wifes' computer

(Windows XP Media Center Edition Version 2002 Service Pack 3 on a Compaq Presario AMD Athlon 64 Processor 3800+ 966MHz 1.93GB RAM )

recently and I've noticed that only the "Non-Service" version (1.6.1.14) of it will work - when I try to use the other (1.6.0.0), it just gives me a message that it can't start the service.

Norton 360 is the A/V and firewall on that computer and its' wirelessly connected to my router, if that makes any difference.

Is this normal? Pete
 
If the service is already running and you hit the "Start Service" button you'll get the message "(Could not start service)", maybe there should be something like "Service already running" or something like that. Did you already try turning it off and on again?
 
Sorry for the delay in responding.

No, I didn't try turning it off and on again, but I can.

Actually, now that I did a C/A/D, I'm seeing that it is running (see screenshot), I'm just not seeing a SYSTRAY icon for it (which it may or may not have - is it supposed to?). I could have sworn one was there before.

Anyway, I guess I can close down the "Stand-Alone" one? I just like to see what's going on with it.

Is there any harm in leaving both of them running? Pete
 
It doesn't seem that way here - the "stand alone" shows you when it runs a test (I think - at least that's what it looks like it's doing), gives you all kinds of cheerful messages when it's happy and seems lonely when it doesn't have anything to do.

That's okay - I'm going to run both until someone tells me otherwise.

Thanks all. Pete
 
I should clarify. Running the standalone client is a model that'll show you what the real thing will look like. The Testing Console is the real stuff.
 
@Drragosta: maybe you should re-check your knowledge about the stand-alone client. (I've got like 60 pages of testing @this confirming it's working)
It's an actual working component you know, it just does all the testing when you start the program, it isn't like the service (which starts-up@start-up :laugh: )

@Anyone of the S&D team: does the client fail (often) when certain malware is able to recognize that's it's being spotted?
In this example: Win32.TDSS.pe-Buster; It seems to be on A pc of some 'friends' & they regularly practice bad Internet usage.. :laugh:
Strangely enough Internet was usable up-to some level until Avira's scanner removed some of the malware.. (now they don't have Internet access on that particular pc/computer.)
 
Last edited:
Yeah, good point :sad:. I didn't read enough books about it.

Enlighten me (the differences between the two)? : D
Even though the Stand-alone client has "Non-Service Version" logo on the window title.
 
I don't know what - if anything - changed, but the "Beta testing service Console" is now working correctly on my wifes' computer.

Starts w/Windows, shows in SYSTRAY and accurately logs the tests as they happen without my having to open the stand-alone client to see that. Pete
 
You must log in or register to reply here.
Back
Top