Surveill just updated their clients and it carries a new feature
It appears to check how many clients are currently running on your LAN
(NB - I think they probably do this on the server by checking which clients were downloaded to hosts on the same ip address, as opposed to 'sniffing' your LAN packets, which might be a bit nefarious)
You may see this in your BOINC manager log
"Wed 17 Aug 2011 12:37:50 EST surveill@home Message from server: Not sending work - max number of probes in your network exceeded"
followed by
"Wed 17 Aug 2011 12:38:27 EST BURP Message from server: This computer has reached a limit on tasks in progress"
Smart move Surveill
Last edited by AMDave; 08-17-2011 at 02:48 AM.
. . . . . ___
. . . . . . .\___/\______
. . . . . . . \__AMD___\\__
---------------------------------------------
That's a shame for those running big pharms. I guess a workaround is to split the pharm over several ISPs. Luckily I have three at my disposal.
I am not seeing a problem here at all. BUt, I only have two systems operating at a time!
Challenge me, or correct me, but don't ask me to die quietly.
…Pursuit is always hard, capturing is really not the focus, it’s the hunt ...
It looks like they were also trying to address the BOINC Manager internet connection popup message on Windows at the same time:
http://surveill.dei.uc.pt/surveill/f....php?id=24#125
Funny thing is that since they limited the number of concurrent cliant apps on the same network I just cut them all back to my Linux boxes.
So can someone else confirm that they are running the v1.05 client app and that the pop-up message has stopped happening?
. . . . . ___
. . . . . . .\___/\______
. . . . . . . \__AMD___\\__
---------------------------------------------
Just checked my boxes and it looks like you have the 'sweet spot' at 2 instances running.
I appear to be down to only 2 running at a time.
That means I can shut down the VM on the other box and try to put BURP on it too!
[EDIT -
incorrect assumption - it might be only 1 I already shut down that VM last night. I forgot
Blast.
I have zero running and all saying there are too many.
I'll need to figure this out.
Allowing work on a windows machine.
1 windows machine just got one right away.
Maybe a Linux client problem.
I'll try detaching all the windows clients and see if Linux picks one up somewhere...later
- EDIT]
[EDIT2 -
forgot about my power outage. duh
One linux box still had a WU that was not returned and showed "Aborted. Not started by deadline"
I guess that one was blocking the rest.
- EDIT2]
Last edited by AMDave; 08-17-2011 at 04:21 AM.
. . . . . ___
. . . . . . .\___/\______
. . . . . . . \__AMD___\\__
---------------------------------------------
Follow-up:
The pop-up message in windows appears to be gone.
My linux machines do get work.
It looks like only one network probe runs at a time now.
. . . . . ___
. . . . . . .\___/\______
. . . . . . . \__AMD___\\__
---------------------------------------------
Hmm. you guys are all getting much better results than me and I don't know why.
Anyone have any clues?
Are you getting multiple WUs running concurrently on the same network?
Last edited by AMDave; 08-20-2011 at 02:14 AM.
. . . . . ___
. . . . . . .\___/\______
. . . . . . . \__AMD___\\__
---------------------------------------------
It's ok. You can play your cards close, if you like :P
The client is back to running multiple instances on the same network.
I'm allowing new work on some windows machines again now the popup issue is fixed.
It was annoying the family so I had to disable it on their machines.
I'm coming back atcha.
. . . . . ___
. . . . . . .\___/\______
. . . . . . . \__AMD___\\__
---------------------------------------------