Page 1 of 1

171.64.65.105/171.67.108.142 Could't authent. AS response

Posted: Wed Aug 12, 2015 12:07 pm
by artoar_11
Old client - v.6.41r2 (GTX 460 + core_15).It worked well until this morning :)

Code: Select all

[06:03:12] + Attempting to get work packet
[06:03:12] Passkey found
[06:03:12] - Will indicate memory of 8168 MB
[06:03:12] Gpu type=3 species=20.
[06:03:12] - Connecting to assignment server
[06:03:12] Connecting to http://assign-GPU.stanford.edu:8080/
[06:03:13] Posted data.
[06:03:13] Initial: 0000; + Could not authenticate Assignment Server response
[06:03:13] Connecting to http://assign-GPU.stanford.edu:80/
[06:03:14] Posted data.
[06:03:14] Initial: 0000; + Could not authenticate Assignment Server 2 response
[06:03:14] + Couldn't get work instructions.
[06:03:14] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[06:04:53] ***** Got a SIGTERM signal (2)
[06:04:53] Killing all core threads

Re: 171.64.65.105/171.67.108.142 Could't authent. AS respons

Posted: Wed Aug 12, 2015 1:52 pm
by toTOW
Last time I had this issue (v6 Linux client), I had to upgrade to v7 to get work again ...

This error is probably the v6 version of this one reported many times in this thread : viewtopic.php?f=18&t=27962