| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 315
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
HI Jonathan,
----------------------------------------I said I wasn't very bothered, and it could very well be a graphics driver problem, but I can watch MP4s and DVDs OK, and web site graphics seem to work, but none of the WCG WUs I've tried "Show graphics" on seem to work, certainly not the last two betas or ZIKA or MIP1, though all have files of the form wcgrid_<shortname>_gfx_<version>_x86_64-pc-linux-gnu Don't spend time on this for me. [EDIT Duh, I meant MP4s.] [Edit 1 times, last edit by Former Member at Jun 21, 2019 8:02:51 PM] |
||
|
|
breathesgelatin
Advanced Cruncher Joined: Aug 5, 2006 Post Count: 117 Status: Offline Project Badges:
|
I've got an odd issue that I can't figure out. Not sure if its the beta's fault or BOINC's. I was running one unit for this new Beta: 6/18/2019 10:03:37 AM | World Community Grid | Starting task BETA_ARP1_0000370_004_1 Then 6 hours later I get another one (yay!). But it looks like this paused the first unit, since its stuck at 6 hours of processing time. New unit: 6/18/2019 4:10:22 PM | World Community Grid | Starting task BETA_ARP1_0000526_003_0 I thought there might have been some strange concurrency issue, so I waited. The second one has since finished and the first is still in Waiting to Run. I had some FAAH2 units which have short deadlines, so tried suspending everything else, still Waiting to run. I clicked 'no new work' and waited for everything else to finish. There was then just the beta and 6 HST units (12 core Ryzen system), and it was still Waiting to Run. Finally though "lets turn it off and on", so exited BOINC and started it again. Then it started running. I experienced this same issue. Thanks for the idea, I exited BOINC and restarted and the WU started again. So I guess we're good, as long as I can make the deadline! haha. ![]() |
||
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 206 Status: Offline Project Badges:
|
My ARP WU saga continues (after a fashion!!) - the WU finally hit 100% after just over 41hrs (including several restarts around the 60% mark that added about 12hrs, due to the long periods between check points) but I've now spotted another issue, as this unit is still running - despite hitting 100% and the properties indicating that it's 'completed', the elapsed time is still increasing and the WU (obviously) hasn't uploaded.... Not sure what to do about this??? Anyone got any suggestions? I'd rather not abort it at this point, unless there's no other solution than the nuclear option!!!
----------------------------------------![]() |
||
|
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 786 Status: Offline Project Badges:
|
After work is done the result files are compressed for sending.
----------------------------------------This can take several minutes. Paul.
Paul.
|
||
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 206 Status: Offline Project Badges:
|
UPDATE!!!
----------------------------------------It's finally uploading - all 72MB across 4 files plus other 'hangers on' - I guess the last 20 mins of processing time (beyond the 100% of WU) was compilation of the upload data before actually commencing the file transfer - not seen that take so long previously.... phew - glad to see the back of that WU!!! The WU length does make me question whether I want to take on these units when they finally appear as fully fledged projects, though.... one to ponder.... ![]() |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
UPDATE!!! It's finally uploading - all 72MB across 4 files plus other 'hangers on' - I guess the last 20 mins of processing time (beyond the 100% of WU) was compilation of the upload data before actually commencing the file transfer - not seen that take so long previously.... phew - glad to see the back of that WU!!! The WU length does make me question whether I want to take on these units when they finally appear as fully fledged projects, though.... one to ponder.... Add an app_config file in the project folder and set it to run only 1 at a time until you decide if your machine can handle more.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
----------------------------------------![]() ![]() [Edit 1 times, last edit by nanoprobe at Jun 22, 2019 6:20:36 PM] |
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 2173 Status: Offline Project Badges:
|
The WU length does make me question whether I want to take on these units when they finally appear as fully fledged projects, though.... one to ponder.... Well,...I have one host that runs Climate Prediction (non-WCG) and a single WU can run for weeks. In the past, there used to be a "trickle" upload and reporting, now this hosts gets once a week or so a "blob" of 6500 credits or so. As long as this does this on a consistent bases, that's perfectly fine for me. I am just always worried if something in the "normal" (on WCG) upload-report-validate process shows some unexpected variation. Yes, the ARP1 beta WU's run for almost 2 days, currently for example have 3 of them still crunching along on my i7 Macbook Pro, but as long as there is still slow but steady progress and the 5 possible WUs around those betas are processing fine, I don't really care. The only disappointment was that a good number of previous ARP1 WUs got only 37 credits, for 40h of runtime. Certainly not a good way to promote crunching for WCG, but than at this point, it's only a beta, where something awack is to be expected... Ralf |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
What would cause one of these tasks to error out after 15 hours of runtime? Here's the log.
----------------------------------------Result Log Result Name: BETA_ ARP1_ 0000368_ 003_ 0-- <core_client_version>7.6.9</core_client_version> <![CDATA[ <message> (unknown error) - exit code -1073741819 (0xc0000005) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. Starting WRFMain [16:07:23] INFO: Checkpoint taken at 2018-04-07_06:00:00 [18:54:03] INFO: Checkpoint taken at 2018-04-07_12:00:00 [21:34:50] INFO: Checkpoint taken at 2018-04-07_18:00:00 [23:24:28] INFO: Checkpoint taken at 2018-04-08_00:00:00 [01:14:07] INFO: Checkpoint taken at 2018-04-08_06:00:00 [04:01:47] INFO: Checkpoint taken at 2018-04-08_12:00:00 Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x0000000140AE805A write attempt to address 0x3DC95000 Engaging BOINC Windows Runtime Debugger... ******************** BOINC Windows Runtime Debugger Version 7.15.0 Dump Timestamp : 06/21/19 05:13:19 Install Directory : C:\Program Files\BOINC\ Data Directory : C:\ProgramData\BOINC Project Symstore : LoadLibraryA( C:\ProgramData\BOINC\dbghelp.dll ): GetLastError = 126 Loaded Library : dbghelp.dll LoadLibraryA( C:\ProgramData\BOINC\symsrv.dll ): GetLastError = 126 LoadLibraryA( symsrv.dll ): GetLastError = 126 LoadLibraryA( C:\ProgramData\BOINC\srcsrv.dll ): GetLastError = 126 LoadLibraryA( srcsrv.dll ): GetLastError = 126 LoadLibraryA( C:\ProgramData\BOINC\version.dll ): GetLastError = 126 Loaded Library : version.dll Debugger Engine : 4.0.5.0 Symbol Search Path: C:\ProgramData\BOINC\slots\2;C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org ModLoad: 000000003f790000 0000000006ee3000 C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org\wcgrid_beta27_wrf_7.21_windows_x86_64 (-nosymbols- Symbols Loaded) Linked PDB Filename : C:\Projects\Climate\main_wrf\x64\Release\main_wrf.pdb ModLoad: 0000000077230000 00000000001a9000 C:\Windows\SYSTEM32\ntdll.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : ntdll.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 0000000077010000 000000000011f000 C:\Windows\system32\kernel32.dll (6.1.7601.17932) (-exported- Symbols Loaded) Linked PDB Filename : kernel32.pdb File Version : 6.1.7601.17932 (win7sp1_gdr.120820-0419) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7601.17932 ModLoad: 00000000fd480000 000000000006c000 C:\Windows\system32\KERNELBASE.dll (6.1.7601.17932) (-exported- Symbols Loaded) Linked PDB Filename : kernelbase.pdb File Version : 6.1.7601.17932 (win7sp1_gdr.120820-0419) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7601.17932 ModLoad: 00000000fdf70000 000000000004d000 C:\Windows\system32\WS2_32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : ws2_32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fdbf0000 000000000009f000 C:\Windows\system32\msvcrt.dll (7.0.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : msvcrt.pdb File Version : 7.0.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 7.0.7600.16385 ModLoad: 00000000fe2f0000 000000000012d000 C:\Windows\system32\RPCRT4.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : rpcrt4.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000ff4b0000 0000000000008000 C:\Windows\system32\NSI.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : nsi.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fde10000 00000000000db000 C:\Windows\system32\ADVAPI32.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : advapi32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fd550000 000000000001f000 C:\Windows\SYSTEM32\sechost.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : sechost.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fbfd0000 000000000000c000 C:\Windows\system32\VERSION.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : version.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 0000000077130000 00000000000fa000 C:\Windows\system32\USER32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : user32.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7601.17514 ModLoad: 00000000fe420000 0000000000067000 C:\Windows\system32\GDI32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : gdi32.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7601.17514 ModLoad: 00000000fdbe0000 000000000000e000 C:\Windows\system32\LPK.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : lpk.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fdfc0000 00000000000c9000 C:\Windows\system32\USP10.dll (1.626.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : usp10.pdb File Version : 1.0626.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoft(R) Uniscribe Unicode script processor Product Version : 1.0626.7601.17514 ModLoad: 00000000ff520000 0000000000017000 C:\Windows\system32\imagehlp.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : imagehlp.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7601.17514 ModLoad: 00000000fd920000 000000000002e000 C:\Windows\system32\IMM32.DLL (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : imm32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fdad0000 0000000000109000 C:\Windows\system32\MSCTF.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : msctf.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fb5f0000 000000000002d000 C:\Windows\system32\ntmarta.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : ntmarta.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000ff4c0000 0000000000052000 C:\Windows\system32\WLDAP32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : wldap32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000f8ec0000 0000000000125000 C:\Windows\system32\dbghelp.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : dbghelp.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version : 6.1.7601.17514 *** Dump of the Process Statistics: *** - I/O Operations Counters - Read: 513168, Write: 389259, Other 52828 - I/O Transfers Counters - Read: -1654722271, Write: 826920146, Other 14718722 - Paged Pool Usage - QuotaPagedPoolUsage: 311624, QuotaPeakPagedPoolUsage: 311632 QuotaNonPagedPoolUsage: 15840, QuotaPeakNonPagedPoolUsage: 16080 - Virtual Memory Usage - VirtualSize: 806436864, PeakVirtualSize: 1177817088 - Pagefile Usage - PagefileUsage: 806436864, PeakPagefileUsage: 1060265984 - Working Set Size - WorkingSetSize: 739495936, PeakWorkingSetSize: 1009430528, PageFaultCount: 117680774 *** Dump of thread ID 4760 (state: Initialized): *** - Information - Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000 - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x0000000140AE805A write attempt to address 0x3DC95000 - Registers - rax=000000003d4d0040 rbx=00000000017c1f34 rcx=000000003dc94fc0 rdx=0000000000000000 rsi=0000000000000001 rdi=00000000017c1f34 r8=0000000000ffcf34 r9=0000000000800000 r10=0000000000000000 r11=0000000046646c00 r12=000000001b251220 r13=000000003d4d0040 r14=0000000006f86244 r15=0000000000000035 rip=0000000040ae805a rsp=0000000006f84d18 rbp=00000000017c1f34 cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 - Callstack - ChildEBP RetAddr Args to Child 06f84d10 3f7d2746 017c1f34 00000001 00000000 00000000 wcgrid_beta27_wrf_7!+0x0 06f84f20 3facf476 00000000 00000000 00000000 00000000 wcgrid_beta27_wrf_7!+0x0 06f8ba10 405236ee 00000004 00000000 40000084 00000001 wcgrid_beta27_wrf_7!+0x0 06f8bdd0 40468b77 06f9521c 00000000 00000000 00000001 wcgrid_beta27_wrf_7!+0x0 06f8be10 3f927b72 00000000 00000000 00000000 00000000 wcgrid_beta27_wrf_7!+0x0 06f952f0 3f927a4e 00000000 41dfc71a 06f9e7b8 06f9e788 wcgrid_beta27_wrf_7!+0x0 06f9e7d0 3f868e39 392e3356 00000246 3f86992d 41ee63a8 wcgrid_beta27_wrf_7!+0x0 06f9e800 3f868de5 00000000 06f9e860 00000011 41d83958 wcgrid_beta27_wrf_7!+0x0 06f9e830 3f79676e 41ee6388 4207aff0 00000088 06f9e8b0 wcgrid_beta27_wrf_7!+0x0 06f9fe90 41d5a21c 00000000 00000000 00000000 00000000 wcgrid_beta27_wrf_7!+0x0 06f9fed0 7702652d 00000000 00000000 00000000 00000000 wcgrid_beta27_wrf_7!+0x0 06f9ff00 7725c521 00000000 00000000 00000000 00000000 kernel32!BaseThreadInitThunk+0x0 06f9ff50 00000000 00000000 00000000 00000000 00000000 ntdll!RtlUserThreadStart+0x0 *** Debug Message Dump **** *** Foreground Window Data *** Window Name : Window Class : Window Process ID: 0 Window Thread ID : 0 Exiting... </stderr_txt> ]]> Close Return to Top
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
![]() ![]() |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges:
|
HI Jonathan, I said I wasn't very bothered, and it could very well be a graphics driver problem That could be it. A couple of other things to check if you want. First the graphics applications are dynamically linked so you can run the ldd command against the graphics application to make sure you have all the needed libraries. Second are you able to push the view graphics button but it just closes instantly or is that button greyed out for you? If it is the former all graphics app should write a file "stderrgfx.txt " to the slot directory. There may or may not be some helpful info in there if it is launching and exiting immediately. Thanks, armstrdj |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Jonathan,
Thanks for the ideas, I'm slowly learning more *nix, but don't have the motivation to do much! At the moment I'm running ZIKA and MIP1. The Show graphics button is available for both. The graphics window for the former opens and immediately closes again, with a title in the title bar but no content. The latter doesn't even open. I tried both your suggestions and found nothing apparently missing and no message file (assuming I did it correctly). Please don't waste any more time. This is off-topic as it's nothing specific to the beta. I'll start another thread if I decide to work on it and get stuck. |
||
|
|
|