"Incorrect function (0x1)"?


Advanced search

Message boards : Number crunching : "Incorrect function (0x1)"?

Sort
Author Message
Profile suguruhirahara
Forum moderator
Volunteer tester
Avatar

Joined: Sep 13 06
Posts: 282
ID: 15
Credit: 56,614
RAC: 0
Message 910 - Posted 7 Oct 2006 12:36:55 UTC
Last modified: 7 Oct 2006 12:39:48 UTC

When a host of main recovered from hanging up and ran the BOINC client, I found an error occured to this result.

http://docking.utep.edu/result.php?resultid=26805

<core_client_version>5.4.11</core_client_version>
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Starting charmm run...
Starting charmm run...
Starting charmm run...
Starting charmm run...
ERROR - Charmm exited with code 1.
Calling BOINC finish.

</stderr_txt>

This error happens when BOINC client isn't closed before shutting down or restarting, too. It's an unique error and I've never seen other science applications have experienced this kind of error so far.
____________

I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.
grummel
Volunteer tester

Joined: Oct 2 06
Posts: 6
ID: 127
Credit: 4,957
RAC: 0
Message 912 - Posted 7 Oct 2006 13:33:07 UTC

On my system no problem with this. It works fine!
He has sometimes an "TIMEOUT BY TEMPERATUR" and i restart the system.
( AMD 2800+, Kubuntu 606 )
____________

Memo
Forum moderator
Project developer
Project tester

Joined: Sep 13 06
Posts: 88
ID: 14
Credit: 1,666,392
RAC: 0
Message 913 - Posted 7 Oct 2006 16:33:57 UTC - in response to Message ID 910 .

When a host of main recovered from hanging up and ran the BOINC client, I found an error occured to this result.

http://docking.utep.edu/result.php?resultid=26805
<core_client_version>5.4.11</core_client_version>
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Starting charmm run...
Starting charmm run...
Starting charmm run...
Starting charmm run...
ERROR - Charmm exited with code 1.
Calling BOINC finish.

</stderr_txt>

This error happens when BOINC client isn't closed before shutting down or restarting, too. It's an unique error and I've never seen other science applications have experienced this kind of error so far.



There is a temporary fix. Its in the news archive. It was a problem related to Linux... now in windows boxes it is the first time that I see it. We will investigate further. Here is the fix copied from the news archive for reference.

Thank you

September 19, 2006 15:30:00
We have finally found the cause of the problem that some users were experiencing on their Linux systems. It has to do with the stacksize setting on your machine which is for some distros (SuSE 9.3 and 10 for example) set to unlimited and for others (FCx, Ubuntu, etc) set to a limited value like 10240. On the Bash and K shells your setting can be seen by typing 'ulimit -s' in a terminal. With TC shell it is 'limit'. To make the Charmm 'exit 1' errors go away, please set the stacksize to unlimited using the command 'ulimit -s unlimited'. This is not saying that Charmm will use all of your memory (it won't), but it gives us a little bit more space to do our simulations correctly and without errors. Please let us know if this does not work for you. If it does work, please add this command to your shell initialization file (.bashrc, .tcshrc, .kshrc, etc) in your home directory. Of course don't forget to resume the D@H project on your boincmgr in case you suspended it before.

Profile suguruhirahara
Forum moderator
Volunteer tester
Avatar

Joined: Sep 13 06
Posts: 282
ID: 15
Credit: 56,614
RAC: 0
Message 918 - Posted 7 Oct 2006 18:15:14 UTC - in response to Message ID 913 .
Last modified: 7 Oct 2006 18:15:37 UTC

Thanks for reply,

<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>


There is a temporary fix. Its in the news archive. It was a problem related to Linux... now in windows boxes it is the first time that I see it. We will investigate further. Here is the fix copied from the news archive for reference.


The same error happens when the application process is ended manually via Task Manager, whether the science application is of docking@home or not...

Anyway there is a page explains the 0x1 error @ BOINC wiki.

Thanks for reading,
suguruhirahara
____________

I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.
Memo
Forum moderator
Project developer
Project tester

Joined: Sep 13 06
Posts: 88
ID: 14
Credit: 1,666,392
RAC: 0
Message 922 - Posted 7 Oct 2006 22:14:09 UTC - in response to Message ID 918 .

Thanks for reply,
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>


There is a temporary fix. Its in the news archive. It was a problem related to Linux... now in windows boxes it is the first time that I see it. We will investigate further. Here is the fix copied from the news archive for reference.


The same error happens when the application process is ended manually via Task Manager, whether the science application is of docking@home or not...

Anyway there is a page explains the 0x1 error @ BOINC wiki.

Thanks for reading,
suguruhirahara



Thanks for the information, will look into it.
Rene
Volunteer tester
Avatar

Joined: Oct 2 06
Posts: 121
ID: 160
Credit: 109,415
RAC: 0
Message 932 - Posted 8 Oct 2006 17:32:56 UTC - in response to Message ID 918 .

The same error happens when the application process is ended manually via Task Manager, whether the science application is of docking@home or not...


Could it be Vista related..?


Profile Andre Kerstens
Forum moderator
Project tester
Volunteer tester
Avatar

Joined: Sep 11 06
Posts: 749
ID: 1
Credit: 15,199
RAC: 0
Message 934 - Posted 9 Oct 2006 1:07:58 UTC - in response to Message ID 932 .

I just checked the host as well and I can say that it is the first Longhorn machine I've seen :-) And yes, maybe that is a problem: we don't have such a machine to test and I have no clue whether the app runs well on it.

Andre

The same error happens when the application process is ended manually via Task Manager, whether the science application is of docking@home or not...


Could it be Vista related..?



____________
D@H the greatest project in the world... a while from now!
Profile DoctorNow
Volunteer tester
Avatar

Joined: Nov 13 06
Posts: 7
ID: 217
Credit: 92,503
RAC: 0
Message 1405 - Posted 14 Nov 2006 17:54:42 UTC

Hello!

The same happens to me...
I've joined yesterday and downloaded 2 wu's.
Both errored out with those messages:

<core_client_version>5.4.9</core_client_version>
<message>
Unzul�ssige Funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Starting charmm run...
ERROR - Charmm exited with code 1.
Calling BOINC finish.
</stderr_txt>


It was WU 13411 and 13412 ...
Unfortunately one of them ran over 7 hours...

I have an AMD Athlon XP 2200+ with Windows XP Pro on it...
____________
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
Memo
Forum moderator
Project developer
Project tester

Joined: Sep 13 06
Posts: 88
ID: 14
Credit: 1,666,392
RAC: 0
Message 1470 - Posted 17 Nov 2006 16:30:06 UTC

I am looking into that but not able to find what happened. I will keep you updated of any findings

Profile suguruhirahara
Forum moderator
Volunteer tester
Avatar

Joined: Sep 13 06
Posts: 282
ID: 15
Credit: 56,614
RAC: 0
Message 1607 - Posted 24 Nov 2006 19:35:45 UTC
Last modified: 24 Nov 2006 19:43:56 UTC

From this thread, several posts have been moved to another thread " large output files ". Please use the thread for making a discussion of that issue.

thanks,
suguruhirahara
____________

I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.

Profile Andre Kerstens
Forum moderator
Project tester
Volunteer tester
Avatar

Joined: Sep 11 06
Posts: 749
ID: 1
Credit: 15,199
RAC: 0
Message 1633 - Posted 27 Nov 2006 15:35:56 UTC
Last modified: 27 Nov 2006 15:36:09 UTC

Unfortunately we haven't been able to reproduce the 'Incorrect Function 0x1' message in the lab. We'll somehow need more info from people that are experiencing this error. Let us know if you see it again and provide us with the result or workunit name please. Also, any information on your system at the time of the error will probably be helpful.

Thanks
Andre
____________
D@H the greatest project in the world... a while from now!

Profile suguruhirahara
Forum moderator
Volunteer tester
Avatar

Joined: Sep 13 06
Posts: 282
ID: 15
Credit: 56,614
RAC: 0
Message 1634 - Posted 28 Nov 2006 5:15:16 UTC - in response to Message ID 1633 .
Last modified: 28 Nov 2006 5:17:09 UTC

Unfortunately we haven't been able to reproduce the 'Incorrect Function 0x1' message in the lab. We'll somehow need more info from people that are experiencing this error. Let us know if you see it again and provide us with the result or workunit name please. Also, any information on your system at the time of the error will probably be helpful.

The computer of mine, windows vista, pentium D, 1GB RAM, may encounter the error when following causes are met: either 1) ending process via Task Manager or 2) running the softwares which require great resources eg 3DMark or VirtualPC, keeping load 100% and leaving charmm running, enough to cause charmm 'crash'.

When I checked this page of the BOINC unofficial wiki, I noticed that the same issue had happened at Predictor@Home, in which the team had participated whether mainly or not. Is there any relevance here, Andre?

edit: according to the page,
Unrecoverable error for result '(result)' (Incorrect function. (0x1) - exit code 1 (0x1))
The error occurs on the reading of the Work Unit Data File (the input data).

____________

I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.
Profile Webmaster Yoda
Volunteer tester
Avatar

Joined: Nov 14 06
Posts: 43
ID: 271
Credit: 6,498
RAC: 0
Message 1641 - Posted 29 Nov 2006 0:48:58 UTC
Last modified: 29 Nov 2006 0:50:15 UTC

I just got another one. http://docking.utep.edu/result.php?resultid=53166

I don't know exactly how it happened as I was away at the time, but the task was suspended yesterday (to meet deadlines on other projects) and the PC has been switched off for a short time.

Only 45 minutes crunching lost - the error log file may have more details.

Athlon 64 3700+
1GB PC4000 RAM
64 bit Windows XP Professional

On another note, I have detached my Athlon XP running Puppy Linux. Some WU crashed, two completed but were deemed invalid. Still two WU pending but if history repeats itself, they will also be invalid, so it's pointless doing more Docking on that computer. I might try another project (with shorter work units) to see whether it's the computer or Docking that has problems...
____________


Join the #1 Aussie Alliance on Docking@Home

Profile Andre Kerstens
Forum moderator
Project tester
Volunteer tester
Avatar

Joined: Sep 11 06
Posts: 749
ID: 1
Credit: 15,199
RAC: 0
Message 1642 - Posted 29 Nov 2006 4:00:40 UTC - in response to Message ID 1634 .

Thanks for the boinc wiki link Suguru. I see that both P@H and CPDN are experiencing this error (and us of course). They all are different apps though with one thing in common: they are all Fortran applications. The error is thrown by the Fortran runtime environment and can have many different causes. We haven't found out exactly why Charmm throws this error, but it is not the same reason as in P@H (who use the MFold application).

If you have many other memory-heavy apps running at the same time as Charmm, this might be the cause of problem, since Charmm uses quite a bit of memory: with the current wu probably around 50 MB; with larger wu's that we will put on the system later, maybe up to 200 MB.

Thanks for the feedback,
Andre

The computer of mine, windows vista, pentium D, 1GB RAM, may encounter the error when following causes are met: either 1) ending process via Task Manager or 2) running the softwares which require great resources eg 3DMark or VirtualPC, keeping load 100% and leaving charmm running, enough to cause charmm 'crash'.

When I checked this page of the BOINC unofficial wiki, I noticed that the same issue had happened at Predictor@Home, in which the team had participated whether mainly or not. Is there any relevance here, Andre?

edit: according to the page,
Unrecoverable error for result '(result)' (Incorrect function. (0x1) - exit code 1 (0x1))
The error occurs on the reading of the Work Unit Data File (the input data).


____________
D@H the greatest project in the world... a while from now!
Profile Andre Kerstens
Forum moderator
Project tester
Volunteer tester
Avatar

Joined: Sep 11 06
Posts: 749
ID: 1
Credit: 15,199
RAC: 0
Message 1643 - Posted 29 Nov 2006 4:13:32 UTC - in response to Message ID 1641 .

Thanks for the note Yoda. Please let us know if you experience the same problems with other projects.

Thanks,
Andre

I just got another one. http://docking.utep.edu/result.php?resultid=53166

I don't know exactly how it happened as I was away at the time, but the task was suspended yesterday (to meet deadlines on other projects) and the PC has been switched off for a short time.

Only 45 minutes crunching lost - the error log file may have more details.

Athlon 64 3700+
1GB PC4000 RAM
64 bit Windows XP Professional

On another note, I have detached my Athlon XP running Puppy Linux. Some WU crashed, two completed but were deemed invalid. Still two WU pending but if history repeats itself, they will also be invalid, so it's pointless doing more Docking on that computer. I might try another project (with shorter work units) to see whether it's the computer or Docking that has problems...


____________
D@H the greatest project in the world... a while from now!
Profile Webmaster Yoda
Volunteer tester
Avatar

Joined: Nov 14 06
Posts: 43
ID: 271
Credit: 6,498
RAC: 0
Message 1649 - Posted 29 Nov 2006 4:37:12 UTC - in response to Message ID 1643 .

Thanks for the note Yoda. Please let us know if you experience the same problems with other projects.


The Athlon XP (host 760 on Windows, 1032 on Linux) is running RieselSieve and Proteins@home right now (on Windows) without any problems.

I'll switch it back to Linux later today (do a bit of Rosetta@home) and see how it goes. This same PC had one invalid result with Docking under Windows.
Profile suguruhirahara
Forum moderator
Volunteer tester
Avatar

Joined: Sep 13 06
Posts: 282
ID: 15
Credit: 56,614
RAC: 0
Message 1654 - Posted 29 Nov 2006 5:45:44 UTC - in response to Message ID 1642 .

Hi Andre,

If you have many other memory-heavy apps running at the same time as Charmm, this might be the cause of problem, since Charmm uses quite a bit of memory: with the current wu probably around 50 MB; with larger wu's that we will put on the system later, maybe up to 200 MB.

Really? Task manager shows that charmm occupys just 10-11MB (when two threads are used 22-23MB). But it's when the science application runs stably. I'm not sure whether charmm uses more than those amount of RAM when it runs unstably.

thanks for reading,
suguruhirahara

____________

I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions.
Profile Webmaster Yoda
Volunteer tester
Avatar

Joined: Nov 14 06
Posts: 43
ID: 271
Credit: 6,498
RAC: 0
Message 1657 - Posted 29 Nov 2006 13:04:29 UTC - in response to Message ID 1649 .

Thanks for the note Yoda. Please let us know if you experience the same problems with other projects.


The Athlon XP (host 760 on Windows, 1032 on Linux) is running RieselSieve and Proteins@home right now (on Windows) without any problems.

I'll switch it back to Linux later today (do a bit of Rosetta@home) and see how it goes. This same PC had one invalid result with Docking under Windows.


Update: it's run 3 Rosetta and 5 Einstein work units under Linux since my last message. No sign of any problems there.

One of the two Docking work units that were pending has now met quorum and was valid. In this case, all three computers in the quorum were Athlon XP. See http://docking.utep.edu/workunit.php?wuid=14089
____________


Join the #1 Aussie Alliance on Docking@Home
Profile Webmaster Yoda
Volunteer tester
Avatar

Joined: Nov 14 06
Posts: 43
ID: 271
Credit: 6,498
RAC: 0
Message 1683 - Posted 2 Dec 2006 7:01:11 UTC

The Athlon XP's last Docking WU also got zero credit - invalid.

It has been running Einstein and Rosetta without any trouble (under Puppy Linux). It passes Memtest86. It processes Proteins and RieselSieve work units without errors under Windows.

My Athlon 64 running 64 bit Windows XP just crashed (power outage) and on resuming, the docking WU errored out with an 0x1, while the SETI WU it also had in memory at the time of the power outage lives on. So there's definitely some work to do on the stability of this project's application. Hopefully the new charmm app will address some of these issues when it comes out.

I am not going to whinge about "lost credit" - this is an alpha project after all. Just hope all these problem reports help in some way.

____________


Join the #1 Aussie Alliance on Docking@Home

Profile Andre Kerstens
Forum moderator
Project tester
Volunteer tester
Avatar

Joined: Sep 11 06
Posts: 749
ID: 1
Credit: 15,199
RAC: 0
Message 1688 - Posted 3 Dec 2006 1:21:36 UTC - in response to Message ID 1683 .

Your problem reports help enormously. Thanks a lot for those!

The problem where Charmm exits with error 0x1 after a resume, is known: because we checkpoint actually quite often (this will be corrected in the new release), the chances are high that when your machine freezes, we are writing a checkpoint at that time. After resuming the calculation, this corrupted checkpoint will be read in and the app exits, because it can't read the file correctly. We will have to look at doing our checkpointing more atomicly so that the chance of a crash because of a corrupt checkpoint file will be reduced to 0.

The athlon problem is the same as the PII / III problem, Athlons seem to give different results than Opterons and Semprons. We'll address this with a modified HR mechanism soon.

Thanks Yoda!
Andre

The Athlon XP's last Docking WU also got zero credit - invalid.

It has been running Einstein and Rosetta without any trouble (under Puppy Linux). It passes Memtest86. It processes Proteins and RieselSieve work units without errors under Windows.

My Athlon 64 running 64 bit Windows XP just crashed (power outage) and on resuming, the docking WU errored out with an 0x1, while the SETI WU it also had in memory at the time of the power outage lives on. So there's definitely some work to do on the stability of this project's application. Hopefully the new charmm app will address some of these issues when it comes out.

I am not going to whinge about "lost credit" - this is an alpha project after all. Just hope all these problem reports help in some way.


____________
D@H the greatest project in the world... a while from now!

Message boards : Number crunching : "Incorrect function (0x1)"?

Database Error
: The MySQL server is running with the --read-only option so it cannot execute this statement
array(3) {
  [0]=>
  array(7) {
    ["file"]=>
    string(47) "/boinc/projects/docking/html_v2/inc/db_conn.inc"
    ["line"]=>
    int(97)
    ["function"]=>
    string(8) "do_query"
    ["class"]=>
    string(6) "DbConn"
    ["object"]=>
    object(DbConn)#25 (2) {
      ["db_conn"]=>
      resource(90) of type (mysql link persistent)
      ["db_name"]=>
      string(7) "docking"
    }
    ["type"]=>
    string(2) "->"
    ["args"]=>
    array(1) {
      [0]=>
      &string(50) "update DBNAME.thread set views=views+1 where id=75"
    }
  }
  [1]=>
  array(7) {
    ["file"]=>
    string(48) "/boinc/projects/docking/html_v2/inc/forum_db.inc"
    ["line"]=>
    int(60)
    ["function"]=>
    string(6) "update"
    ["class"]=>
    string(6) "DbConn"
    ["object"]=>
    object(DbConn)#25 (2) {
      ["db_conn"]=>
      resource(90) of type (mysql link persistent)
      ["db_name"]=>
      string(7) "docking"
    }
    ["type"]=>
    string(2) "->"
    ["args"]=>
    array(3) {
      [0]=>
      object(BoincThread)#3 (16) {
        ["id"]=>
        string(2) "75"
        ["forum"]=>
        string(1) "2"
        ["owner"]=>
        string(2) "15"
        ["status"]=>
        string(1) "0"
        ["title"]=>
        string(27) ""Incorrect function (0x1)"?"
        ["timestamp"]=>
        string(10) "1165108896"
        ["views"]=>
        string(4) "1946"
        ["replies"]=>
        string(2) "19"
        ["activity"]=>
        string(23) "2.8572636183352998e-127"
        ["sufferers"]=>
        string(1) "0"
        ["score"]=>
        string(1) "0"
        ["votes"]=>
        string(1) "0"
        ["create_time"]=>
        string(10) "1160224615"
        ["hidden"]=>
        string(1) "0"
        ["sticky"]=>
        string(1) "0"
        ["locked"]=>
        string(1) "0"
      }
      [1]=>
      &string(6) "thread"
      [2]=>
      &string(13) "views=views+1"
    }
  }
  [2]=>
  array(7) {
    ["file"]=>
    string(63) "/boinc/projects/docking/html_v2/user/community/forum/thread.php"
    ["line"]=>
    int(184)
    ["function"]=>
    string(6) "update"
    ["class"]=>
    string(11) "BoincThread"
    ["object"]=>
    object(BoincThread)#3 (16) {
      ["id"]=>
      string(2) "75"
      ["forum"]=>
      string(1) "2"
      ["owner"]=>
      string(2) "15"
      ["status"]=>
      string(1) "0"
      ["title"]=>
      string(27) ""Incorrect function (0x1)"?"
      ["timestamp"]=>
      string(10) "1165108896"
      ["views"]=>
      string(4) "1946"
      ["replies"]=>
      string(2) "19"
      ["activity"]=>
      string(23) "2.8572636183352998e-127"
      ["sufferers"]=>
      string(1) "0"
      ["score"]=>
      string(1) "0"
      ["votes"]=>
      string(1) "0"
      ["create_time"]=>
      string(10) "1160224615"
      ["hidden"]=>
      string(1) "0"
      ["sticky"]=>
      string(1) "0"
      ["locked"]=>
      string(1) "0"
    }
    ["type"]=>
    string(2) "->"
    ["args"]=>
    array(1) {
      [0]=>
      &string(13) "views=views+1"
    }
  }
}
query: update docking.thread set views=views+1 where id=75