Seti@Home optimized science apps and information
Optimized Seti@Home apps => Windows => GPU crunching => Topic started by: Maik on 03 Jan 2009, 09:07:14 pm
-
Hi there!
Maybe you know me from Seti Board. Raistmer was suggesting me to join here.
Here i am ! ;) You should know my first language is German, so please be patient with me if my english looks a bit silly ^^
Ok, on work:
Maybe you know i have written a VBscript that watches Cuda-app.exe and fights with its freezing.
vbscript is modified and will copy automaticly wu's which get stuck, tested -> works
now ill try to modify the script that it also will do a copy of WU's that ran to short (compute error) ...
then i'll have my full-auto-watching-wu-and-copy-it-to-stand-alone-dir-vbscript ;))
Wow, very nice !
It seems it's very useful to master VB scripting, will look in this direction, thanks for info :)
After that PM i was thinking i should report here what i have done:
# i created 2 scripts, one for normal use (cuda_log), one for users who do stand alone tests (cuda_log_test)
-> cuda_log activity:
' watching cuda-app.exe
' terminating it when cpu-usage is 0 over 60sec
' logging to file / monitoring at cmd-window all activities
-> cuda_log_test activity:
' same as cuda_log +
' counting task-runtime and monitoring / logging it
' if runtime below defined time -> copy WU to defined folder (to catch compute errors / result overflows)
' if task get freezing -> copy WU to defined folder
' (on my to-do-list -> copy of stderr)
Be carful if you use that 'automated' WU-cleaning (process-terminating). Check your host from time to time.
Some WU's are causing your grafic driver to crash. The result are a lot of failing WU's in a row (noticed that this morning at my host).
The crash announces itself with around jumping pixels everywhere. Some users posted that already ...
If you want to use the script please focus your attention to the settings. Wrong settings will make the script to fail.
I will explain them in my post.
The scripts is running fine at my host (WinXP Pro SP3).
If the script want start, maybe 'scipting host' is deactivated (via xp-AntiSpy or other tools like this)
Edit: delete files-downloads (newer one)
Extract the file where you want and where you have full access (create-file, change-file, e.g. C:\temp).
DONT double-click the *.vbs-file. Windows will use the wrong application tu run the script. Just double-click the *.cmd-file, its the starter-file for the *.vbs-files.
Example from script output:
04.01.2009 01:48:11 > Process-Control for MB_6.06r380mod_CUDA.exe
04.01.2009 01:48:11 > logFile: pc_log_0_04012009.txt
04.01.2009 01:48:11 > maxLogFileSize set to: 51200 bytes
04.01.2009 01:48:11 > boinc dataDir found
04.01.2009 01:48:11 > standAlone folder found ... sub-standAlone activated
04.01.2009 01:48:11 > - running ----------------------------------------
04.01.2009 01:48:11 >
04.01.2009 01:48:14 > --- watching new WU-file: 06no08aa.9787.12342.9.8.106_0
04.01.2009 01:48:29 > ID: 3540 MB_6.06r380mod_CUDA.exe 6 %, running: 15s
...
04.01.2009 01:55:01 > ID: 3540 MB_6.06r380mod_CUDA.exe 12 %, running: 407s
04.01.2009 01:55:16 > --- watching new WU-file: 06no08aa.9787.12342.9.8.125_0
04.01.2009 01:55:31 > ID: 2020 MB_6.06r380mod_CUDA.exe 36 %, running: 15s
...
04.01.2009 02:03:32 > ID: 2020 MB_6.06r380mod_CUDA.exe 12 %, running: 496s
04.01.2009 02:03:47 > ID: 2020 MB_6.06r380mod_CUDA.exe 12 %, running: 511s
04.01.2009 02:04:02 > --- watching new WU-file: 06no08aa.9787.12342.9.8.93_1
04.01.2009 02:04:18 > ID: 2988 MB_6.06r380mod_CUDA.exe 18 %, running: 16s
04.01.2009 02:04:33 > --- watching new WU-file: 06no08aa.9787.12342.9.8.112_0
04.01.2009 02:04:33 >
04.01.2009 02:04:33 > --- debug > RunningTime: 31 --- MinRunTime: 120
04.01.2009 02:04:33 > File: 06no08aa.9787.12342.9.8.93.wu copied ...
04.01.2009 02:04:33 >
04.01.2009 02:04:33 >
04.01.2009 02:04:48 > ID: 1016 MB_6.06r380mod_CUDA.exe 4 %, running: 15s
-
To change settings right-click the *.vbs-file -> context-menue comes up -> choose open with ... -> use notepad.exe
All settings are explained with comments (comments beginning with ')
Settings in cuda_log are easy to understand i think.
For cuda_log_test users, scroll a bit down, there you will find a comment
'settings only for stand alone to copy WU's
To make the script to copy files ssp must be true (ssp = true)
To set your temp-folder is sspp for ...
sspp = "D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\"
Here set the time in seconds that the WU should run to be not a cumpute error / result overflow
(normally WU's are canceled from set-app after 30 sec if result overflow happened)
appMinRunTime = 120
OK, nuff said ... Your turn ;)
-
Sounds like I might be able to try the App again with this, thanks Maik, Will try later today. May take a looksie what is causing these issues If I get a chance.
-
-
I have a request:
If you use the script please notify me about errors (with error messages).
I cant bugfix it if i read posts like 'i have changed that and now it runs' as it happend in seti-forum.
-
Thanks
-
@Maik - can't send PM to you - PM limit reached. I deleted some messages but still the same - maybe it's your PM limit reached not my ?
Check this, please.
-
' (on my to-do-list -> copy of stderr)
I have finished that little project now. Some tests on my host ended sucessfull.
The zip-file contains: *cuda_log_030b.cmd, *cuda_log_030b.vbs, *readme_030b.txt
Please report back on a sucessfull / unsucessfull use of it.
EDIT:
Notice: This script is written for users who want to have a copy of crashed WU's (Stand-Alone-Tester)
For 'normal' users please use cuda_log.zip posted above.
EDIT: deleted file - newer one
-
> Update 040beta
================
> I've re-written the cuda_log_030b.vbs-code.
> It includes now both versions of my basic scripts.
> The script will now be started with options.
> Also i have included tests for file-handling / specified folders.
> Addon: a cuda_log.ini with all settings to handle settings better.
> sart with option -ver and/or -sam or -non
> -ver will show all informatiosn to cmd-window (without the script is only logging to log-file)
> -sam will copy crashed WU's to a specified folder and will try to get a stderr from client_state.xml
> -non will disable both options above
>
> to change start-options edit the cuda_log_040b.cmd - file and change it there
> or run manual start from cmd-window while using the "cscript cuda_log_040b.vbs -option" command
Edit:
I wasnt able to do a complete test with -sam option because i dont have stucking WU's the last 24h ^^
Edit2:
Had a stucking WU now. -sam options seem to wotk without errors.
End at the END: Please report back how the script works for you.
Edit3: Once again. If you use my Script dont leave your PC alone.
If you notice a lot of failing Tasks in a row stop seti and reboot your PC.
-
minor update that fix wrong variables needed with -sam option to detect result overflows.
my fault, sorry for that ^^
It is a bit tricky to handle with variables when VBscript only know the variant-typ....
notice: the script seems to work correctly now. maybe ill rename it to v1.0 if i get no response with errors ;)
External link for download (http://maik0978.homepage.t-online.de/cuda_log.htm)
-
Tried the new version... Here is the log... (Yes that is my Boinc DATA Directory... )
starting script ...
1/10/2009 12:52:09 PM > ============================================
1/10/2009 12:52:09 PM > = WU / Cuda watch script by Maik v0.41beta =
1/10/2009 12:52:09 PM > = maybe not working on Win 95/98/NT =
1/10/2009 12:52:09 PM > ============================================
1/10/2009 12:52:09 PM > = option on: print to cmd-window =
1/10/2009 12:52:09 PM > = option on: copy crashed WU =
1/10/2009 12:52:09 PM > ============================================
1/10/2009 12:52:09 PM >
1/10/2009 12:52:09 PM > ini: appName > MB_r396mod_CUDA.exe
1/10/2009 12:52:09 PM > ini: logFileName > cuda_log
1/10/2009 12:52:09 PM > ini: maxLogFileSize > 50000
1/10/2009 12:52:09 PM > ini: setiPath > C:\Program Files\BOINC\projects
1/10/2009 12:52:09 PM > ini: sspp > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
1/10/2009 12:52:09 PM > ini: appMinRunTime > 120
1/10/2009 12:52:09 PM > ini: showId > 1
1/10/2009 12:52:09 PM > ini: showName > 0
1/10/2009 12:52:09 PM > ini: showUsage > 1
1/10/2009 12:52:09 PM > ini: showRuntime > 1
1/10/2009 12:52:09 PM > Folder valid:
1/10/2009 12:52:09 PM > C:\Program Files\BOINC\projects
1/10/2009 12:52:09 PM > debug:
1/10/2009 12:52:09 PM > invalid Folder!
1/10/2009 12:52:09 PM > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
1/10/2009 12:52:09 PM > no stand alone directory set, process/WU-watching only
1/10/2009 12:52:09 PM > log-file handling successful
1/10/2009 12:52:09 PM > wu-file-handling turned off
end of startup ...
1/10/2009 12:52:09 PM > logFile: cuda_log_0_1102009.txt
1/10/2009 12:52:09 PM > maxLogFileSize set to: 50000 bytes
1/10/2009 12:52:09 PM > --running-----------------
1/10/2009 12:52:12 PM >
1/10/2009 12:52:12 PM > -watching new WU-file:
1/10/2009 12:52:27 PM > ID: 2688 16%, running: 15s
1/10/2009 12:52:43 PM > ID: 2688 14%, running: 31s
Reports invalid folder but it still monitors wu's....
-
it should look like that:
10.01.2009 17:37:00 > ini: appName > MB_r396mod_CUDA.exe
10.01.2009 17:37:00 > ini: logFileName > cuda_log
10.01.2009 17:37:00 > ini: maxLogFileSize > 50000
10.01.2009 17:37:00 > ini: setiPath > D:\boinc_data\projects\setiathome.berkeley.edu\
10.01.2009 17:37:00 > ini: sspp > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
10.01.2009 17:37:00 > ini: appMinRunTime > 120
10.01.2009 17:37:00 > ini: showId > 1
10.01.2009 17:37:00 > ini: showName > 1
10.01.2009 17:37:00 > ini: showUsage > 1
10.01.2009 17:37:00 > ini: showRuntime > 1
10.01.2009 17:37:00 > Folder valid:
10.01.2009 17:37:00 > D:\boinc_data\projects\setiathome.berkeley.edu\
10.01.2009 17:37:00 > Folder valid:
10.01.2009 17:37:00 > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
10.01.2009 17:37:00 > log-file handling successful
10.01.2009 17:37:00 > wu-file-handling successful
end of startup ...
10.01.2009 17:37:00 > logFile: cuda_log_0_10012009.txt
10.01.2009 17:37:00 > maxLogFileSize set to: 50000 bytes
10.01.2009 17:37:00 > --running-----------------
10.01.2009 17:37:03 >
10.01.2009 17:37:03 > -watching new WU-file: 06no08ab.14392.175545.9.8.162_0
10.01.2009 17:37:18 > ID: 344 MB_r396mod_CUDA.exe 4%, running: 15s
10.01.2009 17:37:33 > ID: 344 MB_r396mod_CUDA.exe 6%, running: 30s
The 'valid/invalid' - message tells you that this folder exists.
At your startup the seti folder is missing:
>> 1/10/2009 12:52:09 PM > C:\Program Files\BOINC\projects .... <-----
Also the WU-Name is missing (that tells yout the setiPath is invalid):
>> 1/10/2009 12:52:12 PM > -watching new WU-file: .... <-----
The Script is only monitoring the *.exe-file set in *.ini at your WinTaskManager.
It will notice a change to new wu-file only because the Process-ID will change if a new task is starting.
- Additional: Delete the 'D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\' - entry in the *.ini-file if you dont need copy's of crashed wu's or start without -sam
Edit: I see, its my fault. The *.ini-information is wrong. It should be:
set seti's data directory , e.g. C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\
-
Ah I see I miss read the log... The valid/invalid line is before it says what the folder is...
1/10/2009 12:52:09 PM > Folder valid:
1/10/2009 12:52:09 PM > C:\Program Files\BOINC\projects
1/10/2009 12:52:09 PM > debug:
1/10/2009 12:52:09 PM > invalid Folder!
1/10/2009 12:52:09 PM > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
So it has the folder for the first but not the stand alone.
-
Ah I see I miss read the log... The valid/invalid line is before it says what the folder is...
1/10/2009 12:52:09 PM > Folder valid:
1/10/2009 12:52:09 PM > C:\Program Files\BOINC\projects
It just tells you, that the folder exists on your drive.
If your setup is valid then you will see the WU/Task-name in script output.
I'm working on 042b. I'll add better output-messages ;)
-
v042 , have fun ;)
better startup messages now:
11.01.2009 20:52:22 > testing folder ...
11.01.2009 20:52:22 > D:\boinc_data\projects\setiathome.berkeley.edu\
11.01.2009 20:52:22 > ... folder found
11.01.2009 20:52:22 >
11.01.2009 20:52:22 > testing folder ...
11.01.2009 20:52:22 > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
11.01.2009 20:52:22 > ... folder found
11.01.2009 20:52:22 >
11.01.2009 20:52:22 > log-file handling successful
11.01.2009 20:52:22 > wu-file-handling successful
and a little bonus ;)
11.01.2009 20:53:28 > -watching new task: 16no08aa.10396.13161.10.8.179_2
11.01.2009 20:53:28 > -true angle range: 2.7185053469689
External link for download (http://maik0978.homepage.t-online.de/cuda_log.htm)
-
it gives me type mistmash at ar 0.3 ... (WS2008 eng)
-
Maik,
Have you thought of using boinccmd to automate the VLAR removal problem? (Arises from your remark at SETI).
Look at http://boinc.berkeley.edu/wiki/Boinccmd_tool (first entry under "Control operations" - boinccmd still calls a unit of work a "result", where the rest of BOINC now calls it a "task"). 'Abort' is one of the result-level operations supported.
If you could find a way of doing that too, then we would have a total package for unattended running.
-
it gives me type mistmash at ar 0.3 ... (WS2008 eng)
[/size]
Could you PM me / attach the log please?
Maik,
Have you thought of using boinccmd to automate the VLAR removal problem? (Arises from your remark at SETI).
[/size]
That is surely possible, but I wanted to give one assistance with my Script only, not to intervene in the characteristic functions of the BM.
-
Maik,
Have you thought of using boinccmd to automate the VLAR removal problem? (Arises from your remark at SETI).
[/size]
That is surely possible, but I wanted to give one assistance with my Script only, not to intervene in the characteristic functions of the BM.
I second in that :) If VLARs will be just deleted as files think it would be enough to prevent their devastating effect on current CUDA MB. No intervention with BM is needed, just interaction with filesystem.
ADDON: look here, peoples wanna such ability :)
http://setiathome.berkeley.edu/forum_thread.php?id=51334&nowrap=true#852707
-
it gives me type mistmash at ar 0.3 ... (WS2008 eng)
Could you PM me / attach the log please?
[/size]
Thanks to Devaster! I made a small however not insignificant error.
Working on update ^^
Update done ... still waiting for an replay from my 'beta-tester' ;)
-
Update done ... still waiting for an replay from my 'beta-tester' ;)[/size]
done ...
Thanks again Devaster!
v043 (http://maik0978.homepage.t-online.de/cuda_log.htm)
edit: removed file->new version
-
I just hope that this script won't be misused to cherry pick WUs ... ::)
-
I just hope that this script won't be misused to cherry pick WUs ... ::)
hmm...the script-code is open. you can have a look on it and you will see what it do.
short-version:
- process watching of defined *.exe (from win task manager)
- terminate this process if it 60sec idle/stuck. a 4-time-counter will show that.
- all actions in seti / boinc - directory are read-only
|- the script is using the OpenTextFile - method with argument 1 (read)
|- you can check that at http://msdn.microsoft.com/en-us/library/314cz14s(VS.85).aspx (http://msdn.microsoft.com/en-us/library/314cz14s(VS.85).aspx)
- the script will create *.txt-files
|- this will be opened with argument 8 (write at and of file), to check that use same url like above
- if defined the script will copy crashed wu's to a defined directory to do stand alone tests with taht file.
|- it will create a copy of stderr from client_state in same directory
|- if not needed start the script without -sam
:P
-
I just hope that this script won't be misused to cherry pick WUs ... ::)
hmm...the script-code is open. you can have a look on it and you will see what it do.
:P
I know, but that not what i had in mind ... since this can work with the regular app as well... get my drift ?
-
anyone getting anglerange warnings since last update? ;D
replace cuda_log_043.vbs with attached file
edit: removed file->new version
-
The latest update started running fine (once I got all the settings right :))
but after a few min of running it just stopped... no errors no nothing...
Log is attached...
[attachment deleted by admin]
-
Maybe your mb-seti run out of work ? or closed BM ?
Edit: I've notice you are not setting the temp - folder for crashed wu's. Please edit the *.cmd file and delete the -sam
Just wondering why i write readme-files ...
edit: removed file->new version
-
Maybe your mb-seti run out of work ? or closed BM ?
Edit: I've notice you are not setting the temp - folder for crashed wu's. Please edit the *.cmd file and delete the -sam
Just wondering why i write readme-files ...
Still have work and BM still running...
Sorry I didn't read through the changes... I'm not used to reading through change logs for instructions on what stuff does... (Its not a problem on your side... just me... no need to change it)
-
Still have work and BM still running...
Did you restart script, is it running now ?
-
Yes I restarted it and it is running now...
-
i hate when i update to new version and had a BUGG
C:\Documents and Settings\Administrator.TEST\Desktop\cuda_log_0431\cuda_log_043.
vbs(471, 3) Microsoft VBScript runtime error: Invalid procedure call or argument
: 'Left'
-
What is the setting for your path to seti directory ?
post the *.ini row pls ...
-
[offtopic]
i hate when i update to new version and had a BUGG
Well, it's just reality of life...
Yesterday I installed some software on sister's PC and updated FlashPlayer to 10 version. And after that fullscreen flash video started to freez for every few seconds of play.
So I spend about half hour to find where I can get older flash version - found some "debug build for developers " on Adobe site... Now all work fine as before.
So, even so BIG and FAT corporations as Adobe release CRAP - be patient to independent developers who even not earn any money for their work
[/offtopic]
-
C:\Program Files\boinc\1\projects\setiathome.berkeley.edu
-
I cant find a error atm.
Would pls start the script and make a copy from commandline output and PM me that.
To do a copy right-click into cmd-window, choose mark, mark all, press return -> text is now in buffer
Edit: The error occured in a part of the script which handles the copy of crashed wu's.
If you dont need it just delete the -sam in the *.cmd-file. Otherwise send me the PM.
-
I get this:
1/15/2009 8:49:29 PM > log-file handling successful
1/15/2009 8:49:29 PM > wu-file-handling successful
1/15/2009 8:49:29 PM >
1/15/2009 8:49:29 PM > --running-----------------
1/15/2009 8:49:29 PM > logFile: cuda_log_0_1152009.txt
1/15/2009 8:49:29 PM > maxLogFileSize set to: 50000 bytes
1/15/2009 8:49:32 PM >
1/15/2009 8:49:32 PM > -watching new task: ap_0
C:\cuda_log_043_with_bugfix\cuda_log_043.vbs(578, 2) Microsoft VBScript runtime
error: File not found
Any idea? i thought this file is running. [Solved with a machine restart]
-
did you set the settings ins cuda_log.ini ?
-
Yep all was configured, and working now. It seems if you accidentally close the window the wrong way, with X instead of CTRL-C, the .vbs file can remain locked until reboot, So a restart fixed it and it appears to be working.
-
Yep all was configured, and working now. It seems if you accidentally close the window the wrong way, with X instead of CTRL-C, the .vbs file can remain locked until reboot, So a restart fixed it and it appears to be working.
If that happen open WindowsTaskManger and kill the cscript.exe. Then you dont need to reboot ;)
-
Ah, gotcha.
-
Hello!
Maik, may I ask for script change due to Raistmer's V6 now not aborting but processing VLAR WUs and for that WUs crunching time is much more long. And, that is MUCH more important for script, often V6 app running at 0% (at Windows Task Manager) for up to minute at which time GPU seems very busy (many screen lags) and then app returns to several percents and job completion in BOINC Manager adds about 0.002%. Due to that Task Manager's 0% script restarts such VLAR job many times :(
For example, my first completed VLAR: http://setiathome.berkeley.edu/result.php?resultid=1123579237
After each restart BM's percentage drops near to 2%, and 28 seconds after rises to about 30%, 40%, 50% etc.
Due to difference in comparison my result from CPU-wingman's result I will revert to V5b for now...
-
Hello!
Maik, may I ask for script change due to Raistmer's V6 now not aborting but processing VLAR WUs and for that WUs crunching time is much more long. And, that is MUCH more important for script, often V6 app running at 0% (at Windows Task Manager) for up to minute at which time GPU seems very busy (many screen lags) and then app returns to several percents and job completion in BOINC Manager adds about 0.002%. Due to that Task Manager's 0% script restarts such VLAR job many times :(
I'll try to write a mod.
-
here you go ...
-> check last section in cuda_log.ini
external link (http://maik0978.homepage.t-online.de/cuda_log.htm)
edit: removed file->new version
-
here you go ...
-> check last section in cuda_log.ini
Ok, thanks!
-
I installed Raistmer_s_opt_package_V6 and run script and this came out: I have to abort the WU.
17/01/2009 00:41:42||Starting BOINC client version 6.4.5 for windows_intelx86
17/01/2009 00:41:42||log flags: task, file_xfer, sched_ops
17/01/2009 00:41:42||Libraries: libcurl/7.19.0 OpenSSL/0.9.8i zlib/1.2.3
17/01/2009 00:41:42||Data directory: C:\Documents and Settings\All Users\Application Data\BOINC
17/01/2009 00:41:42||Running under account Zoran
17/01/2009 00:41:42|SETI@home|Found app_info.xml; using anonymous platform
17/01/2009 00:41:42||Processor: 2 AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ [x86 Family 15 Model 67 Stepping 3]
17/01/2009 00:41:42||Processor features: fpu tsc pae nx sse sse2 3dnow mmx
17/01/2009 00:41:42||OS: Microsoft Windows XP: Professional x86 Editon, Service Pack 2, (05.01.2600.00)
17/01/2009 00:41:42||Memory: 2.00 GB physical, 3.85 GB virtual
17/01/2009 00:41:42||Disk: 21.62 GB total, 2.22 GB free
17/01/2009 00:41:42||Local time is UTC +1 hours
17/01/2009 00:41:42||Not using a proxy
17/01/2009 00:41:42||CUDA devices found
17/01/2009 00:41:42||Coprocessor: GeForce 8600 GT (1)
17/01/2009 00:41:42|Project TANPAKU|URL: http://issofty17.is.noda.tus.ac.jp/; Computer ID: 51085; location: home; project prefs: default
17/01/2009 00:41:42|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4234493; location: home; project prefs: home
17/01/2009 00:41:42|PrimeGrid|URL: http://www.primegrid.com/; Computer ID: 89846; location: (none); project prefs: default
17/01/2009 00:41:42|World Community Grid|URL: http://www.worldcommunitygrid.org/; Computer ID: 782092; location: home; project prefs: home
17/01/2009 00:41:42||General prefs: from PrimeGrid (last modified 16-Jan-2009 12:49:35)
17/01/2009 00:41:42||Host location: none
17/01/2009 00:41:42||General prefs: using your defaults
17/01/2009 00:41:42||Reading preferences override file
17/01/2009 00:41:42||Preferences limit memory usage when active to 1023.21MB
17/01/2009 00:41:42||Preferences limit memory usage when idle to 1841.78MB
17/01/2009 00:41:42||Preferences limit disk usage to 0.50GB
17/01/2009 00:41:42||Preferences limit # CPUs to 3
17/01/2009 00:41:42||Suspending computation - initial delay
17/01/2009 00:41:42||Suspending network activity - user request
17/01/2009 00:42:03|SETI@home|Starting 08no08aa.2628.2936.10.8.90_0
17/01/2009 00:42:03|SETI@home|Starting task 08no08aa.2628.2936.10.8.90_0 using setiathome_enhanced version 607
17/01/2009 02:11:42|SETI@home|Task 08no08aa.2628.2936.10.8.90_0 exited with zero status but no 'finished' file
17/01/2009 02:11:42|SETI@home|If this happens repeatedly you may need to reset the project.
17/01/2009 02:11:42|SETI@home|Restarting task 08no08aa.2628.2936.10.8.90_0 using setiathome_enhanced version 607
17/01/2009 02:20:50|SETI@home|Task 08no08aa.2628.2936.10.8.90_0 exited with zero status but no 'finished' file
17/01/2009 02:20:50|SETI@home|If this happens repeatedly you may need to reset the project.
17/01/2009 02:20:51|SETI@home|Restarting task 08no08aa.2628.2936.10.8.90_0 using setiathome_enhanced version 607
17/01/2009 02:24:28|SETI@home|Task 08no08aa.2628.2936.10.8.90_0 exited with zero status but no 'finished' file
17/01/2009 02:24:28|SETI@home|If this happens repeatedly you may need to reset the project.
17/01/2009 02:24:28|SETI@home|Restarting task 08no08aa.2628.2936.10.8.90_0 using setiathome_enhanced version 607
17/01/2009 02:28:50|SETI@home|Task 08no08aa.2628.2936.10.8.90_0 exited with zero status but no 'finished' file
17/01/2009 02:28:50|SETI@home|If this happens repeatedly you may need to reset the project.
17/01/2009 02:28:50|SETI@home|Restarting task 08no08aa.2628.2936.10.8.90_0 using setiathome_enhanced version 607
17/01/2009 02:30:42|SETI@home|Computation for task 08no08aa.2628.2936.10.8.90_0 finished
17/01/2009 02:30:42|SETI@home|Starting 08no08aa.2628.2936.10.8.40_1
17/01/2009 02:30:42|SETI@home|Starting task 08no08aa.2628.2936.10.8.40_1 using setiathome_enhanced version 607
17/01/2009 02:34:38|SETI@home|Computation for task 08no08aa.2628.2936.10.8.40_1 finished
17/01/2009 02:36:20||Resuming network activity
17/01/2009 02:36:20|SETI@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 2 completed tasks
17/01/2009 02:36:25|SETI@home|Scheduler request completed: got 0 new tasks
And CUDA_log
starting script ...
17.01.2009 1:57:45 > ============================================
17.01.2009 1:57:45 > = WU / Cuda watch script by Maik v0.44 =
17.01.2009 1:57:45 > = maybe not working on Win 95/98/NT =
17.01.2009 1:57:45 > = written&tested at WinXPPRo SP3 =
17.01.2009 1:57:45 > = with Windows Script 5.7 =
17.01.2009 1:57:45 > ============================================
17.01.2009 1:57:45 > = option on: print to cmd-window =
17.01.2009 1:57:45 > = option on: copy crashed WU =
17.01.2009 1:57:45 > ============================================
17.01.2009 1:57:45 >
17.01.2009 1:57:45 > ini: appName > MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 1:57:45 > ini: logFileName > cuda_log
17.01.2009 1:57:45 > ini: maxLogFileSize > 50000
17.01.2009 1:57:45 > ini: setiPath > D:\boinc_data\projects\setiathome.berkeley.edu\
17.01.2009 1:57:45 > ini: sspp > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
17.01.2009 1:57:45 > ini: appMinRunTime > 120
17.01.2009 1:57:45 > ini: showId > 1
17.01.2009 1:57:45 > ini: showName > 0
17.01.2009 1:57:45 > ini: showUsage > 1
17.01.2009 1:57:45 > ini: showRuntime > 1
17.01.2009 1:57:45 > ini: showARWarning > 1
17.01.2009 1:57:45 > ini: BreakPerCycle > 12
17.01.2009 1:57:45 >
17.01.2009 1:57:45 > testing folder ...
17.01.2009 1:57:45 > debug:
17.01.2009 1:57:45 > D:\boinc_data\projects\setiathome.berkeley.edu\
17.01.2009 1:57:45 > ... folder not found!
17.01.2009 1:57:45 > no Boinc directory set, process-watching only
17.01.2009 1:57:45 >
17.01.2009 1:57:45 > log-file handling successful
17.01.2009 1:57:45 > wu-file-handling turned off
17.01.2009 1:57:45 >
end of startup ...
17.01.2009 1:57:45 > logFile: cuda_log_0_17012009.txt
17.01.2009 1:57:45 > maxLogFileSize set to: 50000 bytes
17.01.2009 1:57:45 > --running-----------------
17.01.2009 1:57:48 >
17.01.2009 1:58:04 > ID: 3112 0%, running: 16s
17.01.2009 1:58:04 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 1:58:21 > ID: 3112 1%, running: 33s
17.01.2009 1:58:21 > resetting counter
17.01.2009 1:58:38 > ID: 3112 0%, running: 49s
17.01.2009 1:58:38 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 1:58:54 > ID: 3112 0%, running: 66s
17.01.2009 1:58:54 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 1:59:10 > ID: 3112 1%, running: 82s
17.01.2009 1:59:10 > resetting counter
17.01.2009 1:59:25 > ID: 3112 1%, running: 97s
17.01.2009 1:59:41 > ID: 3112 1%, running: 113s
17.01.2009 1:59:56 > ID: 3112 0%, running: 128s
17.01.2009 1:59:57 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:00:13 > ID: 3112 0%, running: 145s
17.01.2009 2:00:13 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:00:28 > ID: 3112 1%, running: 160s
17.01.2009 2:00:28 > resetting counter
17.01.2009 2:00:44 > ID: 3112 0%, running: 176s
17.01.2009 2:00:44 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:01:00 > ID: 3112 1%, running: 192s
17.01.2009 2:01:00 > resetting counter
17.01.2009 2:01:16 > ID: 3112 0%, running: 208s
17.01.2009 2:01:16 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:01:31 > ID: 3112 0%, running: 223s
17.01.2009 2:01:31 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
starting script ...
17.01.2009 2:05:50 > ============================================
17.01.2009 2:05:50 > = WU / Cuda watch script by Maik v0.44 =
17.01.2009 2:05:50 > = maybe not working on Win 95/98/NT =
17.01.2009 2:05:50 > = written&tested at WinXPPRo SP3 =
17.01.2009 2:05:50 > = with Windows Script 5.7 =
17.01.2009 2:05:50 > ============================================
17.01.2009 2:05:50 > = option on: print to cmd-window =
17.01.2009 2:05:50 > = option on: copy crashed WU =
17.01.2009 2:05:50 > ============================================
17.01.2009 2:05:50 >
17.01.2009 2:05:50 > ini: appName > MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 2:05:50 > ini: logFileName > cuda_log
17.01.2009 2:05:50 > ini: maxLogFileSize > 50000
17.01.2009 2:05:50 > ini: setiPath > C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\
17.01.2009 2:05:50 > ini: sspp > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
17.01.2009 2:05:50 > ini: appMinRunTime > 120
17.01.2009 2:05:50 > ini: showId > 1
17.01.2009 2:05:50 > ini: showName > 0
17.01.2009 2:05:50 > ini: showUsage > 1
17.01.2009 2:05:50 > ini: showRuntime > 1
17.01.2009 2:05:50 > ini: showARWarning > 1
17.01.2009 2:05:50 > ini: BreakPerCycle > 12
17.01.2009 2:05:50 >
17.01.2009 2:05:50 > testing folder ...
17.01.2009 2:05:50 > C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\
17.01.2009 2:05:50 > ... folder found
17.01.2009 2:05:50 >
17.01.2009 2:05:50 > testing folder ...
17.01.2009 2:05:50 > debug:
17.01.2009 2:05:50 > D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\
17.01.2009 2:05:50 > ... folder not found!
17.01.2009 2:05:50 > no stand alone directory set, process/WU-watching only
17.01.2009 2:05:50 >
17.01.2009 2:05:50 > log-file handling successful
17.01.2009 2:05:50 > wu-file-handling turned off
17.01.2009 2:05:50 >
end of startup ...
17.01.2009 2:05:50 > logFile: cuda_log_0_17012009.txt
17.01.2009 2:05:50 > maxLogFileSize set to: 50000 bytes
17.01.2009 2:05:50 > --running-----------------
17.01.2009 2:05:54 >
17.01.2009 2:05:54 > -watching new task: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:05:54 > -true angle range: 0.0093754101446022
17.01.2009 2:05:54 >
17.01.2009 2:05:54 > =========================================
17.01.2009 2:05:54 > --Warning: Very Low Angle Range detected!
17.01.2009 2:05:54 > --Warning: Very Low Angle Range detected!
17.01.2009 2:05:54 > =========================================
17.01.2009 2:05:54 >
17.01.2009 2:05:54 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:06:09 > ID: 3112 0%, running: 15s
17.01.2009 2:06:10 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:06:25 > ID: 3112 0%, running: 31s
17.01.2009 2:06:25 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (3. time)
17.01.2009 2:06:41 > ID: 3112 0%, running: 47s
17.01.2009 2:06:41 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (4. time)
17.01.2009 2:06:41 > ...
17.01.2009 2:06:41 > ...process security routine is running
17.01.2009 2:06:41 > ...last process terminating was only 51 sec ago
17.01.2009 2:06:41 > ...this ist the 1. time in a row
17.01.2009 2:06:41 > ...
17.01.2009 2:06:41 > ... - ckeck your driver
17.01.2009 2:06:41 > ... |- maybe do a reboot
17.01.2009 2:06:41 > ... - ckeck the angle range
17.01.2009 2:06:41 > ... |- maybe abort the task
17.01.2009 2:06:41 > ...
17.01.2009 2:06:41 > ... forced script timeout 5 min
17.01.2009 2:11:41 >
17.01.2009 2:11:41 > ! terminating process MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 2:11:41 > ! - crashed WU-file: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:11:41 > --- > RunningTime: 47 --- MinRunTime: 120
17.01.2009 2:11:41 >
17.01.2009 2:11:41 > trying to copy wu
17.01.2009 2:11:41 > File: 08no08aa.2628.2936.10.8.90.wu copied ...
17.01.2009 2:11:41 > --> trying copy of stderr ...
17.01.2009 2:11:41 > --> WU_copy_log.txt found
17.01.2009 2:11:41 > --> client_state.xml found
17.01.2009 2:11:57 >
17.01.2009 2:11:57 > -watching new task: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:11:57 > -true angle range: 0.0093754101446022
17.01.2009 2:11:57 >
17.01.2009 2:11:57 > =========================================
17.01.2009 2:11:57 > --Warning: Very Low Angle Range detected!
17.01.2009 2:11:57 > --Warning: Very Low Angle Range detected!
17.01.2009 2:11:57 > =========================================
17.01.2009 2:11:57 >
17.01.2009 2:12:14 > ID: 6016 0%, running: 17s
17.01.2009 2:12:14 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:12:29 > ID: 6016 0%, running: 32s
17.01.2009 2:12:29 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:12:45 > ID: 6016 0%, running: 48s
17.01.2009 2:12:45 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (3. time)
17.01.2009 2:13:01 > ID: 6016 0%, running: 64s
17.01.2009 2:13:01 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (4. time)
17.01.2009 2:13:01 > ...
17.01.2009 2:13:01 > ...process security routine is running
17.01.2009 2:13:01 > ...last process terminating was only 80 sec ago
17.01.2009 2:13:01 > ...this ist the 2. time in a row
17.01.2009 2:13:01 > ...
17.01.2009 2:13:01 > ... - ckeck your driver
17.01.2009 2:13:01 > ... |- maybe do a reboot
17.01.2009 2:13:01 > ... - ckeck the angle range
17.01.2009 2:13:01 > ... |- maybe abort the task
17.01.2009 2:13:01 > ...
17.01.2009 2:13:01 > ... forced script timeout 30 min
starting script ...
17.01.2009 2:14:12 > ============================================
17.01.2009 2:14:12 > = WU / Cuda watch script by Maik v0.44 =
17.01.2009 2:14:12 > = maybe not working on Win 95/98/NT =
17.01.2009 2:14:12 > = written&tested at WinXPPRo SP3 =
17.01.2009 2:14:12 > = with Windows Script 5.7 =
17.01.2009 2:14:12 > ============================================
17.01.2009 2:14:12 > = option on: print to cmd-window =
17.01.2009 2:14:12 > = option on: copy crashed WU =
17.01.2009 2:14:12 > ============================================
17.01.2009 2:14:12 >
17.01.2009 2:14:12 > ini: appName > MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 2:14:12 > ini: logFileName > cuda_log
17.01.2009 2:14:12 > ini: maxLogFileSize > 50000
17.01.2009 2:14:12 > ini: setiPath > C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\
17.01.2009 2:14:12 > ini: sspp > C:\Documents and Settings\Zoran\Desktop\cuda_log_044\copy\
17.01.2009 2:14:12 > ini: appMinRunTime > 120
17.01.2009 2:14:12 > ini: showId > 1
17.01.2009 2:14:12 > ini: showName > 0
17.01.2009 2:14:12 > ini: showUsage > 1
17.01.2009 2:14:12 > ini: showRuntime > 1
17.01.2009 2:14:12 > ini: showARWarning > 1
17.01.2009 2:14:12 > ini: BreakPerCycle > 12
17.01.2009 2:14:12 >
17.01.2009 2:14:12 > testing folder ...
17.01.2009 2:14:12 > C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\
17.01.2009 2:14:12 > ... folder found
17.01.2009 2:14:12 >
17.01.2009 2:14:12 > testing folder ...
17.01.2009 2:14:12 > C:\Documents and Settings\Zoran\Desktop\cuda_log_044\copy\
17.01.2009 2:14:12 > ... folder found
17.01.2009 2:14:12 >
17.01.2009 2:14:12 > log-file handling successful
17.01.2009 2:14:12 > wu-file-handling successful
17.01.2009 2:14:12 >
end of startup ...
17.01.2009 2:14:12 > logFile: cuda_log_0_17012009.txt
17.01.2009 2:14:12 > maxLogFileSize set to: 50000 bytes
17.01.2009 2:14:12 > --running-----------------
17.01.2009 2:14:16 >
17.01.2009 2:14:16 > -watching new task: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:14:16 > -true angle range: 0.0093754101446022
17.01.2009 2:14:16 >
17.01.2009 2:14:16 > =========================================
17.01.2009 2:14:16 > --Warning: Very Low Angle Range detected!
17.01.2009 2:14:16 > --Warning: Very Low Angle Range detected!
17.01.2009 2:14:16 > =========================================
17.01.2009 2:14:16 >
17.01.2009 2:14:32 > ID: 6016 2%, running: 16s
17.01.2009 2:14:47 > ID: 6016 1%, running: 31s
17.01.2009 2:15:03 > ID: 6016 0%, running: 47s
17.01.2009 2:15:03 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:15:19 > ID: 6016 0%, running: 63s
17.01.2009 2:15:19 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:15:34 > ID: 6016 0%, running: 78s
17.01.2009 2:15:34 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (3. time)
17.01.2009 2:15:49 > ID: 6016 0%, running: 93s
17.01.2009 2:15:49 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (4. time)
17.01.2009 2:15:49 > ...
17.01.2009 2:15:49 > ...process security routine is running
17.01.2009 2:15:49 > ...last process terminating was only 97 sec ago
17.01.2009 2:15:49 > ...this ist the 1. time in a row
17.01.2009 2:15:49 > ...
17.01.2009 2:15:49 > ... - ckeck your driver
17.01.2009 2:15:49 > ... |- maybe do a reboot
17.01.2009 2:15:49 > ... - ckeck the angle range
17.01.2009 2:15:49 > ... |- maybe abort the task
17.01.2009 2:15:49 > ...
17.01.2009 2:15:49 > ... forced script timeout 5 min
17.01.2009 2:20:50 >
17.01.2009 2:20:50 > ! terminating process MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 2:20:50 > ! - crashed WU-file: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:20:50 > --- > RunningTime: 93 --- MinRunTime: 120
17.01.2009 2:20:50 >
17.01.2009 2:20:50 > trying to copy wu
17.01.2009 2:20:50 > File: 08no08aa.2628.2936.10.8.90.wu copied ...
17.01.2009 2:20:50 > --> trying copy of stderr ...
17.01.2009 2:20:50 > --> WU_copy_log.txt found
17.01.2009 2:20:50 > --> client_state.xml found
17.01.2009 2:21:05 >
17.01.2009 2:21:05 > -watching new task: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:21:05 > -true angle range: 0.0093754101446022
17.01.2009 2:21:05 >
17.01.2009 2:21:05 > =========================================
17.01.2009 2:21:05 > --Warning: Very Low Angle Range detected!
17.01.2009 2:21:05 > --Warning: Very Low Angle Range detected!
17.01.2009 2:21:05 > =========================================
17.01.2009 2:21:05 >
17.01.2009 2:21:21 > ID: 1852 1%, running: 16s
17.01.2009 2:21:36 > ID: 1852 1%, running: 31s
17.01.2009 2:21:52 > ID: 1852 1%, running: 47s
17.01.2009 2:22:07 > ID: 1852 1%, running: 62s
17.01.2009 2:22:23 > ID: 1852 1%, running: 78s
17.01.2009 2:22:38 > ID: 1852 1%, running: 93s
17.01.2009 2:22:53 > ID: 1852 1%, running: 108s
17.01.2009 2:23:08 > ID: 1852 1%, running: 123s
17.01.2009 2:23:24 > ID: 1852 2%, running: 139s
17.01.2009 2:23:39 > ID: 1852 0%, running: 154s
17.01.2009 2:23:39 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:23:55 > ID: 1852 0%, running: 170s
17.01.2009 2:23:55 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:24:11 > ID: 1852 0%, running: 186s
17.01.2009 2:24:11 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (3. time)
17.01.2009 2:24:26 > ID: 1852 0%, running: 201s
17.01.2009 2:24:26 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (4. time)
17.01.2009 2:24:27 >
17.01.2009 2:24:27 > ! terminating process MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 2:24:27 > ! - crashed WU-file: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:24:27 > --- > RunningTime: 201 --- MinRunTime: 120
17.01.2009 2:24:27 >
17.01.2009 2:24:27 > trying to copy wu
17.01.2009 2:24:27 > 08no08aa.2628.2936.10.8.90.wu already exists, no copy needed
17.01.2009 2:24:27 > --> trying copy of stderr ...
17.01.2009 2:24:27 > --> WU_copy_log.txt found
17.01.2009 2:24:27 > --> client_state.xml found
17.01.2009 2:24:42 >
17.01.2009 2:24:42 > -watching new task: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:24:42 > -true angle range: 0.0093754101446022
17.01.2009 2:24:42 >
17.01.2009 2:24:42 > =========================================
17.01.2009 2:24:42 > --Warning: Very Low Angle Range detected!
17.01.2009 2:24:42 > --Warning: Very Low Angle Range detected!
17.01.2009 2:24:42 > =========================================
17.01.2009 2:24:42 >
17.01.2009 2:24:58 > ID: 4340 1%, running: 16s
17.01.2009 2:25:13 > ID: 4340 0%, running: 31s
17.01.2009 2:25:13 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:25:29 > ID: 4340 0%, running: 47s
17.01.2009 2:25:29 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:25:44 > ID: 4340 3%, running: 62s
17.01.2009 2:25:44 > resetting counter
17.01.2009 2:26:00 > ID: 4340 1%, running: 78s
17.01.2009 2:26:16 > ID: 4340 1%, running: 94s
17.01.2009 2:26:31 > ID: 4340 1%, running: 109s
17.01.2009 2:26:46 > ID: 4340 1%, running: 124s
17.01.2009 2:27:01 > ID: 4340 0%, running: 139s
17.01.2009 2:27:01 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:27:16 > ID: 4340 1%, running: 154s
17.01.2009 2:27:16 > resetting counter
17.01.2009 2:27:32 > ID: 4340 2%, running: 170s
17.01.2009 2:27:47 > ID: 4340 2%, running: 185s
17.01.2009 2:28:02 > ID: 4340 0%, running: 200s
17.01.2009 2:28:03 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:28:18 > ID: 4340 0%, running: 216s
17.01.2009 2:28:18 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:28:34 > ID: 4340 0%, running: 231s
17.01.2009 2:28:34 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (3. time)
17.01.2009 2:28:50 > ID: 4340 0%, running: 248s
17.01.2009 2:28:50 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (4. time)
17.01.2009 2:28:50 >
17.01.2009 2:28:50 > ! terminating process MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 2:28:50 > ! - crashed WU-file: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:28:50 > --- > RunningTime: 248 --- MinRunTime: 120
17.01.2009 2:28:50 >
17.01.2009 2:28:50 > trying to copy wu
17.01.2009 2:28:50 > 08no08aa.2628.2936.10.8.90.wu already exists, no copy needed
17.01.2009 2:28:50 > --> trying copy of stderr ...
17.01.2009 2:28:50 > --> WU_copy_log.txt found
17.01.2009 2:28:50 > --> client_state.xml found
17.01.2009 2:29:05 >
17.01.2009 2:29:05 > -watching new task: 08no08aa.2628.2936.10.8.90_0
17.01.2009 2:29:05 > -true angle range: 0.0093754101446022
17.01.2009 2:29:05 >
17.01.2009 2:29:05 > =========================================
17.01.2009 2:29:05 > --Warning: Very Low Angle Range detected!
17.01.2009 2:29:05 > --Warning: Very Low Angle Range detected!
17.01.2009 2:29:05 > =========================================
17.01.2009 2:29:05 >
17.01.2009 2:29:20 > ID: 1448 1%, running: 15s
starting script ...
17.01.2009 2:31:26 > ============================================
17.01.2009 2:31:26 > = WU / Cuda watch script by Maik v0.44 =
17.01.2009 2:31:26 > = maybe not working on Win 95/98/NT =
17.01.2009 2:31:26 > = written&tested at WinXPPRo SP3 =
17.01.2009 2:31:26 > = with Windows Script 5.7 =
17.01.2009 2:31:26 > ============================================
17.01.2009 2:31:26 > = option on: print to cmd-window =
17.01.2009 2:31:26 > = option on: copy crashed WU =
17.01.2009 2:31:26 > ============================================
17.01.2009 2:31:26 >
17.01.2009 2:31:26 > ini: appName > MB_6.08a_mod_VLAR_fix_CUDA.exe
17.01.2009 2:31:26 > ini: logFileName > cuda_log
17.01.2009 2:31:26 > ini: maxLogFileSize > 50000
17.01.2009 2:31:26 > ini: setiPath > C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\
17.01.2009 2:31:26 > ini: sspp > C:\Documents and Settings\Zoran\Desktop\cuda_log_044\copy\
17.01.2009 2:31:26 > ini: appMinRunTime > 120
17.01.2009 2:31:26 > ini: showId > 1
17.01.2009 2:31:26 > ini: showName > 0
17.01.2009 2:31:26 > ini: showUsage > 1
17.01.2009 2:31:26 > ini: showRuntime > 1
17.01.2009 2:31:26 > ini: showARWarning > 1
17.01.2009 2:31:26 > ini: BreakPerCycle > 12
17.01.2009 2:31:26 >
17.01.2009 2:31:26 > testing folder ...
17.01.2009 2:31:26 > C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\
17.01.2009 2:31:26 > ... folder found
17.01.2009 2:31:26 >
17.01.2009 2:31:26 > testing folder ...
17.01.2009 2:31:26 > C:\Documents and Settings\Zoran\Desktop\cuda_log_044\copy\
17.01.2009 2:31:26 > ... folder found
17.01.2009 2:31:26 >
17.01.2009 2:31:27 > log-file handling successful
17.01.2009 2:31:27 > wu-file-handling successful
17.01.2009 2:31:27 >
end of startup ...
17.01.2009 2:31:27 > logFile: cuda_log_0_17012009.txt
17.01.2009 2:31:27 > maxLogFileSize set to: 50000 bytes
17.01.2009 2:31:27 > --running-----------------
17.01.2009 2:31:31 >
17.01.2009 2:31:31 > -watching new task: 08no08aa.2628.2936.10.8.40_1
17.01.2009 2:31:31 > -true angle range: 0.0093754101446022
17.01.2009 2:31:31 >
17.01.2009 2:31:31 > =========================================
17.01.2009 2:31:31 > --Warning: Very Low Angle Range detected!
17.01.2009 2:31:31 > --Warning: Very Low Angle Range detected!
17.01.2009 2:31:31 > =========================================
17.01.2009 2:31:31 >
17.01.2009 2:31:31 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:31:47 > ID: 4444 0%, running: 16s
17.01.2009 2:31:47 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 2:32:02 > ID: 4444 0%, running: 31s
17.01.2009 2:32:02 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (3. time)
17.01.2009 2:32:17 > ID: 4444 2%, running: 46s
17.01.2009 2:32:17 > resetting counter
17.01.2009 2:32:32 > ID: 4444 1%, running: 61s
17.01.2009 2:32:49 > ID: 4444 0%, running: 78s
17.01.2009 2:32:49 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:33:05 > ID: 4444 1%, running: 94s
17.01.2009 2:33:05 > resetting counter
17.01.2009 2:33:20 > ID: 4444 1%, running: 109s
17.01.2009 2:33:35 > ID: 4444 0%, running: 124s
17.01.2009 2:33:35 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 2:33:51 > ID: 4444 1%, running: 140s
17.01.2009 2:33:51 > resetting counter
17.01.2009 2:34:08 > ID: 4444 1%, running: 156s
17.01.2009 2:34:23 > ID: 4444 1%, running: 172s
17.01.2009 2:34:38 > ID: 4444 0%, running: 187s
17.01.2009 2:34:38 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
For me is better to go back to Raistmer_s_opt_package_5b and skip WU's with VLAR!
Is this what writes in log a problem or what!??
When CUDA with V6 processing the WU, the computer is very slow,and is hard to work on him. Even the win explorer needs 4-6 seconds to open.
-
The script is telling you what the problem is ... VLAR VLAR VLAR VALR VALR
noticed it now ?
Edit: next dont post the complete log, just attach the txt-file please
try this:
(mod_info)
based on v044 this mod will increase BreakPerCycle with 1sec after 'resetting counter'
to give the task better chances to crunch to 100% without terminating the process.
you will see 'resetting counter' on script-output if it seems that the task is stuck and then running again.
this happen very often while crunching low angle range / very low angle range tasks ...
script does now (copy of script log):
17.01.2009 02:41:42 > ID: 3480 0%, running: 315s
17.01.2009 02:41:42 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 02:42:22 > ID: 3480 1%, running: 355s
17.01.2009 02:42:22 > resetting counter
17.01.2009 02:42:22 > auto increase BreakPerCycle, now: 38 sec
17.01.2009 02:43:03 > ID: 3480 0%, running: 396s
17.01.2009 02:43:03 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 02:43:45 > ID: 3480 1%, running: 438s
17.01.2009 02:43:45 > resetting counter
17.01.2009 02:43:45 > auto increase BreakPerCycle, now: 39 sec
17.01.2009 02:44:27 > ID: 3480 2%, running: 480s
17.01.2009 02:45:09 > ID: 3480 1%, running: 522s
17.01.2009 02:45:51 > ID: 3480 0%, running: 564s
17.01.2009 02:45:51 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (1. time)
17.01.2009 02:46:33 > ID: 3480 0%, running: 606s
17.01.2009 02:46:33 > MB_6.08a_mod_VLAR_fix_CUDA.exe at 0% (2. time)
17.01.2009 02:47:15 > ID: 3480 1%, running: 648s
17.01.2009 02:47:16 > resetting counter
17.01.2009 02:47:16 > auto increase BreakPerCycle, now: 40 sec
17.01.2009 02:47:59 > ID: 3480 4%, running: 692s
17.01.2009 02:48:42 > ID: 3480 5%, running: 735s
17.01.2009 02:49:25 > ID: 3480 1%, running: 778s
external link (http://maik0978.homepage.t-online.de/cuda_log.htm)
edit: removed file->new version
-
Don't need to go to app V5a or b. V6 is very capable to process the WU with high or mid AR.
I don't have yet the VLAR. so testing of the mod will wait.
-
Maik, thanks for new version with mod :)
May I ask You for another new option in Your script very useful for "fire-and-forget" crunching? (As for me, script really helps to stable crunching without paying attention to BOINC very often)
Maybe, for more safe BOINC handling You will add in script and ini-file the 2nd option to "not kill task but suspend/resume project"?
(Because of my OS is Win2003 server which works as file-server, mail-server, proxy-server, wsus-server I don't like killing any tasks...)
Legal stop/start frozen jobs can be made through commands "boinccmd.exe --project setiathome.berkeley.edu suspend" and "boinccmd.exe --project setiathome.berkeley.edu resume"
Of course, that will lead to new parameters in ini-file with names something like "project_name" and "boinc_dir" but You are too more skilled in such things, so it will be Your decision how to implement and do that or not at all ;)
-
One question: What happen if you dont use the script, a task get stuck and you press the 'suspend'-button?
Answere: Right! Nothing. The process is still in your processlist ...
Explanation: If a task goes stuck then there is no more communication between the cpu-process and the gpu-process. That is what my script detects. If you press the 'suspend'-button while there is still no communication between the processes how should the 'suspend'-command arrive the gpu-process? So it will make no sense to write a modification like this.
-
One question: What happen if you dont use the script, a task get stuck and you press the 'suspend'-button?
Answere: Right! Nothing. The process is still in your processlist ...
Explanation: If a task goes stuck then there is no more communication between the cpu-process and the gpu-process. That is what my script detects. If you press the 'suspend'-button while there is still no communication between the processes how should the 'suspend'-command arrive the gpu-process? So it will make no sense to write a modification like this.
But suspend/resume project in BM helps to resume calculation! Before using Your script I had never killing tasks by myself but only pressed suspend/resume buttons in BM!
(I think bug is lies somewhere in CUDA-code filling GPU with work - not task goes stuck and accepts no communication, but loop inside task waits for CUDA-answer from GPU, and suspend/resume button will send commands from BM to task - task {not stucked but looped} receives that message and forcefully breaks loop and restarts itself)
OK, this is my IMHO and I will wait, maybe other crunchers will ask You about the same option later ;)
Please don't abuse/blame me, I only have modestly asked changes, will not - so will not
-
A other User was asking me some posts earlier to add bmcmd commands to the script.
I've rejected this.
After i modded 044 yesterday i noticed that the measure on cpu time is too inaccurate.
I've fixed that and now im monitoring results ... (crunching a VLAR atm).
If this test pass sucessfull I'll offer this new version.
Edit:
- attached a example log from new version to show and explain changes
- initial BreakPerCycle (BPC) is still in use (ini-setting)
- if the script detects a LAR then
. . it adds a amount of 40% to BPC
. . it changes measure-time on cpu process from 3 to 5 sec
. . it adds 2 sec to BPC after every 'resetting counter'
- if the script detects a VLAR then
. . it adds a amount of 80% to BPC
. . it changes measure-time on cpu process from 3 to 7 sec
. . it adds 5 sec to BPC after every 'resetting counter'
The 'heavy looking' cpu-usage on the task before the VLAR has begun is depended on the new measure-procedure.
My Host is a quaddy so the cpu usage is normal the shown / 4.
Atm there is no way to make differences between quad/dual/singel core systems. I think you can live with that :P
Edit2:
need more time to fine tune the timings. script terminated a VLAR although it was running fine ... :'(
[attachment deleted by admin]
-
Ok, im done.
Had a runtime error: overflow , but I wasnt able to reproduce the error to figure out why it happened.
Now the scipt is running about a hour without errors ... -> must be some of Murphy's Law ;D
Please read update infos including in readme.txt before editing the ini and starting the script!
If you have questions to this version I will be online next 2 to 3 hours to answer them here.
external link (http://maik0978.homepage.t-online.de/cuda_log.htm)
-
> Update 046
============
> fixed: error in line 527 (write stderr - function, 'left')
> fixed: DT_a doesnt work
external link (http://maik0978.homepage.t-online.de/cuda_log.htm)
-
> Update 046
Script is working with VLAR much better now (more often it displayed "... at 0% (1. time)" and then "resetting counter", less often "(2. time)").
Running with two 6.03 at main S@H and one 6.08 at S@H Beta simultaneously. Script is monitoring 6.08 (CUDA), of course.
Thanks again, Maik!
-
> Update 048
============
> fixed: error on 'timed stderr run' (used with -sam option)
-> (did no stderr run)
external link (http://maik0978.homepage.t-online.de/cuda_log.htm)
[attachment deleted by admin]
-
Hi,
Do you have an option to monitor the progress of a WU, and then restart boincmgr.exe if there is no progress in a given time?
On Vista x64/Boinc 6.4.5 x64 WUs will be processed normally for some time, and then one WU will stop progressing at between 0,000% and 0,500%. The app is using 100% cpu. When boincmgr is stopped and started, this WU is processed normally. Killing the app will also kill the WU (computation error), which is not appropriate in this case.
I have discussed this with Raistmer and he has pointed to you and your script, but as I pointed out to Raistmer I think this problem is in his V7-code.
Morten Ross
-
I have discussed this with Raistmer and he has pointed to you and your script, but as I pointed out to Raistmer I think this problem is in his V7-code.
Morten Ross
And I pointed out that I need stderr.txt for this task ;) Could you provide it ?
-
Hi,
There are no meaningful entries here - no entries from today's "hung" WUs.
Perhaps debug flags could be set in order to output more info?
Morten
[attachment deleted by admin]
-
Hi,
There are no meaningful entries here - no entries from today's "hung" WUs.
Perhaps debug flags could be set in order to output more info?
Morten
No, I need not BOINC stderr, I need task stderr.txt For task that hangs. It will beposted along with result info on web site after tsk completion. And keeped in slot directory while task in progress. That file I need, not BOINC's.
-
Hi,
That file has no errors at the time of the hang/100% cpu utilization of the app.
When boincmgr is restarted this WU is completed without errors, so there will be no logging of any error. That's why I suggest that the a debug-version of the v7 app is tested.
I have attached the stderr at the time of no WU progression and the same file after boincmgr was restarted.
This is the WU - no errors there...:
http://setiathome.berkeley.edu/result.php?resultid=1129307192
Morten
[attachment deleted by admin]
-
Hi,
Do you have an option to monitor the progress of a WU, and then restart boincmgr.exe if there is no progress in a given time?
...
nope ;)
-
> Update 048
============
> fixed: error on 'timed stderr run' (used with -sam option)
-> (did no stderr run)
external link (http://maik0978.homepage.t-online.de/cuda_log.htm)
Your script does not terminate stalled WUs for me. I am NOT using the -sam option, do I need to for it to terminate stalled WUs?
Attached is a segment of the log showing it doesn't terminate along with the files out of update 048 that I customized for my system.
Let me know what I'm doing wrong.
[attachment deleted by admin]
-
I finished with AP testing, and loaded up the 6.08 cuda app with VLAR Kill mod, and still have been getting frozen tasks, So I've just now enabled the script again.
Since they fixed a lot of things, and the app itself will be terminating the Sluggish VLAR's anyway, one thing that seems to work for me is restarting Boinc. Is it possible to modify the script such that it restarts Boinc on detection of a stuck task,(with perhaps a few seconds in between stopping then starting the service... for us with service install anyway ;) ) rather than terminating the task?
Anyway, seeing how it will go. Pretty good if I can stop having to manually check the machine every few minutes ;).
-
I've had one stick so far that the script seemed to not be able to terminate?
Relevant Log fragment: (Sorry for long post :() [Edit: Not happened again since this one time, a fluke ?]
1/26/2009 1:25:48 PM > -watching new task: 16dc08ad.22822.1708.5.8.113_1
1/26/2009 1:25:48 PM > -true angle range: 0.43389603140378
1/26/2009 1:25:48 PM >
1/26/2009 1:25:48 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (1. time)
1/26/2009 1:26:34 PM > ID: 2260 0%, running: 46s
1/26/2009 1:26:34 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (2. time)
1/26/2009 1:27:19 PM > ID: 2260 0%, running: 91s
1/26/2009 1:27:19 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (3. time)
1/26/2009 1:28:05 PM > ID: 2260 0%, running: 137s
1/26/2009 1:28:05 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (4. time)
1/26/2009 1:28:05 PM >
1/26/2009 1:28:05 PM > ! terminating process MB_6.08_mod_VLAR_kill_CUDA.exe
1/26/2009 1:28:05 PM > ! - crashed WU-file: 16dc08ad.22822.1708.5.8.113_1
1/26/2009 1:28:05 PM > --- > RunningTime: 137 --- MinRunTime: 120
1/26/2009 1:28:05 PM >
1/26/2009 1:28:05 PM > trying to copy wu
1/26/2009 1:28:05 PM > File: 16dc08ad.22822.1708.5.8.113.wu copied ...
1/26/2009 1:28:05 PM > --> trying copy of stderr ...
1/26/2009 1:28:05 PM > --> WU_copy_log.txt found
1/26/2009 1:28:05 PM > --> client_state.xml found
1/26/2009 1:28:50 PM > ID: 2260 0%, running: 182s
1/26/2009 1:28:50 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (1. time)
1/26/2009 1:29:36 PM > ID: 2260 0%, running: 228s
1/26/2009 1:29:36 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (2. time)
1/26/2009 1:30:21 PM > ID: 2260 0%, running: 273s
1/26/2009 1:30:21 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (3. time)
1/26/2009 1:31:07 PM > ID: 2260 0%, running: 319s
1/26/2009 1:31:07 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (4. time)
1/26/2009 1:31:07 PM >
1/26/2009 1:31:07 PM > ! terminating process MB_6.08_mod_VLAR_kill_CUDA.exe
1/26/2009 1:31:07 PM > ! - crashed WU-file: 16dc08ad.22822.1708.5.8.113_1
1/26/2009 1:31:07 PM > --- > RunningTime: 319 --- MinRunTime: 120
1/26/2009 1:31:07 PM >
1/26/2009 1:31:07 PM > trying to copy wu
1/26/2009 1:31:07 PM > 16dc08ad.22822.1708.5.8.113.wu already exists, no copy ne
eded
1/26/2009 1:31:07 PM > --> trying copy of stderr ...
1/26/2009 1:31:07 PM > --> WU_copy_log.txt found
1/26/2009 1:31:07 PM > --> client_state.xml found
1/26/2009 1:31:52 PM > ID: 2260 0%, running: 364s
1/26/2009 1:31:52 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (1. time)
1/26/2009 1:32:38 PM > ID: 2260 0%, running: 410s
1/26/2009 1:32:38 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (2. time)
1/26/2009 1:33:23 PM > ID: 2260 0%, running: 455s
1/26/2009 1:33:23 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (3. time)
1/26/2009 1:34:09 PM > ID: 2260 0%, running: 501s
1/26/2009 1:34:09 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (4. time)
1/26/2009 1:34:09 PM >
1/26/2009 1:34:09 PM > ! terminating process MB_6.08_mod_VLAR_kill_CUDA.exe
1/26/2009 1:34:09 PM > ! - crashed WU-file: 16dc08ad.22822.1708.5.8.113_1
1/26/2009 1:34:09 PM > --- > RunningTime: 501 --- MinRunTime: 120
1/26/2009 1:34:09 PM >
1/26/2009 1:34:09 PM > trying to copy wu
1/26/2009 1:34:09 PM > 16dc08ad.22822.1708.5.8.113.wu already exists, no copy ne
eded
Then I manually aborted the task (actually killed it it task manager), Though a restart of the Boinc service would have allowed it to process, more than likely:
1/26/2009 1:34:09 PM > --> trying copy of stderr ...
1/26/2009 1:34:09 PM > --> WU_copy_log.txt found
1/26/2009 1:34:09 PM > --> client_state.xml found
1/26/2009 1:34:54 PM > ID: 2260 0%, running: 546s
1/26/2009 1:34:54 PM > MB_6.08_mod_VLAR_kill_CUDA.exe at 0% (1. time)
1/26/2009 1:35:40 PM >
1/26/2009 1:35:40 PM > -watching new task: 16dc08ad.22822.1708.5.8.74_1
1/26/2009 1:35:40 PM > -true angle range: 0.43389603140378
1/26/2009 1:35:40 PM >
1/26/2009 1:35:40 PM > resetting counter
1/26/2009 1:35:40 PM > -increasing BreakPerCycle to 43 sec
1/26/2009 1:35:40 PM > -increasing CpuReadTime to 4 sec
1/26/2009 1:36:27 PM > ID: 1864 11%, running: 47s
-
@Jason: I cant reconstruct the error, sorry.
I see the script wasn't termianting the task because of the process-ID did not change.
Its the same error like RandyC reported.
@RandyC: What OS are you using? The 'VB-Script terminate command' does not work on all OS.
And no. You don not need -sam to make the script terminating idleing taks processes.
Maybe booth could attach a full (not snipped) log.txt next time?
I wasn't really thinking that the script is needed such a long time so I did not add any routine to print debug informations with internal variable settings ^^
-
Sure, will attach a full log if it happens again. Have run out of MB work since then, and it never happened again.
-
@Jason: I cant reconstruct the error, sorry.
I see the script wasn't termianting the task because of the process-ID did not change.
Its the same error like RandyC reported.
@RandyC: What OS are you using? The 'VB-Script terminate command' does not work on all OS.
And no. You don not need -sam to make the script terminating idleing taks processes.
Maybe booth could attach a full (not snipped) log.txt next time?
I wasn't really thinking that the script is needed such a long time so I did not add any routine to print debug informations with internal variable settings ^^
I am using XP Pro 32b SP3. I don't know if that's my problem or not. One thing I thought of a while ago: I am using a Service install for BOINC. It may be that with a Service install, the userid running your script is not allowed to terminate BOINC's tasks.
-
I am using XP Pro 32b SP3. I don't know if that's my problem or not. One thing I thought of a while ago: I am using a Service install for BOINC. It may be that with a Service install, the userid running your script is not allowed to terminate BOINC's tasks.
exact same scenario here(XPsp3 & Service), but the script should be running as 'me' right? so in my case has admin privileges AFAIK.
-
I am using XP Pro 32b SP3. I don't know if that's my problem or not. One thing I thought of a while ago: I am using a Service install for BOINC. It may be that with a Service install, the userid running your script is not allowed to terminate BOINC's tasks.
exact same scenario here(XPsp3 & Service), but the script should be running as 'me' right? so in my case has admin privileges AFAIK.
Not sure about that (my id has admin privileges too)...BOINC 6.x.x (running 6.4.5) sets up a special set of IDs to run Service installs. Could try starting the script using 'run-as' option and see if that fixes it. I'd need to set-up a shortcut to start the script.
-
Hehe, process terminat works at XP. Im using that too. but not installed as Service. Maybe thats the reason ...
-
Hehe, process terminat works at XP. Im using that too. but not installed as Service. Maybe thats the reason ...
Can you give me a code segment (and tell me where to insert it) that will perform the following (I don't code VBS) in place of the terminate:
net stop boinc
wait 30 seconds
net start boinc
-
Not atm, sorry.
I have no time atm. Maybe in 3 or 4 days.
-
Not atm, sorry.
I have no time atm. Maybe in 3 or 4 days.
OK. That was going to take too long, so I did some surfing and found a VBS and wscript tutorial and spent about 3 hours on it last night working up some code. It's kind of brute force and could be accomplished better if I knew VBS and wscript more, but I think it will work. See attached for a write-up of what I did.
[attachment deleted by admin]
-
Not atm, sorry.
I have no time atm. Maybe in 3 or 4 days.
OK. That was going to take too long, so I did some surfing and found a VBS and wscript tutorial and spent about 3 hours on it last night working up some code. It's kind of brute force and could be accomplished better if I knew VBS and wscript more, but I think it will work. See attached for a write-up of what I did.
I'm home from work now and I checked that system. It showed 3 stalled WUs and the script restarted BOINC each time. I think we have a winner.
If you can come up with something more efficient, that'd be neat too.
-
Batch restart service mod works well!. Two days now & it only needed to restart once, but it did so and resumed processing on GPU normally.
Jason
-
Is it possible to watch for 2 tasks, not one? (for dual GPU setup)
-
[Edited] - Sorry please ignore the post, somehow manage to get the script running again, must be something wrong at my side.
-
Maik! Where are you? have been using the script for some time with the service restart mods. Works well, Now it needs some small modifcatiion to avoid erroneuosly picking up AStropulse 5.03 WU filenames, which seem to now have a simile filename pattern with .wu in it :( . Is there some small mod so we can ignore ones starting with 'ap_' ?
Jason
-
Maik! Where are you? have been using the script for some time with the service restart mods.
private trouble ...
Works well, Now it needs some small modifcatiion to avoid erroneuosly picking up AStropulse 5.03 WU filenames, which seem to now have a simile filename pattern with .wu in it :( . Is there some small mod so we can ignore ones starting with 'ap_' ?
Yes, that should be possible. I've never had running ap+cuda so never had that problem ... ;)
Is it possible to watch for 2 tasks, not one? (for dual GPU setup)
Should be possible but not with actual code structure. It is based on one filename with one process-ID. At the begining of sh-cuda and the big trouble with it I wasnt thinking that it is needed to write code for dual-card rigs ;)
-
Is it possible to watch for 2 tasks, not one? (for dual GPU setup)
Should be possible but not with actual code structure. It is based on one filename with one process-ID. At the begining of sh-cuda and the big trouble with it I wasnt thinking that it is needed to write code for dual-card rigs ;)
On single GPU host I have no freezes at all but on dual GPU one under Win x64 9400GT tends to hang each few hours :(
So I should manually check that host pretty often...
-
Do they have different filenames on the WTM if they are running?
e.g.
a) setiathome_6.08_windows_intelx86__cuda_1.exe
b) setiathome_6.08_windows_intelx86__cuda_2.exe
-
No, but they would have different working directories ( Slot # at the end of the path) if that's at all accessible. (Not familiar with the WMI interface myself).
-
hi. please forgive my stupidity, but i am interested in this vb-script but have no idea where i can get it. looked in the download-section.
-
Hi there,
This workaround is by Maik, and as such isn't hosted here in downloads. You should find links & attachment on the previous page at http://lunatics.kwsn.net/gpu-crunching/vbscript-fights-cuda.msg13136.html#msg13136 . I recommend (as it seems to work well for me) that if you have Boinc installed as a service (protected application), making the modification that restarts the service instead of killing the tasks. The directions for the modifications are an attachment to a post on this page called 'BounceBM.txt'.
-
Thank you very much for your directions. It's working perfectly.