| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Computer overcommited? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 20
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The error doesn't seem to be that harmless after all, there was an unrecoverable error:
send: -1 send: Bad file descriptor connect: Die Operation ist jetzt in Bearbeitung 2007-04-12 17:36:01 [World Community Grid] Unrecoverable error for result 10001030-10001604_0 (process exited with code 131 (0x83)) 2007-04-12 17:36:01 [World Community Grid] Unrecoverable error for result 10001030-10001604_0 (process exited with code 131 (0x83)) 2007-04-12 17:36:01 [World Community Grid] Deferring scheduler requests for 1 minutes and 0 seconds 2007-04-12 17:36:01 [---] Rescheduling CPU: application exited 2007-04-12 17:36:01 [World Community Grid] Computation for task 10001030-10001604_0 finished 2007-04-12 17:36:01 [World Community Grid] Starting task faah1481_d081n886_x2AZ8_01_2 using faah version 530 2007-04-12 17:36:03 [World Community Grid] Started upload of file 10001030-10001604_0_0 2007-04-12 17:36:13 [World Community Grid] Finished upload of file 10001030-10001604_0_0 2007-04-12 17:36:13 [World Community Grid] Throughput 84787 bytes/sec I'd show you the error log, but as yet the result is still listed as being in progress when I click on https://secure.worldcommunitygrid.org/ms/viewBoincResults.do |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
according oogle, the 'Bad Line Descriptor' hints at a corrupted files or file system.
----------------------------------------http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/009583.html The Genome Comparison goes awry, but is the FightAIDS@home job still running?
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Apr 12, 2007 4:19:47 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
according oogle, the 'Bad Line Descriptor' hints at a corrupted files or file system. http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/009583.html The Genome Comparison goes awry, but is the FightAIDS@home job still running? It is still running, but only 13 % percent finished so far. I'll keep you püosted on how it goes. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
according oogle, the 'Bad Line Descriptor' hints at a corrupted files or file system. http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/009583.html The Genome Comparison goes awry, but is the FightAIDS@home job still running? I just tried shutting down and then restarting again. There is no error message or problem when I start the client, that only happens when I start the manager as well. That makes sense, I ver has an error message or problem as long as I only started the client. In the future I'll only start the manager when I have to abort a result. Btw, in the meantime the manager reports that the project that has been reported as being faulty has been uploaded. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So here are the error messages:[/]
1) 10001030-10001604 <core_client_version>5.4.11</core_client_version> <message> process exited with code 131 (0x83) </message> <stderr_txt> SIGSEGV: segmentation violation Stack trace (2 frames): wcg_fcg1_ssearch_5.14_i686-pc-linux-gnu(boinc_catch_signal+0x57)[0x80b6247] [0xb7fa5420] Exiting... </stderr_txt> ---------------------------------------------------------------------------------------------------- 2)faah1449_d016n829_x2AZ8_00 <core_client_version>5.4.11</core_client_version> <message> aborted by user </message> <stderr_txt> INFO: wcg_faah_autodock_5.30_i686-pc-linux-gnu Start AutoGrid... About to call graphics init INFO:[15:10:48] Start AutoGrid... autogrid: autogrid4: Successful Completion. Starting to checkpoint ... Checkpoint complete INFO:[15:11:51] End AutoGrid... Beginning AutoDock... Virtual File wcg_autodock4.dlg resolves as physical file ../../projects/www.worldcommunitygrid.org/faah1449_d016n829_x2AZ8_00_2_1 INFO: Setting num_generations: 27000 Setting maxGen to 6750 autodock4: WARNING: Unrecognized keyword in docking parameter file, in line: compute_unbound_extended # compute extended ligand energyINFO: No state to restore. Start from the beginning. About to enter main loop...(dockings already completed: 0) call_glss(): pop_size: 200 num_evals: 10000000 start: [15:11:54] _maxGenSeenSoFar changed: 6750 call_glss(): end: [15:15:23] Updating Best Energy for WU: 0.00 Starting to checkpoint ... Checkpoint complete call_glss(): pop_size: 200 num_evals: 10000000 start: [15:15:23] call_glss(): end: [15:19:02] Starting to checkpoint ... Checkpoint complete call_glss(): pop_size: 200 num_evals: 10000000 start: [15:19:02] call_glss(): end: [15:22:44] Updating Best Energy for WU: -5.65 Starting to checkpoint ... Checkpoint complete call_glss(): pop_size: 200 num_evals: 10000000 start: [15:22:44] call_glss(): end: [15:26:50] Updating Best Energy for WU: -5.78 Starting to checkpoint ... Checkpoint complete call_glss(): pop_size: 200 num_evals: 10000000 start: [15:26:51] INFO: wcg_faah_autodock_5.30_i686-pc-linux-gnu Start AutoGrid... About to call graphics init AG Check: Found receptor.C.map Beginning AutoDock... Virtual File wcg_autodock4.dlg resolves as physical file ../../projects/www.worldcommunitygrid.org/faah1449_d016n829_x2AZ8_00_2_1 INFO: Setting num_generations: 27000 Setting maxGen to 6750 autodock4: WARNING: Unrecognized keyword in docking parameter file, in line: compute_unbound_extended # compute extended ligand energyAbout to enter main loop...(dockings already completed: 4) call_glss(): pop_size: 200 num_evals: 10000000 start: [15:32:14] _maxGenSeenSoFar changed: 6750 </stderr_txt> -------------------------------------------------------------------------------------------------------- 3)10000581-10001520[/] <core_client_version>5.4.11</core_client_version> <message> aborted by user </message> ---------------------------------------------------------------- The last one had been too old Btw, by now I have updated to version 5.8.17. |
||
|
|
D_T_G
Advanced Cruncher Poland Joined: Jan 25, 2007 Post Count: 56 Status: Offline Project Badges: 
|
Btw, by now I have updated to version 5.8.17.  ---------------------------------------- [Edit 1 times, last edit by D_T_G at Apr 13, 2007 4:17:41 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
RalfG,
----------------------------------------Have you run a disk / file system integrity check? The FAAH message log looks identical to the first part of one i just completed - valid. How did the job end (per the Result Status page) or is it still running?
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
RalfG, Have you run a disk / file system integrity check? The FAAH message log looks identical to the first part of one i just completed - valid. How did the job end (per the Result Status page) or is it still running? Which faah? The faah1449_d016n829_x2AZ8_00_2_1 had an error, but the result seems to have been uploaded, while the faah1481_d081n886_x2AZ8_01_2 is still running. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Btw, by now I have updated to version 5.8.17. Thanks!  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The faah1481_d081n886_x2AZ8_01_2 result is complete, without any error message. I'l check the file system tomorrow, but it looks as if the problem was solved after the upgrade.
|
||
|
|
|