message: "Error while computing"

Forums › Problems and Bug Reports

Richard Rankin
Richard Rankin
Joined: 27 Jun 10
Posts: 3
Credit: 12829834
RAC: 0
27 Dec 2010 16:25:26 UTC
Topic 195541
(moderation:
    )

    What does this mean? Everything else is working fine. How do I debug this? I have an ASUS P6X58D motherboard, Intel 980X CPU, 12 GB DDR3-1333 RAM and a Nvidia GeForce GTX 465 video card. Please drop me a note if you have any ideas. Thanks!

    Jord
    Joined: 26 Jan 05
    Posts: 2952
    Credit: 5893653
    RAC: 1

    message: "Error while computing"

    27 Dec 2010 17:22:03 UTC
    Message 101572
    (moderation:
      )

      How to debug? Find the error, which is stored in the stderr.txt sent back to the project. You can find this by clicking on any of the task ID numbers, then checking in the stderr section what it says there.

      I see in your case a load of "Can't write init file: -108" followed by "Can't get shared memory segment name: shmget() failed"; the latter is probably a cause of the first error.

      The BOINC FAQs write for exit code -108:

      Quote:

      ERR_FOPEN -108

      1. BOINC has a problem opening or writing one or more files. One of the ways to get this error is by hiding the BOINC / BOINC Data directory and its sub directories. Then BOINC can't find where it is running from.

      Solution: Do not hide your BOINC / BOINC Data directory.

      2. BOINC finds that the file is open and in use by another process, or BOINC cannot write to the file.

      Solution: Exit BOINC completely and restart it.

      3. It may happen, that when an application hangs while opening/writing to a file and then terminates abnormally (e.g. via Task Manager or even BOINC), this (formerly opened) file may stay locked even if the application is terminated (due to file locks are handled by the OS - e.g. file locks on network shares are handled by the OS for the network PC/Server - the OS needs a definite "remove this lock!" from the calling application to remove it).

      Solution: Restart your computer.

      4. You installed BOINC as an administrator but run it as another user and didn't give that user rights to write to the BOINC or BOINC Data directory and sub-directories. The directories their read-only attributes are set.

      Solution: Either run BOINC as administrator, or give the user you want to run under rights to write to the BOINC /BOINC Data directory and subdirectories.

      Gundolf Jahn
      Gundolf Jahn
      Joined: 1 Mar 05
      Posts: 1079
      Credit: 341280
      RAC: 0

      RE: How do I debug

      27 Dec 2010 17:26:19 UTC
      Message 101573
      (moderation:
        )

        Quote:
        How do I debug this?


        First step: look at the stderr output (to be found in All tasks for computer 2969904 by clicking on the Task ID).

        All S5GCESSE2 tasks I checked, ended with "Can't write init file: -108".
        All BRP3cuda32 tasks I checked, ended with "Can't get shared memory segment name: shmget() failed".

        The latter I've only heard of with Macs, not windows machines.

        Check the file system access rights for the BOINC processes.

        Gruß,
        Gundolf
        [edit]Okay, have mulled over my post for too long again :-)[/edit]

        Computer sind nicht alles im Leben. (Kleiner Scherz)

        Comment viewing options

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

        Forums › Problems and Bug Reports