I suspect that graphics card with more than 2 GB internal RAM is a requirement (?)

I think it's more likely to be the /bin/bash which actually needs to write temporary files. I've now managed (with some difficulty) to separate the 569 lines of actual script from the 90 MB of payload. There's

export TMP_BACKUP="$TMP"
export TMP=$PREFIX/install_tmp

but no sign of the TMPDIR mentioned in https://linux.die.net/man/1/bash. More than that is above my pay-grade, I'm afraid.

You can run the script in your home directory if you want to know more about it. (Like the End User License Agreement, the Notice of Third Party Software Licenses, and the Export; Cryptography Notice!)

wrapper starts the script successfully,
miniconda folder is installed silently in /www.gpugrid.net/ directory,
conda install starts the setup of the environment, unpacks files then initiates processes to compile the task.

The environment setup is the step I am thinking causes the error.



Directories and Files of Interest:

/miniconda/etc/profile.d/ directory,
/miniconda/lib/python3.7/<_sysconfigdata_> files

These files and directories seem to contain Gpugrid environment information, which might be of interest. (probably more which I haven't found yet)


I am sure the team at Gpugrid are already 10 steps ahead of us and all issues well in hand!

 (Python) estimated total NVIDIA GPU task duration: 1631149 seconds
(TONI) estimated total NVIDIA GPU task duration: 731036 seconds

Returning to graphics card RAM size and Python tasks:
My Host #567828 and Host #557889, both running acemd3 tasks fine on their 2GB RAM graphics cards, haven't been able to process none of the Python tasks that they have received.
I gave up, and set their GPUGrid preferences for them not to ask for Python tasks any more.
This way, they won't be delaying these tasks uselessly.

I happened to receive my first beta task today on a 750Ti (2GB VRAM). It started okay and the task progress bar advanced normally just to fail after ~800 sec. What I have seen so far on other hosts was that either the task seemed to fail immediately within seconds or it finished successfully, so it's strange that it did compute for quite some time. Saw that some of you reported >2GB VRAM used for the task so that could be an issue here as well, but I can't find in the stderr file what might have caused this error. Task 26520658

What is strange for my host is that normally for the ACEMD tasks that CPU time = runtime, but here CPU time was well below it.

Traceback (most recent call last):
File "run.py", line 50, in <module>
assert os.path.exists('output.coor')
AssertionError
15:13:02 (13979): ./gpugridpy/bin/python exited; CPU time 31.339888

I just read through this whole thread, and I am still not clear what changes I need to make to fix the permissions error. FWIW, I have the regular BOINC installation, not a service installation.

Which file do I need to edit? What changed do I make to that file?

TIA!

I executed the stated command:
sudo systemctl edit boinc-client.service

And I added to the file the suggested lines:
[Service]
PrivateTmp=true

I just read through this whole thread, and I am still not clear what changes I need to make to fix the permissions error. FWIW, I have the regular BOINC installation, not a service installation.

Which file do I need to edit? What changed do I make to that file?

TIA!

Apply this modification:

Extracted from post by ServicEnginIC
(https://www.gpugrid.net/forum_thread.php?id=5204&nowrap=true#55988

I executed the stated command:
sudo systemctl edit boinc-client.service

And I added to the file the suggested lines:
[Service]
PrivateTmp=true

A reboot is recommended after applying this change. (Or at the least, restart the boinc-client service)

Interesting to learn that all linux installations do it as a service install. I thought that caused a problem with GPU crunching?

Interesting to learn that all linux installations do it as a service install. I thought that caused a problem with GPU crunching?

Yes, your statement is right. The "GPUs are not available to services" is a specific, Windows only, driver security matter. Mac and Linux have different ways of handling it.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
"boincmgr"="\"D:\\BOINC\\boincmgr.exe\" /a /s"

[HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager]
"DisableAutoStart"=dword:00000000