[FADCHAT 5/5/08] KK is to Lazy to start a new Thread

[nunyadam]

Maybe We should just start a new Thread when the old one hits 100 posts.

[Cmptr-Gy-Dv]

is this the new thread, I wasn't sure!

it must be the new thread nobody posted yet, at what post count do we consider the thread used,

why am I here alone, why am I talking to my self, what do I do if I answer,

do I believe what I say, should I tell myself to shut my pie hole,


does this thread make me look fat, can we have two threads in the same day,

can we just use somebody Else's thread or do we have to just use our own,

well with all that off my chest just remember spam on and don't take no for an answer,

[KarmaKiller]

Well at least everyone knows I'm lazy now..
So i don't have to say it over and over again anymore..

Dave, why are you talking to yourself. You know people consider you crazy when you start answering your own question out loud..

[CoonDawg]

Update to my problem:

A few threads ago I said I was getting an Error Message warning that there were long 1-4 interactions, having the program's progress freeze, and then give me EARLY_UNIT_END and start a new core. Someone responded, asking if it says it's been 3 hours since last checkpoint written.

Yeah, it does. This is exactly what it says:

[23:14:56] Completed 4750000 out of 5000000 steps (95 percent)
[23:23:35] Warning: long 1-4 interactions
[02:14:57] At least 3 hours since checkpoint written...
[02:16:57]
[02:16:57] Folding@home Core Shutdown: EARLY_UNIT_END
[02:16:57]
[02:16:57] Folding@home Core Shutdown: EARLY_UNIT_END
[02:17:05] CoreStatus = 7B (123)
[02:17:05] Client-core communications error: ERROR 0x7b
[02:17:05] Deleting current work unit & continuing...
[02:19:11] - Preparing to get new work unit...
[02:19:11] + Attempting to get work packet
[02:19:11] - Connecting to assignment server
[02:19:12] - Successful: assigned to (171.64.65.64).
[02:19:12] + News From Folding@Home: Welcome to Folding@Home
[02:19:12] Loaded queue successfully.
[02:19:16] + Closed connections

Also, it is always at 95 percent. This has happened at least 3 times, possible four.

[engracio]

Originally Posted by CoonDawg

Update to my problem:

A few threads ago I said I was getting an Error Message warning that there were long 1-4 interactions, having the program's progress freeze, and then give me EARLY_UNIT_END and start a new core. Someone responded, asking if it says it's been 3 hours since last checkpoint written.

Yeah, it does. This is exactly what it says:

[23:14:56] Completed 4750000 out of 5000000 steps (95 percent)
[23:23:35] Warning: long 1-4 interactions
[02:14:57] At least 3 hours since checkpoint written...
[02:16:57]
[02:16:57] Folding@home Core Shutdown: EARLY_UNIT_END
[02:16:57]
[02:16:57] Folding@home Core Shutdown: EARLY_UNIT_END
[02:17:05] CoreStatus = 7B (123)
[02:17:05] Client-core communications error: ERROR 0x7b
[02:17:05] Deleting current work unit & continuing...
[02:19:11] - Preparing to get new work unit...
[02:19:11] + Attempting to get work packet
[02:19:11] - Connecting to assignment server
[02:19:12] - Successful: assigned to (171.64.65.64).
[02:19:12] + News From Folding@Home: Welcome to Folding@Home
[02:19:12] Loaded queue successfully.
[02:19:16] + Closed connections

Also, it is always at 95 percent. This has happened at least 3 times, possible four.

I asked you that dawg cuz it also happened to me. It dumped that wu and grabbed a different wu series and as far as I know it has not done that anymore. As i have said before if you know the box is stable, more than likely its the wu being given out by Stanford. Keep an eye on your log file to see any similarities

[KarmaKiller]

Hi guys!
A couple of thing I wanted to add, as a possible fix.
1. Go into the advanced option of F@H, and there is a option for selecting how often it saves checkpoints. I myself always put it on the most frequent, which is 3 mins. Might check/change that and see if it helps.
2. Also in advanced options, there is a option for getting work units without deadlines, you might check that also..

I had my Quaddy box restart over night, not really sure why. I have automatic updates set not to install till I tell it too. My OC has been 100% stable on folding so far, so I really don't think that's it. Not really sure why, but it's going again, and already dumped a WU that started at 5:30am...

[engracio]

Last I heard F@H have not been handing out timeless wu lately and they don't know when it would again. Smaller checkpoint between saves are good especially for those machines rebooting a lot. On my Pentium D 945 running smp client with the default 15min between checkpoints it would trigger 3 checkpoints before going to the next step. However you feel like doing it.

As far as coondawg's early_end wu I think it was just the wu/client. If it happens more then it could be the box.

[KarmaKiller]

I just glanced over at the dually system, and it seems that it quit the WU at 17%, and is trying to send results.
The even worse thing is it's saying, "Could not send HTTP results to server" and "Failed to connect to work server."

It was just running fine an hour ago...

[2monsters]

Originally Posted by KarmaKiller

I just glanced over at the dually system, and it seems that it quit the WU at 17%, and is trying to send results.
The even worse thing is it's saying, "Could not send HTTP results to server" and "Failed to connect to work server."

It was just running fine an hour ago...

I thought it was just me that has that problem
I find that my 2 cows that i have hardwired to the router rarely dump wu's, but the 2 wireless cows always have problems sending results, or dumping wu's

[KarmaKiller]

They are both hard wired..