LHC@home

Hi,

we have a univerity computer lab with about 120 computer and we would like to join LHC@home in the time the rooms are unused.

We use OpenSLX as a streaming virtualisation so for that we have a basic image. After a long time we configured, with help from some BOINC guys, to change the hostname to an unique one and register automaticaly the LHC.

Now, after testing on 5 PCs, we are running a test with about 20 PCs and run into a problem. Some computer are running the same tasks and are not showing in the computer list of our account.

Is there a limation for registations accoring to a time e.g. 5 PCs in 30min or is there another problem?

All PCs have own IPv4 Adresses, a unique MAC and a unique hostname. BOINC was fresh installed and not startet in the image. So each PC should be unique.

Some ideas? We are from Germany - so if someone like we can skype because our project here is a bit confusing.

Thanks!

We are following this up. Many thanks for deciding to join
LHC@home SixTrack. Eric.

Hi,

we have a univerity computer lab with about 120 computer and we would like to join LHC@home in the time the rooms are unused.

We use OpenSLX as a streaming virtualisation so for that we have a basic image. After a long time we configured, with help from some BOINC guys, to change the hostname to an unique one and register automaticaly the LHC.

Now, after testing on 5 PCs, we are running a test with about 20 PCs and run into a problem. Some computer are running the same tasks and are not showing in the computer list of our account.

Is there a limation for registations accoring to a time e.g. 5 PCs in 30min or is there another problem?

All PCs have own IPv4 Adresses, a unique MAC and a unique hostname. BOINC was fresh installed and not startet in the image. So each PC should be unique.

Some ideas? We are from Germany - so if someone like we can skype because our project here is a bit confusing.

Thanks!

---

This covers how to automate:

http://boinc.berkeley.edu/wiki/Boinccmd_tool

I guess if there is a limit, you can test various delays.

Now, after testing on 5 PCs, we are running a test with about 20 PCs and run into a problem. Some computer are running the same tasks and are not showing in the computer list of our account.

Your account shows 83 registered computers

---

Supporting BOINC, a great concept !

Now 85 running and all seem to have tasks running.

15 pending and I see one Valid now

---

Volunteer Mad Scientist For Life

Thank you for you feedback!

We gave it a try with two rooms ( 85 PCs ) over night. I am amazed that everything is right now. But i am confused why it took so long?! Yesterday in the evening we had about 12 active PCs but 85 PCs online and connected and just a few tasks. But all PCs were running some tasks.

Is there a management server or sth. like this which checks the PCs e.g. every hour and check if same tasks are running on different PCs and reassign the tasks?

I am glad that it is running now but i can not explain why we need a while everything runs right.

We have two other rooms we will join today ( same procedure as yesterday ) so i will report!

Thanks & Greetings

Okay - now we joined 16 PCs - all are working and running tasks - but, however, some running the same tasks. Some ideas here? We will keep it running to check ...

Edit: Just two from the news PCs are listed under active PCs

Is there a way to get the number of active PCs? Like you guys did it except from counting the list?

There is many management options Boinccmd, RPC clients and Boinc Tasks.

There is also account managers where you can add remove project globally.


You can see the computer count and stats on site like Boincstats.


Many options, to fit your needs.

Many of the tasks have similar names and there is duplication of tasks to ensure there is the correct results.

Welcome, FritzBox, et al,
You contribution will be greatly appreciated.
On your account page there is a link to all your attached Computers on this account. There I can see you have now attached 118 hosts WOW 8¬)

Each task is sent to at least 2 hosts so the results are cross-checked, and sometimes a 3rd and 4th if there is a discrepancy in the results so with that number of hosts it may be likely that you might get the same tasks sent to more than one host. However, the name of each task will finish with boincxxxxx_0, _1, _2, _3 etc to show that, even though it is the exact same task, the system knows that they are going to different hosts. (If EVERY bit of the task name is the same, then there is a problem, but hopefully you are able to distinguish them from the subtle difference outlined above.)

Thank you Ray Murray for the explanation ;) But i am sure we had duplicated tasks in the beginning because we compared the whole task name and it was the same.

We keep running but we need to do a restart after the weekend - maybe now it is fine because als PCs are registert in the database. We will see - i will keep you informed.