No work for newly attached machines?
log in

Advanced search

Message boards : Number crunching : No work for newly attached machines?

Author Message
Profile Beyond
Avatar
Send message
Joined: 2 Nov 16
Posts: 24
Credit: 5,367,881
RAC: 24,917
United States
Message 1206 - Posted: 30 Nov 2017, 22:00:45 UTC

One of my teammates is reporting:

"Having a heck of a time getting any work on the machines I added here, they request new tasks and event log just says the request was completed, got 0 new tasks. No error, no out of work, just nothing. Machines that were attached several weeks ago seem to work fine."

What's going on?

Profile valterc
Project administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 320
Credit: 16,272,871
RAC: 4,766
Italy
Message 1208 - Posted: 1 Dec 2017, 10:37:29 UTC - in response to Message 1206.
Last modified: 1 Dec 2017, 10:56:53 UTC

One of my teammates is reporting:

"Having a heck of a time getting any work on the machines I added here, they request new tasks and event log just says the request was completed, got 0 new tasks. No error, no out of work, just nothing. Machines that were attached several weeks ago seem to work fine."

What's going on?

We didn't change anything recently. We still have the issue of the work generator not being able to make enough workunits to satisfy user's requests, so sometime there is no work available. Anyway, you may check the newest attached computers (hostid >= 19874) and see that they were able to download some work.

If you give me the hostid of one of the computers you are talking about I may check the server log and see if there is something strange.

[edit] looking at the scheduler log I found a lot of lines like
Bad authenticator '1140_42646555bcaff2fadd
I really don't know what it is....

Profile valterc
Project administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 320
Credit: 16,272,871
RAC: 4,766
Italy
Message 1209 - Posted: 1 Dec 2017, 10:59:26 UTC - in response to Message 1208.
Last modified: 1 Dec 2017, 11:00:59 UTC

looking at the scheduler log I found a lot of lines like
Bad authenticator '1140_42646555bcaff2fadd
I really don't know what it is....

... But looking at the server source code (handle_request.cpp) I noticed that this is something related with the 'weak authentication key' (the one used by the gridcoin pools, I guess....)

BGB [gridcoin.us]
Send message
Joined: 1 Feb 17
Posts: 1
Credit: 3,104,842
RAC: 0
United States
Message 1210 - Posted: 2 Dec 2017, 14:04:35 UTC - in response to Message 1209.

Hi,

The weak key you see in the log is not from the pool. You can use the first part of the weak key as the userid to determine the owner. Therefore:

http://gene.disi.unitn.it/test/show_user.php?userid=1140

Thanks,

Brian...
grcpool dev


Post to thread

Message boards : Number crunching : No work for newly attached machines?


Main page · Your account · Message boards


Copyright © 2017 CNR-TN & UniTN