128.143.231.201 bigadv out of work

[Grandpa_01]

I think the bigadv server may need a little attention or maybe not it has been out of bigadv work for the last 12 hrs. or so.

[Joe_H]

Email sent

[bcavnaugh]

I am Only Getting only Core GRO A3 P6096 now on both of my Rigs.

21:55:05:WARNING:WU01:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Empty work server assignment
21:55:06:WARNING:WU01:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Empty work server assignment
21:55:06:ERROR:WU01:FS00:Exception: Could not get an assignment

[snapshot]

There is an easy fix, request a kick it, I am sure some will kick it soon.

[PinHead]

Looks like there is a small bit of work out there, but now I'm getting authentication failures.

Code: Select all

[17:53:33] Initial: 0000; + Could not authenticate Assignment Server response
[17:53:33] Connecting to http://assign2.stanford.edu:80/
[17:53:37] Posted data.
[17:53:37] Initial: 0000; + Could not authenticate Assignment Server 2 response
[17:53:37] + Couldn't get work instructions.
[17:53:37] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[17:53:51] + Attempting to get work packet
[17:53:51] Passkey found
[17:53:51] - Will indicate memory of 16047 MB
[17:53:51] - Connecting to assignment server
[17:53:51] Connecting to http://assign.stanford.edu:8080/
[17:53:51] Posted data.
[17:53:51] Initial: 0000; + Could not authenticate Assignment Server response
[17:53:51] Connecting to http://assign2.stanford.edu:80/
[17:53:52] Posted data.
[17:53:52] Initial: 0000; + Could not authenticate Assignment Server 2 response
[17:53:52] + Couldn't get work instructions.

[Nathan_P]

2 of my rigs have managed to pick up an 8105 after a few A3 units but my third rig is still on standard SMP

[Grandpa_01]

My guess is Stanford did something to the server code at around 13:10 PST (1:10PM) on Friday November 21 the big advance server actually all the servers quit recording then, when the bigadv server / all the servers I checked started recording again 4hrs and 10 min latter it had gone from 310 WU's available to 2 WU's available. And has a few bigadv WU's on occasion ever since.

So I am assuming either someone at Stanford messed with the server code or they had a crash of some kind that changed things.

Code: Select all

Fri Nov 21 13:00:12 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.05	0	0		16294	2732	0	307	307	307	-	-	-	-	-	9	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Nov 21 13:10:14 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.07	0	0		16294	2732	0	310	310	310	-	-	-	-	-	1	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Nov 21 17:20:11 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.07	0	0		16294	2728	-1	2	2	2	-	-	-	-	-	3	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Nov 21 17:30:11 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.06	0	0		16294	2728	-1	3	3	3	-	-	-	-	-	6	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Nov 21 17:40:11 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.05	0	0		16294	2728	-1	6	6	6	-	-	-	-	-	8	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Nov 21 17:50:11 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.05	0	0		16294	2728	-1	1	1	1	-	-	-	-	-	10	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Nov 21 18:00:11 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.05	0	0		16294	2728	-1	0	0	0	-	-	-	-	-	10	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	
Fri Nov 21 18:10:11 PST 2014	128.143.231.201	pmks04	kasson	SMP	full	Accepting	1.05	0	0		16294	2728	0	3	3	3	-	-	-	-	-	2	0	-	-	1		-	0	1	L; L;	10, 10	6.33, 6.33	50, 50	10000, 10000	2800, 2800	-	24, 24	-	-	8080, 8080	

[kasson]

We've added some bigadv jobs (~200 as of this evening, likely more to come). Hopefully this will alleviate the shortage.

(I'm sure everyone remembers, but bigadv EOL is planned for Jan 31, 2015. We will do our best to keep jobs available until then, though.)