Hashtopus - distributed solution

[sharkchaser]

I have been tinkering with Hashtopus on Amazon's EC2 service using Amazon's flavor of linux. I have the lamp stack working fine, and after a good deal of tinkering, I have been able to get an Agent virtual machine working complete with cuda environment and working mono. After this small bit of success, I created an image(AMI) of my instance so that I could deploy multiple agents at one time. I started up two of them. The first started up and I executed hashtopus.exe. The agent was shown in the agent list. On the second machine, I downloaded the hashtopus.exe from the server, gave it a new token, and it downloaded the cudahashcat binaries and looked ok. When I switched back over to the first instance deployed, I had this output:

Hashtopus 0.8.8a
Registering to server...Enter registration voucher: fBI6wn8W
OK.
Logging in to server...OK.
Loading task...failed: No active tasks.
Waiting for next assignment...
Loading task...failed: No active tasks.
Loading task...failed: No active tasks.
Loading task...failed: No active tasks.
Could not download hashcat: Access token invalid.

Now the second agent shows up in the agent list, but not the first. Each instance has a different ip address, so that isn't the problem. Is there some unique identified that the server uses to identify the agents that I am unaware of?

Interestingly enough, no matter which of the agents/servers is shown in the list, it shows a previously executed test session in the chunk list. I'm guessing there is some identifier that has to be changed between each vm.

Thank you for your help.