Project: 2605 (Run 5, Clone 15, Gen 49)

[7im]

This one's been shutting itself off every time I start it, for the last 24 hours.
Running on a standard 1.66 GHz Core Duo mini, 2 GB ram, OSX 10.4.11

Already replaced the client and the core, no joy.

When running in InCrease:

[21:26:12] Writing local files
[21:26:13] Completed 0 out of 500000 steps (0 percent)
[21:26:13]
[21:26:13] Folding@home Core Shutdown: INTERRUPTED
[21:26:17] CoreStatus = 66 (102)
[21:26:17] + Shutdown requested by user. Exiting.***** Got a SIGTERM signal (15)
[21:26:17] Killing all core threads

Folding@Home Client Shutdown.[/quote]

When running under Terminal:

[13:22:23] Protein: Protein in POPC
[13:22:23] Writing local files
[13:22:24] Extra SSE boost OK.
[13:22:25] Writing local files
[13:22:25] Completed 0 out of 500000 steps (0 percent)
[13:22:25]
[13:22:25] Folding@home Core Shutdown: INTERRUPTED
[cli_1]: aborting job:
Fatal error in MPI_Sendrecv: Error message texts are not available
[0]0:Return code = 102
[0]1:Return code = 1
[0]2:Return code = 0, signaled with Segmentation fault
[0]3:Return code = 0, signaled with Segmentation fault
[13:22:30] CoreStatus = 66 (102)
[13:22:30] + Shutdown requested by user. Exiting.***** Got a SIGTERM signal (15)
[13:22:30] Killing all core threads

Is this me or is it the WU? (Which I'm dumping now, in order to move on)

[toTOW]

When you see Segmentation Fault, there's only few possibles causes : memory (or maybe CPU) issue or bad WU

[Xilikon]

Same here :

Code: Select all

[04:31:47] Preparing to commence simulation
[04:31:47] - Ensuring status. Please wait- Created dyn
[04:31:47] - Files status OK
[04:31:47] - Expanded 2431392 -> 12908109 (decompressed 530.8 percent)
[04:31:48] - Starting from initial work packet
[04:31:48] 
[04:31:48] Project: 2605 (Run 5, Clone 15, Gen 49)
[04:31:48] 
[04:31:48] Assembly optimizations on if available.
[04:31:48] Entering M.D.
[04:32:05] 8 percent)
[04:32:05] cket
[04:32:05] 
[04:32:05] Project: 2605 (Run 5, Clone 15, Gen 49)
[04:32:05] 
[04:32:05] Entering M.D.
[04:32:05] one 15, Gen 49)
[04:32:05] 
[04:32:05] Entering M.D.
[04:32:12] g local files
[04:32:12] in in POPC
[04:32:12] Writing local files
[04:32:13] Extra SSE boost OK.
[04:32:15] Finalizing output
[04:32:19] CoreStatus = 1 (1)
[04:32:19] Client-core communications error: ERROR 0x1
[04:32:19] Deleting current work unit & continuing...
[04:36:44] - Warning: Could not delete all work unit files (7): Core returned invalid code
[04:36:44] Trying to send all finished work units
[04:36:44] + No unsent completed units remaining.
[04:36:44] - Preparing to get new work unit...
[04:36:44] + Attempting to get work packet

[Macaholic]

So why in the world has this unit not been pulled? It just showed up on one of my machines (Mac mini C2D 2.0GHz) doing the same damned thing. I would post the log, but what in the hell would be the point? I'll just leave the machine idle. Thank you, so much.

[Xilikon]

Got it on my file server, I pulled my hair all day for nothing because I forgot to check if there is a report about that

[parkut]

Got this one myself on a Quad CentOS x64 Linux system.
Linux SMP Client Version 6.22 Betar4
Project: 2605 (Run 5, Clone 15, Gen 49)
Immediately errored 0x0 three times in a row . Now working on another WU.