171.64.65.56 not responding

[kasson]

I think NMJ may mean no more jobs--the server is a bit low on jobs at the moment. We're working on a couple things related to this server right now (hard to expand jobs immediately because some of the storage arrays are pretty full--we're trying to shift data around).

[314159]

Thank you for the explanation.

I must commend you on the stablity of those servers assigned under your name Dr. Kasson.
I suspect that keeping them like this is a real p.i.t.a, - especially during the Holidays.
We all appreciate your dedication. THANK YOU!

John

P.S. I have had five new WUs assigned from this server since my post.
NMJ "may" not mean what we suspect - and also the blue has disappeared from the column in question.

[kasson]

If it does indeed mean "no more jobs," this isn't a terminal condition. The AS keeps talking to the work servers to see how many jobs they have, and as work units come back in, more jobs become available. When I checked the server this morning, we were somewhat low, but this server typically gets a lot of WU returns. Thanks for your patience!

[codysluder]

I think that one possible issue is that serverstat is a periodic snapshot of the server condition and that condition can change much more rapidly than the web page. A server that was out of jobs at one moment can be low on jobs (but not out) within a minute or so.

I'll second John's comment: Thanks for your attentiveness during the holidays, Kasson.

[314159]

Hi codysluder,

I agree with your comment concerning the update of server condition(s).

In this case and all others, I survey the status over at least 3 update cycles before generating any posts.
Since most of my WUs are coming from "good old xx.56", I had watched this one for about two hours last evening - mostly out of curiosity, since I continued to successfully send and receive WUs.

It went into reject first (for about an hour), re-activated, and in the update following the re-activation, "blued out" the NMJ data column.

My current suspicion, on which I stand ready to be corrected, is that the blue NMJ column is automatically generated when the WU Available data remains in the bold black condition for some unknown period - perhaps with a reject condition variable thrown in for good measure.

Fold on!

John

[314159]

This server is in REJECT MODE once again.

Please help!

Thanks,

John

[Cajun_Don]

This server is in REJECT MODE once again.

Please help!

Thanks,

John

Folding@Home server status
Report initiated on Sun Jan 4 20:30:21 PST 2009.

171.64.65.56 SMP vspg4 kasson full Reject 4.83 53 1 17883 2391 0 1.51 132 132 5856146 0 1 1 171.64.122.86 171.67.108.25

I have 2 WUs waiting to be uploaded.

[VijayPande]

Should be resolved shortly.

[314159]

Server is not pingable.
Looks overloaded but operational on current server stats page (the last time I looked).

All my Linux machines are being assigned to this server (and NO others) and I am getting nothing but "503's".

All completed WUs from this server are sitting queued.

Help!

Thanks!

John

Edit 0435 EST:
Several completed WUs have been sent to the "collection server".
Collection server has NO record of the WUs.
I am already facing excessive bandwidth issues with my ISP and this makes things considerably worse. <-- "sad" not "mad"

[Mortlake]

503's here as well , thankfully only one machine at the moment - 2.5 hours until the next Linux box completes .

[314159]

Hi Mortlake,

It's a pleasure to meet you! & also good to know that I am not the only one with this problem.
Thanks for the reassuring post!

Unfortunately, I have a quite large "farm" and most of the remaining dualies have xx.56 WUs completing within the next several hours.

Luckily, the 12 Quads are not having problems too!

Fold on and we'll wait for the good folks from the PG to wake up and fix things.
I guess that I'll just retire for some "beauty sleep" (I need it desperately)

John

[toTOW]

Server is operational, but a bit overloaded with a netload of 150 ...

[alexopth69]

503 here too

[314159]

Server is operational, but a bit overloaded with a netload of 150 ...

It is now 0948 EST.
I have still not been able to send the completed WUs, nor have I been able to connect to another server for new work.

With all due respects, II do not call that "functional".

The netload has remained at 150 for the past 7 hours or so.

Someone modified the criteria for this server and it has created a real mess.

Please help!

John

[Mortlake]

I managed to get some more work by stopping/starting the client , and getting routed to another server , but still cannot send the outstanding result , luckily my other machines seem to have missed the problem .