|
1)
Message boards :
BOINC Manager :
Developers request help on finding errors
(Message 6215)
Posted 27 Oct 2006 by Jakob Creutzfeld Post: 2006-10-27 01:21:55 [---] Curl error: a libcurl function was given a bad argument Ok (I thought something like that...). Thanks, Jord! |
|
2)
Message boards :
BOINC Manager :
Developers request help on finding errors
(Message 6213)
Posted 27 Oct 2006 by Jakob Creutzfeld Post: Hi there! since the last weekly outage on Oct 24th I sporadically receive this message: 2006-10-27 01:21:47 [---] General prefs: from SETI@home (last modified 2006-10-22 23:30:11) 2006-10-27 01:21:47 [---] General prefs: using separate prefs for home 2006-10-27 01:21:49 [SETI@home] Started download of file 01my03aa.4308.1266.154822.3.221 2006-10-27 01:21:49 [SETI@home] Started download of file 01my03aa.4308.1266.154822.3.222 2006-10-27 01:21:55 [SETI@home] Finished download of file 01my03aa.4308.1266.154822.3.221 2006-10-27 01:21:55 [SETI@home] Throughput 71967 bytes/sec 2006-10-27 01:21:55 [---] Curl error: a libcurl function was given a bad argument 2006-10-27 01:21:55 [SETI@home] Finished download of file 01my03aa.4308.1266.154822.3.222 2006-10-27 01:21:55 [SETI@home] Throughput 78285 bytes/sec 2006-10-27 01:21:56 [---] Starting 01my03aa.4308.1266.154822.3.221_3 2006-10-27 01:21:56 [SETI@home] Starting task 01my03aa.4308.1266.154822.3.221_3 using setiathome_enhanced version 517 2006-10-27 01:21:56 [---] Starting 01my03aa.4308.1266.154822.3.222_2 2006-10-27 01:21:56 [SETI@home] Starting task 01my03aa.4308.1266.154822.3.222_2 using setiathome_enhanced version 517 2006-10-27 01:46:41 [SETI@home] Computation for task 01my03aa.4308.1266.154822.3.222_2 finished 2006-10-27 01:46:41 [SETI@home] Resuming task 15my03aa.5778.8880.665884.3.131_0 using setiathome_enhanced version 517 2006-10-27 01:46:43 [SETI@home] Started upload of file 01my03aa.4308.1266.154822.3.222_2_0 2006-10-27 01:46:47 [SETI@home] Computation for task 01my03aa.4308.1266.154822.3.221_3 finished 2006-10-27 01:46:47 [SETI@home] Resuming task 15my03aa.5778.9569.73576.3.121_1 using setiathome_enhanced version 517 2006-10-27 01:46:49 [SETI@home] Started upload of file 01my03aa.4308.1266.154822.3.221_3_0 2006-10-27 01:47:01 [---] Curl error: a libcurl function was given a bad argument 2006-10-27 01:47:01 [---] Curl error: a libcurl function was given a bad argument 2006-10-27 01:47:01 [SETI@home] Finished upload of file 01my03aa.4308.1266.154822.3.222_2_0 2006-10-27 01:47:01 [SETI@home] Throughput 1009 bytes/sec 2006-10-27 01:47:04 [SETI@home] Finished upload of file 01my03aa.4308.1266.154822.3.221_3_0 2006-10-27 01:47:04 [SETI@home] Throughput 4223 bytes/sec 2006-10-27 01:51:52 [SETI@home] Computation for task 15my03aa.5778.8880.665884.3.131_0 finished 2006-10-27 01:51:52 [---] Starting 13my03aa.2062.28480.634652.3.101_2 however, the concerning Seti results are downloaded, crunched and uploaded successfully. This error also doesn't show up constantly. It is only generated on every 5-8 up-/download. Okay, here are the usual Infos (I know, I know...). BOINC version 5.6.5 (former 5.4.11, version 5.6.5 installed on Oct 22nd over the existing one (that is, I haven't removed 5.4.11 before)). Was working fine between 22nd and 24th. The first time this error has came up was on Oct 24th about 20:00 UTC. Did a PC restart since then. Direct link to the Internet (ADSL). Using Norton AntiVirus 2006 (haven't ever had any issues with it). I have searched this fora, the SetiBeta fora (both with no success), and haven't seen someone else who has mentioned this on the Seti fora. So I thought, I do post this here... Panic Mode On?!? Nope. Or? Regards Andy |
|
3)
Message boards :
BOINC Manager :
Developers request help on finding errors
(Message 5668)
Posted 19 Sep 2006 by Jakob Creutzfeld Post: Hi there! I'm not sure, but I may have found an error in the BOINC code base. In File 'Scheduler_op.C', function 'bool SCHEDULER_OP::poll()' at the Line "cur_proj->attach_failed(ERR_ATTACH_FAIL_SERVER_ERROR);", it passes "ERR_ATTACH_FAIL_SERVER_ERROR" to the function "attach_failed" (as can be seen). ok. But this parameter isn't handled in the switch() function over there. switch(error_num){ There is no "case ERR_ATTACH_FAIL_SERVER_ERROR", so errors which where passed in this manner are not resolved, and the project detaches without any given reason. I don't know, if this is resolved in the actual Beta version of BOINC, but might be worth to check. Regards Andy **EDIT** I think this (ERR_ATTACH_FAIL_SERVER_ERROR) happens, if the user name in an account is left blank. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.