| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: Error message in stderr.txt for GPU work units. |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
BoincSpy
Cruncher Joined: Feb 27, 2007 Post Count: 11 Status: Offline Project Badges: 
|
Hi All,
I am getting the following errors in the stdout.txt for GPU related tasks. Although the status is valid. Here is the log. I have 2 RTX 2070 running Ubuntu 22.04.1 LTS. Note I have CPU workunits that are successful according to the results Tab. Another issue I am having probably not GPU related is that my host is not showing up on the devices tab. Error or not? core_client_version>7.18.1</core_client_version> <![CDATA[ <stderr_txt> ../../projects/www.worldcommunitygrid.org/wcgrid_opng_autodockgpu_7.28_x86_64-pc-linux-gnu__opencl_nvidia_102 -jobs OPNG_0162374_00044.job -input OPNG_0162374_00044.zip -seed 303724008 -wcgruns 850 -wcgdpf 17 INFO: Using gpu device from app init data 1 INFO:[04:23:57] Start AutoGrid... autogrid4: Successful Completion. INFO:[04:24:28] End AutoGrid... INFO:[04:24:29] Start AutoDock for OB3ZINC001284422299--7los_A-001--TYR268_inert.dpf(Job #0)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-6bde96.d INFO:[04:24:39] End AutoDock... INFO:[04:24:39] Start AutoDock for OB3ZINC001368605122--7los_A-001--TYR268_inert.dpf(Job #1)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-4feacc.d INFO:[04:24:50] End AutoDock... INFO:[04:24:50] Start AutoDock for OB3ZINC001268356497_2--7los_A-001--TYR268_inert.dpf(Job #2)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-606198.d INFO:[04:24:59] End AutoDock... INFO:[04:24:59] Start AutoDock for OB3ZINC001133668435--7los_A-001--TYR268_inert.dpf(Job #3)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-b68ac1.d INFO:[04:25:09] End AutoDock... INFO:[04:25:09] Start AutoDock for OB3ZINC001498410436_3--7los_A-001--TYR268_inert.dpf(Job #4)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-3b7887.d INFO:[04:25:18] End AutoDock... INFO:[04:25:18] Start AutoDock for OB3ZINC001107494464_2--7los_A-001--TYR268_inert.dpf(Job #5)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-ce2acb.d INFO:[04:25:30] End AutoDock... INFO:[04:25:30] Start AutoDock for OB3ZINC001100450891--7los_A-001--TYR268_inert.dpf(Job #6)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-00aea6.d INFO:[04:25:39] End AutoDock... INFO:[04:25:39] Start AutoDock for OB3ZINC000523310720_2--7los_A-001--TYR268_inert.dpf(Job #7)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-a16020.d INFO:[04:25:46] End AutoDock... INFO:[04:25:46] Start AutoDock for OB3ZINC001445663656_2--7los_A-001--TYR268_inert.dpf(Job #8)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-9d6173.d INFO:[04:25:53] End AutoDock... INFO:[04:25:53] Start AutoDock for OB3ZINC000174359795--7los_A-001--TYR268_inert.dpf(Job #9)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-2aea36.d INFO:[04:26:00] End AutoDock... INFO:[04:26:01] Start AutoDock for OB3ZINC001414565140_2--7los_A-001--TYR268_inert.dpf(Job #10)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-1f5391.d INFO:[04:26:12] End AutoDock... INFO:[04:26:12] Start AutoDock for OB3ZINC001399196891_2--7los_A-001--TYR268_inert.dpf(Job #11)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-e9287c.d INFO:[04:26:21] End AutoDock... INFO:[04:26:21] Start AutoDock for OB3ZINC001732950676--7los_A-001--TYR268_inert.dpf(Job #12)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-f1d520.d INFO:[04:26:29] End AutoDock... INFO:[04:26:29] Start AutoDock for OB3ZINC001370390367--7los_A-001--TYR268_inert.dpf(Job #13)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-5bdcc5.d INFO:[04:26:40] End AutoDock... INFO:[04:26:40] Start AutoDock for OB3ZINC001440869859--7los_A-001--TYR268_inert.dpf(Job #14)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-fefd82.d INFO:[04:26:50] End AutoDock... INFO:[04:26:50] Start AutoDock for OB3ZINC001497361470--7los_A-001--TYR268_inert.dpf(Job #15)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-3928cb.d INFO:[04:26:58] End AutoDock... INFO:[04:26:58] Start AutoDock for OB3ZINC001379503495--7los_A-001--TYR268_inert.dpf(Job #16)... OpenCL device: NVIDIA GeForce RTX 2070 Could not open file: /tmp/dep-aa5c3c.d INFO:[04:27:06] End AutoDock... INFO:Cpu time = 189.195987 04:27:07 (2046811): called boinc_finish(0) </stderr_txt> ]]> |
||
|
|
geophi
Advanced Cruncher U.S. Joined: Sep 3, 2007 Post Count: 113 Status: Offline Project Badges: 
|
Not sure if the errors opening the files in the tmp folder are a permissions problem? I'm not sure how boinc or the specific WCG applications use the tmp folder and if there is any difference in the way that the GPU application uses it compared to CPU applications. Did it work before, and, if so, have there been any changes to your PC/configuration since it last worked?
As for the host not showing up in your devices tab, this is an issue for some hosts since the project restarted in June. More about that here: https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,44607 |
||
|
|
BoincSpy
Cruncher Joined: Feb 27, 2007 Post Count: 11 Status: Offline Project Badges:
|
This was the first time I have had GPU workunits running on this PC. There should not be a permission problem on /tmp as I can create and read files from that directory from a non privileged account.
|
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges: 
|
Did you download the NVIDIA-software and bake it into your kernel? What's the word on your downloaded NVIDIA-* version, or, what is its version?
One possibility is that the NVIDIA-guys forgot to remove the check for that temporary file in one of those particular NVIDIA-* software versions - and BTW, IMHO, it doesn't do much harm. |
||
|
|
BoincSpy
Cruncher Joined: Feb 27, 2007 Post Count: 11 Status: Offline Project Badges:
|
I had 470.141.03 version installed it was from Ubuntus additional drivers dialog box. I tried update to 515.76 but failed so I installed the NVIDIA software. Will see if it gets rid of the /tmo error..
|
||
|
|
|