Surveill@Home

http://surveill.dei.uc.pt/surveill/index.php

Surveill@Home is a research project that uses Internet-connected computers to conduct end-to-end fine-grained monitoring of web sites. The aim of the project is to deploy a large infrastructure to support thousands of probes monitoring the Internet.
Each probe repeatedly performs a pre-defined set of web transactions on web-sites, accessing each site about 4 times per hour.
The proposed approach allows us to obtain important results on end-user visible failures and performance statics, from several thousands view points spread throughout the Internet.
With the help of the volunteer community we will achieve this ambitious goal.
We are welcoming BOINC users who want to participate in our initial monitoring effort.
This is a "non-CPU" intensive project.

It pays 100 credits per day per host and will use a total of 30 seconds of CPU time per day. That's the equivalent of 288,000 credits per day at 100% CPU.

FYI, there currently there is a problem with hosts with ATI GPUs. They can't attach or get tasks. I am sure this will get fixed shortly.

The good news is that they have apps for win, linux, and osx.

Edit: ....aaaaand we broke it. ;)

ok who killed the website? wont come up:(

Back in action. I just signed up...

A golden chance for a early lead...:p

UPS - I spoke to soon!!


Got signede up alright....But every time my pc connects for WU´s it´s showing up as a new host!!!So far I got 13 crunchers listed under my account...:D

i signed up which 1 should i run? app 1 or app 2

Quote:

---

Originally Posted by BLUWOLF

i signed up which 1 should i run? app 1 or app 2

---

Have no idea. Getting no love from this project ATM...:(

Quote:

---

Originally Posted by Beerdrinker

Have no idea. Getting no love from this project ATM...:(

---

i had too update it twice to get it too work right

Quote:

---

Originally Posted by BLUWOLF

i signed up which 1 should i run? app 1 or app 2

---

I really don't think it matters. It seems to be a default of the new servers that nobody bothers to disable.

It's working again. Still only for non-ATI machines.

FWIW, with alpha projects, I always select all sub-projects. You can never tell which will be issuing work. Of course, you are taking a risk with any new/alpha project. So go in knowing that you will likely have crunching time wasted or lost, credits could be reset or never exported, or it could even mess with the other sustaining projects you are also crunching. Expect things go wrong, and credit loss.

Quote:

---

Originally Posted by zombie67

It's working again. Still only for non-ATI machines.

FWIW, with alpha projects, I always select all sub-projects. You can never tell which will be issuing work. Of course, you are taking a risk with any new/alpha project. So go in knowing that you will likely have crunching time wasted or lost, credits could be reset or never exported, or it could even mess with the other sustaining projects you are also crunching. Expect things go wrong, and credit loss.

---

With that in mind, wouldn't it be worth it to run alphas in a VM? So if it crashes, or does something very bad, then no harm to your whole system?

Account creation Dissabled. :(

Quote:

---

Originally Posted by Crazybob

Account creation Dissabled. :(

---

There site is really slow. My guess is that either the server isn't big enough or else it uses too much network bandwidth.

They claim they are limiting it because of DOS concerns (see below).

But the real question: Did everyone get their account created while it was still open? I am SURE everyone did, after this was discussed ad nausea, and very recently too! RIGHT?!


This is the news post:

Quote:

---

New registrations are temporarily closed
Hi Everyone,

The main goal of the project is to conduct end-to-end fine-grained monitoring of web sites. These web sites are monitored from different point-of-view (our host/network) and each WU contains a pre-defined set of web transactions.

Your clients doesn’t get WUs because currently Surveill@Home is limiting the number of WUs in order to limit bandwidth demanding and the possibility of using BOINC to recruit and deploy a machine base to launch denial of service style web attacks.

In the next days we will speed up WUs generation based on WUs processed and host locations.

I'll temporarily stop new registrations.

Thank you for your suggestions and comments.

Best regards,

Carlos Vaz

---

Did create account alrigth...Just waiting for them to fix the Ati-host issue...

I signed up for an account but only got a couple of wu's then nothing. Still waiting.

Quote:

---

Originally Posted by Beerdrinker

Did create account alrigth...Just waiting for them to fix the Ati-host issue...

---

The ATI host problem was corrected yesterday. ;)

Quote:

---

Originally Posted by DrBob

The ATI host problem was corrected yesterday. ;)

---

Alrigth then!...I am attaching now....Will see if it works..:)


EDIT: It did work!!! I got 2 WU´s rigth away - and I am now doing work for SETI.USA....!

Not a lot of credit, but I notice that I am getting what seems like a lot of work according to the web site. Almost 200 wu's so far.

I have noticed two problems running this project, and I am looking for confirmation from teammates.

1) It seems to hammer the network to the point where the "can't connect to the network" pop-up happens frequently. This has been confirmed by others on the project forum.

2) On my windows machines (but not my macs), something keeps killing the boinc client. The manager is still running, but can't connect to the localhost. CPU usage is zero. Check the processes, and the BOINC client is not running. It happens about once a day across all my windows machines. This started when I started running this project. So I have suspended this project on all my windows machines.

Since suspending, both 1 and 2 have stopped.

Is anyone else seeing #2?

Quote:

---

Originally Posted by zombie67

I have noticed two problems running this project, and I am looking for confirmation from teammates.

1) It seems to hammer the network to the point where the "can't connect to the network" pop-up happens frequently. This has been confirmed by others on the project forum.

2) On my windows machines (but not my macs), something keeps killing the boinc client. The manager is still running, but can't connect to the localhost. CPU usage is zero. Check the processes, and the BOINC client is not running. It happens about once a day across all my windows machines. This started when I started running this project. So I have suspended this project on all my windows machines.

Since suspending, both 1 and 2 have stopped.

Is anyone else seeing #2?

---

Yeh, I can confirm that. When I could not connect, I checked Task Manager and it was the project's WU that was taking all my 8Gb of RAM or close to it. The strange part is that it does not happen on all of my machines yet they are identical in build.

Quote:

---

Originally Posted by zombie67

I have noticed two problems running this project, and I am looking for confirmation from teammates.

1) It seems to hammer the network to the point where the "can't connect to the network" pop-up happens frequently. This has been confirmed by others on the project forum.

2) On my windows machines (but not my macs), something keeps killing the boinc client. The manager is still running, but can't connect to the localhost. CPU usage is zero. Check the processes, and the BOINC client is not running. It happens about once a day across all my windows machines. This started when I started running this project. So I have suspended this project on all my windows machines.

Since suspending, both 1 and 2 have stopped.

Is anyone else seeing #2?

---

Haven't noticed either problem with Surveill but will keep a closer eye on my machines and try to confirm.
I have noticed your #2 problem on one of my Win32 boxes, the culprit turned out to be FreeHal, since suspending FreeHall on that machine the problem has not re-occurred.

Quote:

---

Originally Posted by Cruncher Pete

Yeh, I can confirm that. When I could not connect, I checked Task Manager and it was the project's WU that was taking all my 8Gb of RAM or close to it. The strange part is that it does not happen on all of my machines yet they are identical in build.

---

Thanks. Could you please follow up to my post on their forum? I would like them to know it's not just me.

Quote:

---

Originally Posted by DrBob

Haven't noticed either problem with Surveill but will keep a closer eye on my machines and try to confirm.
I have noticed your #2 problem on one of my Win32 boxes, the culprit turned out to be FreeHal, since suspending FreeHall on that machine the problem has not re-occurred.

---

Hmm. I am running Freehal too, but that is not causing me any problems. It happens only when I turn on surveill.

I still have not been able to attach. :(

Quote:

---

Originally Posted by DrBob

Haven't noticed either problem with Surveill but will keep a closer eye on my machines and try to confirm.
I have noticed your #2 problem on one of my Win32 boxes, the culprit turned out to be FreeHal, since suspending FreeHall on that machine the problem has not re-occurred.

---

Quote:

---

Originally Posted by zombie67

Thanks. Could you please follow up to my post on their forum? I would like them to know it's not just me.

---

Quote:

---

Originally Posted by zombie67

Hmm. I am running Freehal too, but that is not causing me any problems. It happens only when I turn on surveill.

---

Maybe it is related to BM version?

Quote:

---

Originally Posted by Fire$torm

Maybe it is related to BM version?

---

FWIW, I am running 6.10.58.

Quote:

---

Originally Posted by zombie67

FWIW, I am running 6.10.58.

---

6.11.6

I'm running 6.12.33 without any problems running Freehal, wuprop, and surveill.

Quote:

---

Originally Posted by c303a

I'm running 6.12.33 without any problems running Freehal, wuprop, and surveill.

---

ditto for me.

Quote:

---

Originally Posted by zombie67

FWIW, I am running 6.10.58.

---

Quote:

---

Originally Posted by DrBob

6.11.6

---

Quote:

---

Originally Posted by c303a

I'm running 6.12.33 without any problems running Freehal, wuprop, and surveill.

---

OK, like zombie I'm using 6.10.58 on all my systems. I have not done surveil but with FH & WUProp I have never run into Zombie's network problem within BOINC. I have seen something similar but it is related to Win7 on my primary desktop when RAM utilization (It has only 3GBs) is upwards of 80%. That is because of apps not related to BOINC.

Still cannot attach. :(

Quote:

---

Originally Posted by denim

Still cannot attach. :(

---

Still can't complete a valid task, a very unusual problem for me.

Can the RSS please be turned on for this project?

http://surveill.dei.uc.pt/surveill/f...read.php?id=30

Quote:

---

Message 163 - Posted: 16 Aug 2011 | 18:46:50 UTC
Hi,

A new version of the crawler application (v.1.05) has been released today.

Best regards,

Carlos Vaz

---

Maybe that will fix the problem where it kills BOINC on windows machines.

I'm getting computation errors now on all my machines. Stopped running this for now.