CUDA crunching broken with BOINC alpha 6.13.3?

Forums › Cruncher's Corner

Ver Greeneyes
Ver Greeneyes
Joined: 26 Mar 09
Posts: 140
Credit: 9562235
RAC: 0
10 Sep 2011 12:44:02 UTC
Topic 195958
(moderation:
    )

    Just a bit of a heads-up for anyone interested in trying the pre-release versions of BOINC - I tried 6.13.3 yesterday and all my CUDA WUs started erroring out (running on a GeForce 580 GTX with Windows 7 x64). Maybe the way BOINC handles them has changed in a way that's not compatible with Einstein@Home yet, but for now I'd stay away from them.

    Has anyone else here given them a try?

    Stranger7777
    Stranger7777
    Joined: 17 Mar 05
    Posts: 436
    Credit: 418812127
    RAC: 37457

    CUDA crunching broken with BOINC alpha 6.13.3?

    10 Sep 2011 13:12:25 UTC
    Message 106632
    (moderation:
      )

      My BOINC client on BOINC 6.13 seems don't like CUDA tasks. I can not get any CUDA tasks here, whilst other my hosts are working OK and server gets them sufficient CUDA tasks.

      Krunchin-Keith [USA]
      Krunchin-Keith [USA]
      Joined: 19 Aug 05
      Posts: 8
      Credit: 5096691
      RAC: 0

      A solution for this problem

      11 Sep 2011 18:18:27 UTC
      Message 106633
      (moderation:
        )

        A solution for this problem has been found:

        David Anderson wrote:
        There are (at least) two issues with 6.13.3:

        1) For GPU apps, it passes an additional command-line argument that causes some apps to fail (usually by exiting immediately). This will be fixed in 6.13.4.

        2) 6.13.3 handles file upload certificates (a mechanism that prevents DoS attacks on upload servers) differently than previous versions.
        This change was necessary to make scheduler requests and replies readable by standard XML parsers. But it means that file uploads will fail to projects that a) use upload certificates, and b) aren't running current server code.

        I sent email to boinc_projects describing this change, and recommending that projects disable upload certificates until they're able to upgrade their server code. Not all project admins read boinc_projects, so it may be necessary to contact them via their message boards or email, and I urge Alpha-testers to do so.

        -- David



        David Anderson, boinc_projects email list wrote:

        "Upload certificates" are a mechanism that keeps bad guys from DoS'ing your upload servers (note: such an attack has never happened, as far as I know).

        We're changing the format of upload certificates, and we're starting to test a version of the client for which old-format certificates won't work. Volunteers testers won't be able to upload completed jobs, and they may complain to you.

        I suggest that all projects disable upload certificates. To do so, add the following to your config.xml file:



        To resume using upload certificates, if you wish:

        1) upgrade to the current server source code (from trunk)
        2) wait for all jobs with old-format certificates to be dispatched
        3) re-enable certificates by removing the above lines.

        Let me know if any questions.

        -- David

        BOINCin since 10-Apr-2004 (2.28) ~~~ Join team USA

        Stranger7777
        Stranger7777
        Joined: 17 Mar 05
        Posts: 436
        Credit: 418812127
        RAC: 37457

        Yes. This is the case. I was

        17 Sep 2011 12:55:45 UTC
        Message 106634 in response to message 106633
        (moderation:
          )

          Yes. This is the case. I was wrong thinking that it is only for uploading tasks. Indeed this is for downloading CUDA tasks too. Rigtht after downgrade to 6.12.34 my host has got a lot of CUDA work. Thank you for pointing me out to the valuable information.

          Comment viewing options

          Select your preferred way to display the comments and click "Save settings" to activate your changes.

          Forums › Cruncher's Corner