1) Message boards : Sixtrack Application : Can't upload sixtrack (Message 5355)
Posted 12 Feb 2018 by nikogianna
Post:
There is currently an issue with the file server and the results do not upload. We are investigating. Also, note that these Sixtrack tasks are submitted through HTCondor and are test ones, meaning they are the same Sixtrack workunit submitted again and again as we are currently testing the full chain of submission from HTCondor to BOINC. You can go ahead and abort them. Lastly the assimilator and validator are actually running but not being shown in the server status page. Will fix.
2) Message boards : News : Development project "face lift" (Message 5201)
Posted 14 Oct 2017 by nikogianna
Post:
No, in production the numbers are much higher so the noise would be too much. If there is enough interest we could develop a paginated page and show every cpu.
3) Message boards : News : Development project "face lift" (Message 5199)
Posted 13 Oct 2017 by nikogianna
Post:
It is actually sorted by GFLOPS/core.
4) Message boards : News : Development project "face lift" (Message 5197)
Posted 13 Oct 2017 by nikogianna
Post:
It should be working now. It was not actually broken before but it was set to display only CPUs with more than 10 active hosts using them. Since the numbers here are not as high as on the prod server nothing was displaying. It is now set to display even CPUs with one active host.

I am not sure I understand the dropdown menu suggestion. Could you please clarify?

Thanks for taking the time to make suggestions. They are very appreciated.

Cheers,
Nikolas
5) Message boards : News : Server Upgrade (Message 5187)
Posted 11 Oct 2017 by nikogianna
Post:
The LeaderBoard is a separator and is not intended to be clickable. As for the Billionaires Club and the MCPlots, they have been added under Billionaires Club and Theory Jobs buttons respectively.

Thank you for your suggestions.
6) Message boards : News : Development project "face lift" (Message 5186)
Posted 11 Oct 2017 by nikogianna
Post:
The development project has been upgraded to use the latest BOINC upstream code. Thus, it now has a new look based on Bootstrap in accordance with other projects like SETI@home.
Your feedback and suggestions are, as always, appreciated.
7) Message boards : News : Server Upgrade (Message 5182)
Posted 9 Oct 2017 by nikogianna
Post:
The upgrade is more or less done now. Please post here any suggestions, feedback, wishes and criticisms.

Thank you for your help and interest.

Cheers,
Nikolas
8) Message boards : Number crunching : Another Problem (Message 5054)
Posted 21 Jul 2017 by nikogianna
Post:
Will have to investigate what the behaviour of the scheduler is when a host is inactive for more than 30 days (there seems to be a pattern here). Normally it should not fail to update the DB record for last contact time, no matter when last contact was made. There might even be a connection with the statistics export failing since the beginning of June.
9) Message boards : Number crunching : Another Problem (Message 5050)
Posted 20 Jul 2017 by nikogianna
Post:
Hello, I can confirm that the database record for the last time the host (384) contacted the server is 6 Jun. Could you please try updating the project from the BOINC manager so that we can test if manually issuing an RPC (by the update) will record in the database?
10) Message boards : Number crunching : issue of the day (Message 5021)
Posted 27 Jun 2017 by nikogianna
Post:
This is related to some tests we ran on the scheduler and at some point tasks that use the MAX_CPUS were sent. Please delete these tasks as they will not run. New tasks should be sent with the correct preferences.

Sorry for the inconvenience.
11) Message boards : News : CGI testing (Message 5014)
Posted 23 Jun 2017 by nikogianna
Post:
We are trying to improve the job limiter that is currently active, so you might experience some instabilities for the rest of the day.

Thank you for your understanding.
12) Message boards : Theory Application : New version v3.07 (Message 4999)
Posted 14 Jun 2017 by nikogianna
Post:
Vboxwrapper is what cleans up after the machine is shut down and it doesn't matter what version the vdi is.
13) Message boards : News : Dev server was down today (Message 4950)
Posted 28 May 2017 by nikogianna
Post:
Could you please try resetting the dev project?
14) Message boards : Theory Application : New version v3.03 (Message 4948)
Posted 28 May 2017 by nikogianna
Post:
The problem with starting from 0% after suspending and restarting has the same root cause that the web application port problem has. It is all due to a change we made to the checkpointing feature of the wrapper that we don't use. This has been fixed on the 3.04 version and neither the web port nor the restarting should be broken.
15) Message boards : Theory Application : New version v3.04 (Message 4932)
Posted 26 May 2017 by nikogianna
Post:
A new version of the vboxwrapper has been released, addressing the web application port problem. Please, report any problems.
16) Message boards : Theory Application : New version v3.03 (Message 4918)
Posted 24 May 2017 by nikogianna
Post:
Does the same apply to the remote desktop port?
17) Message boards : News : Screenshot display (Message 4872)
Posted 28 Apr 2017 by nikogianna
Post:
We were going with "setterm -blank 0", but it obviously wasn't working. Trying to understand why. Possibly not surviving reboots
18) Message boards : News : Screenshot display (Message 4869)
Posted 27 Apr 2017 by nikogianna
Post:
The screen is blanking indeed. I will look into it. As a temporary workaround you could add a keyboard space (0x39) input to your script right before the screenshot to "wake" the VM. That is what the vboxwrapper is currently doing.
19) Message boards : News : Screenshot display (Message 4866)
Posted 26 Apr 2017 by nikogianna
Post:
Sorry about the link. Here is one that should be working:

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=323055

About the screen blanking, it is actually disabled for Theory and it will be for the rest of the apps as soon as we feel satisfied with the way Theory works.

About the screen capturing, the most important and crucial part of the VM's life is the moment a task errors out, so that is what we are trying to capture. Periodical screen capturing could be done but it would have to be on an ad hoc basis (e.g. using a script).
20) Message boards : News : Screenshot display (Message 4861)
Posted 26 Apr 2017 by nikogianna
Post:
It seems that the actual state of the VM was the one displayed by the screenshot since as far as I can see it is working for other cases e.g.

https://lhcathomedev.cern.ch/lhcathome-dev_ops/db_action.php?table=result&id=322790


Next 20


©2024 CERN