I am getting a lot of these errors after only one minute of computing on my i7-8700 (running three WUs at a time), but none on my i7-4770 (running only two).

So apparently the Conda server is still being overloaded. Longer work units?

Stderr output

<core_client_version>7.12.0</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
06:34:41 (1134): wrapper (7.7.26016): starting
06:34:41 (1134): wrapper (7.7.26016): starting
06:34:41 (1134): wrapper: running /usr/bin/flock (/var/lib/boinc-client/projects/www.gpugrid.net/miniconda.lock -c "/bin/bash ./miniconda-installer.sh -b -u -p /var/lib/boinc-client/projects/www.gpugrid.net/miniconda &&
                      /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/bin/conda install -m -y -p qmml3 --override-channels -c defaults  -c gpugrid  --file requirements.txt ")
Python 3.6.5 :: Anaconda, Inc.

# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

`$ /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/bin/conda install -m -y -p qmml3 --override-channels -c defaults -c gpugrid --file requirements.txt`

  environment variables:
                 CIO_TEST=<not set>
               CONDA_ROOT=/var/lib/boinc-client/projects/www.gpugrid.net/miniconda
                     PATH=/usr/bin:/bin
       REQUESTS_CA_BUNDLE=<not set>
            SSL_CERT_FILE=<not set>

     active environment : None
       user config file : /var/lib/boinc-client/.condarc
 populated config files : 
          conda version : 4.5.4
    conda-build version : not installed
         python version : 3.6.5.final.0
       base environment : /var/lib/boinc-client/projects/www.gpugrid.net/miniconda  (writable)
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/pro/linux-64
                          https://repo.anaconda.com/pkgs/pro/noarch
                          https://conda.anaconda.org/gpugrid/linux-64
                          https://conda.anaconda.org/gpugrid/noarch
          package cache : /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/pkgs
                          /var/lib/boinc-client/.conda/pkgs
       envs directories : /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/envs
                          /var/lib/boinc-client/.conda/envs
               platform : linux-64
             user-agent : conda/4.5.4 requests/2.18.4 CPython/3.6.5 Linux/4.15.0-36-generic ubuntu/18.04 glibc/2.27
                UID:GID : 122:128
             netrc file : None
           offline mode : False


V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V

CondaHTTPError: HTTP 000 CONNECTION FAILED for url <https://conda.anaconda.org/gpugrid/linux-64/repodata.json>
Elapsed: -

An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.
ConnectionError(MaxRetryError("HTTPSConnectionPool(host='conda.anaconda.org', port=443): Max retries exceeded with url: /gpugrid/linux-64/repodata.json (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fc210f7b630>: Failed to establish a new connection: [Errno -2] Name or service not known',))",),)

A reportable application error has occurred. Conda has prepared the above report.
Upload did not complete.06:35:52 (1134): /usr/bin/flock exited; CPU time 19.235371
06:35:52 (1134): app exit status: 0x1
06:35:52 (1134): called boinc_finish(195)

</stderr_txt>

No issues here, crunching 11 units at a time the last week.

No issues here, crunching 11 units at a time the last week.

Interesting. It may have to do with the communication problems between the U.S. and Spain. But it happened only when the work units on the i7-8700 ran for less than 60 minutes on average, so I think the amount of work has something to do with it. Thanks for the info.