6508 (Run 11, Clone 192, Gen 21)

[pluto7777]

Code: Select all

[07:04:09] + Attempting to send results [November 7 07:04:09 UTC]
[07:04:21] + Results successfully sent
[07:04:21] Thank you for your contribution to Folding@Home.
[07:04:21] + Number of Units Completed: 9

Warning: Ignoring unknown arg 
Warning: Ignoring unknown arg 
[07:04:26] - Preparing to get new work unit...
[07:04:26] Cleaning up work directory
[07:04:26] + Attempting to get work packet
[07:04:26] Passkey found
[07:04:26] - Connecting to assignment server
[07:04:27] - Successful: assigned to (171.64.65.62).
[07:04:27] + News From Folding@Home: Welcome to Folding@Home
[07:04:27] Loaded queue successfully.
[07:04:28] + Closed connections
[07:04:28] 
[07:04:28] + Processing work unit
[07:04:28] Core required: FahCore_78.exe
[07:04:28] Core found.
[07:04:28] Working on queue slot 00 [November 7 07:04:28 UTC]
[07:04:28] + Working ...
Warning: Ignoring unknown arg 
Warning: Ignoring unknown arg 
[07:04:28] 
[07:04:28] *------------------------------*
[07:04:28] Folding@Home Gromacs Core
[07:04:28] Version 1.90 (March 8, 2006)
[07:04:28] 
[07:04:28] Preparing to commence simulation
[07:04:28] - Looking at optimizations...
[07:04:28] - Created dyn
[07:04:28] - Files status OK
[07:04:28] - Expanded 473008 -> 2359929 (decompressed 498.9 percent)
[07:04:29] - Starting from initial work packet
[07:04:29] 
[07:04:29] Project: 6508 (Run 11, Clone 192, Gen 21)
[07:04:29] 
[07:04:29] Assembly optimizations on if available.
[07:04:29] Entering M.D.

  Gromacs is Copyright (c) 1991-2003, University of Groningen, The Netherlands
        This inclusion of Gromacs code in the Folding@Home Core is under
        a special license (see http://folding.stanford.edu/gromacs.html)
         specially granted to Stanford by the copyright holders. If you
          are interested in using Gromacs, visit www.gromacs.org where
                you can download a free version of Gromacs under
         the terms of the GNU General Public License (GPL) as published
       by the Free Software Foundation; either version 2 of the License,
                     or (at your option) any later version.

[07:04:35] Protein: proG_12 in water
[07:04:35] 
[07:04:35] Writing local files
[07:04:35] Extra SSE boost OK.
[07:04:35] Writing local files
[07:04:35] Completed 0 out of 250000 steps  (0%)
[07:09:50] Writing local files
[07:09:50] Completed 2500 out of 250000 steps  (1%)
[07:15:05] Writing local files
[07:15:05] Completed 5000 out of 250000 steps  (2%)
[07:20:20] Writing local files
[07:20:20] Completed 7500 out of 250000 steps  (3%)
[07:25:36] Writing local files
[07:25:36] Completed 10000 out of 250000 steps  (4%)
[07:30:51] Writing local files
[07:30:51] Completed 12500 out of 250000 steps  (5%)
[07:36:05] Writing local files
[07:36:05] Completed 15000 out of 250000 steps  (6%)
[07:41:20] Writing local files
[07:41:20] Completed 17500 out of 250000 steps  (7%)
[07:46:37] Writing local files
[07:46:37] Completed 20000 out of 250000 steps  (8%)
[07:51:52] Writing local files
[07:51:52] Completed 22500 out of 250000 steps  (9%)
[07:57:07] Writing local files
[07:57:07] Completed 25000 out of 250000 steps  (10%)
[08:02:21] Writing local files
[08:02:21] Completed 27500 out of 250000 steps  (11%)
[08:07:36] Writing local files
[08:07:36] Completed 30000 out of 250000 steps  (12%)
[08:12:50] Writing local files
[08:12:50] Completed 32500 out of 250000 steps  (13%)
[08:18:05] Writing local files
[08:18:05] Completed 35000 out of 250000 steps  (14%)
[08:23:19] Writing local files
[08:23:19] Completed 37500 out of 250000 steps  (15%)
[08:28:33] Writing local files
[08:28:33] Completed 40000 out of 250000 steps  (16%)
[08:33:50] Writing local files
[08:33:50] Completed 42500 out of 250000 steps  (17%)
[08:39:06] Writing local files
[08:39:06] Completed 45000 out of 250000 steps  (18%)
[08:44:23] Writing local files
[08:44:23] Completed 47500 out of 250000 steps  (19%)
[08:49:40] Writing local files
[08:49:40] Completed 50000 out of 250000 steps  (20%)
[08:54:57] Writing local files
[08:54:57] Completed 52500 out of 250000 steps  (21%)
[09:00:12] Writing local files
[09:00:12] Completed 55000 out of 250000 steps  (22%)
[09:05:27] Writing local files
[09:05:27] Completed 57500 out of 250000 steps  (23%)
[09:10:42] Writing local files
[09:10:42] Completed 60000 out of 250000 steps  (24%)
[09:15:58] Writing local files
[09:15:58] Completed 62500 out of 250000 steps  (25%)
[09:21:13] Writing local files
[09:21:13] Completed 65000 out of 250000 steps  (26%)
[09:26:28] Writing local files
[09:26:28] Completed 67500 out of 250000 steps  (27%)
[09:31:44] Writing local files
[09:31:44] Completed 70000 out of 250000 steps  (28%)
[09:37:00] Writing local files
[09:37:00] Completed 72500 out of 250000 steps  (29%)
[09:42:17] Writing local files
[09:42:17] Completed 75000 out of 250000 steps  (30%)
[09:47:33] Writing local files
[09:47:33] Completed 77500 out of 250000 steps  (31%)
[09:52:49] Writing local files
[09:52:49] Completed 80000 out of 250000 steps  (32%)
[09:58:04] Writing local files
[09:58:04] Completed 82500 out of 250000 steps  (33%)
[10:03:20] Writing local files
[10:03:20] Completed 85000 out of 250000 steps  (34%)
[10:08:37] Writing local files
[10:08:37] Completed 87500 out of 250000 steps  (35%)
[10:13:53] Writing local files
[10:13:53] Completed 90000 out of 250000 steps  (36%)
[10:19:08] Writing local files
[10:19:08] Completed 92500 out of 250000 steps  (37%)
[10:24:24] Writing local files
[10:24:24] Completed 95000 out of 250000 steps  (38%)
[10:29:40] Writing local files
[10:29:40] Completed 97500 out of 250000 steps  (39%)
[10:34:56] Writing local files
[10:34:57] Completed 100000 out of 250000 steps  (40%)
[10:40:13] Writing local files
[10:40:13] Completed 102500 out of 250000 steps  (41%)
[10:45:29] Writing local files
[10:45:29] Completed 105000 out of 250000 steps  (42%)
[10:50:43] Writing local files
[10:50:43] Completed 107500 out of 250000 steps  (43%)
[10:55:58] Writing local files
[10:55:58] Completed 110000 out of 250000 steps  (44%)
[11:01:11] Writing local files
[11:01:12] Completed 112500 out of 250000 steps  (45%)
[11:06:27] Writing local files
[11:06:27] Completed 115000 out of 250000 steps  (46%)
[11:11:43] Writing local files
[11:11:43] Completed 117500 out of 250000 steps  (47%)
[11:16:58] Writing local files
[11:16:58] Completed 120000 out of 250000 steps  (48%)
[11:22:14] Writing local files
[11:22:14] Completed 122500 out of 250000 steps  (49%)
[11:27:30] Writing local files
[11:27:30] Completed 125000 out of 250000 steps  (50%)
[11:32:47] Writing local files
[11:32:47] Completed 127500 out of 250000 steps  (51%)
[11:38:03] Writing local files
[11:38:03] Completed 130000 out of 250000 steps  (52%)
[11:43:18] Writing local files
[11:43:18] Completed 132500 out of 250000 steps  (53%)
[11:48:34] Writing local files
[11:48:34] Completed 135000 out of 250000 steps  (54%)
[11:53:51] Writing local files
[11:53:51] Completed 137500 out of 250000 steps  (55%)
[11:59:06] Writing local files
[11:59:06] Completed 140000 out of 250000 steps  (56%)
[12:04:21] Writing local files
[12:04:21] Completed 142500 out of 250000 steps  (57%)
[12:09:36] Writing local files
[12:09:36] Completed 145000 out of 250000 steps  (58%)
[12:14:50] Writing local files
[12:14:50] Completed 147500 out of 250000 steps  (59%)
Segmentation fault
[12:19:13] CoreStatus = 8B (139)
[12:19:13] Client-core communications error: ERROR 0x8b
[12:19:13] This is a sign of more serious problems, shutting down.

[sortofageek]

Could we see more of the log, please? What happened after that? Did it send results? Delete? What?

I checked, but there is no data back from my query.

[Tobit]

I'm also curious as to what OS you are running on and the version of the client you are using. Please also tell us what flags you are passing to the client as you have two "Warning: Ignoring unknown arg" entries in your log.

[pluto7777]

I'm also curious as to what OS you are running on and the version of the client you are using. Please also tell us what flags you are passing to the client as you have two "Warning: Ignoring unknown arg" entries in your log.

Linux Ubuntu 10.10 kernel 2.6.35 . I'm using the -advancedmethods flag but I'm not sure how that could lead to a segfault
I'm not overclocking and I am running ncsd as someone advised in the Linux forum otherwise F@H version 6.29 wouldn't even run.
There are also load balancing issues with SMP which is why I don't use it.
I use to fold 24-7 running Ubuntu 8.4-9.10 with F@H client 6.02 no problems whatsoever.

Somewhere Somehow something has gone massively wrong. If it's an issue with Ubuntu I have no issues changing distributions. It isn't the only distribution with major problems though.

Could we see more of the log, please? What happened after that? Did it send results? Delete? What?

I checked, but there is no data back from my query.

No you cannot. Restarting the client results in the same failure forcing me to manually delete everything.

[Fireball0236]

The correct flag is "-advmethods" not "-advancedmethods". As for the other issues, can't be of help, sorry.


~ Fireball0236

[bruce]

Without the details from FAHlog, we won't be able to support you.

[7im]

...
Linux Ubuntu 10.10 kernel 2.6.35.

As you said, fah works just fine with all previous versions "running Ubuntu 8.4-9.10 with F@H client" Probably a good hint that something changed in v10 that is not compatible with FAH.

The segfault error is a known issue. 10.x versions of Ubuntu don't work with the current version of the v6 fah client. Go back to v9.x Ubuntu, or use one of the workarounds documented here in the forum. Search for segfault or NCSD.

[Tobit]

The segfault error is a known issue. 10.x versions of Ubuntu don't work with the current version of the v6 fah client. Go back to v9.x Ubuntu, or use one of the workarounds documented here in the forum. Search for segfault or NCSD.

but there isn't a single segfault reported in his logfile. According to his logfile, it was folding fine. He has other issues going on.

[7im]

Regardless of the log contents (check your PM) pluto7777 also mentions...

I'm using the -advancedmethods flag but I'm not sure how that could lead to a segfault

v10 = segmentation fault, and the wrong flag syntax explains the other error. (-advancedmethods= invalid arg)


EDIT: tobit corrected me. v10 seg faults are typically immediate, upon client startup. So that's not it.

So it's either a bad work unit, or a computer hardware issue, typically a memory issue or overclocking (related). Ask a mod to see if anyone else can complete that WU. If not, bad WU. If the seg fault is isolated incident on this PC, also likely a bad WU. If it continues, time to start testing system components and checking system temps.

[pluto7777]

The correct flag is "-advmethods" not "-advancedmethods". As for the other issues, can't be of help, sorry.


~ Fireball0236

You are correct. It's enabled through configuration so I never need to actually type it in.

but there isn't a single segfault reported in his logfile. According to his logfile, it was folding fine. He has other issues going on.

Wow did you even look at it or was that an automated response?

...
Linux Ubuntu 10.10 kernel 2.6.35.

As you said, fah works just fine with all previous versions "running Ubuntu 8.4-9.10 with F@H client" Probably a good hint that something changed in v10 that is not compatible with FAH.

The segfault error is a known issue. 10.x versions of Ubuntu don't work with the current version of the v6 fah client. Go back to v9.x Ubuntu, or use one of the workarounds documented here in the forum. Search for segfault or NCSD.

I said F@H6.02 worked fine. It runs great without NCSD on 10.10 aside from no SMP work units being available.
I'll say it again F@H version 6.02 runs without error on Ubuntu 10.10 whereas version 6.29 isn't even usable without NCSD
Does 6.02 use a different gromacs version?

[bruce]

Does 6.02 use a different gromacs version?

You're talking about two different things. The client version and the FahCore version change virtually independently of each other. Gromacs is inside of a FahCore. The Pande Group can distribute a new version of a FahCore or can distribute an entirely new FahCore without ever changing the client version.

For example, FahCore_a4 runs a newer version of Gromacs than FahCore_78 but either one can run with a 6.02 client or with a 6.29 client -- provided that you have an OS that is configured so that that client version can run. On the other hand if a client cannot link with the version of the Linux library that you have, the client, itself, so no version of Gromacs can be used.

[pluto7777]

Does 6.02 use a different gromacs version?

You're talking about two different things. The client version and the FahCore version change virtually independently of each other. Gromacs is inside of a FahCore. The Pande Group can distribute a new version of a FahCore or can distribute an entirely new FahCore without ever changing the client version.

For example, FahCore_a4 runs a newer version of Gromacs than FahCore_78 but either one can run with a 6.02 client or with a 6.29 client -- provided that you have an OS that is configured so that that client version can run. On the other hand if a client cannot link with the version of the Linux library that you have, the client, itself, so no version of Gromacs can be used.

Let me rephrase the question then. Is FahCore_78 the same in 6.02 and 6.29?
I feel like I'm beating a dead horse here. I have removed NSCD and gone back to 6.02 for the time being.

[bruce]

Look at the date/time that FahCore_78 was downloaded and the version number that appears in FAHlog. Do you see any changes? When you reverted to 6.02 did it download a fresh version of FahCore_78 or are you using one that was backed up from the other configuration?

Deleting a copy of FahCore_78 might install a newer version but once again that has nothing to do with which client you're running. You might keep an old version for quite a while as long as (A) you don't delete it, and (B) you're not assigned a WU that needs a newer version than you have.

The Project that you're assigned is what determines which core you need and what minimum version is required, not the client.

[sortofageek]

Just as a follow-up, I checked the database again. Another folder completed this WU and returned it for full credit yesterday.