Admin Updates Discussion  |
Hello everyone,
This thread will be used to discuss posts made in Admin Updates.
Thanks,
Kevin
|
|
| Commenting on Recent Issues with the server |
Hello everyone,
I wanted to apologize for the recent server issues. The migration brought unforeseen challenges, particularly with DNS changes. As a newcomer to server management and BOINC projects, I've been on a steep learning curve to transition this project to a new server.
As mentioned in a previous post, and reiterated here, we have set up a temporary DNS entry for milkyway-new that now points to the server. The changes will take some time to become effective (I don't have a specific timeline, but I'm closely monitoring the process). This update will allow for downloading older work units linked to milkyway-new and uploading completed ones.
I'm immensely grateful to all the volunteers who have suggested fixes and assisted others with client-side issues. Your contributions have significantly accelerated problem-solving during this server migration. I can't thank you enough for your support.
To those who have voiced frustrations, I apologize for any shortcomings in my expertise. I recognize the value of the computing time you generously volunteer and understand your desire for acknowledgment of your contributions. I encourage you to continue sharing your concerns, as long as they are respectful. Destructive or derogatory comments don't contribute constructively to our project. We aim to foster a positive environment at MilkyWay@home for everyone passionate about science and distributed computing, free from unnecessary negativity.
One common concern has been the need for better communication. Despite my efforts to preemptively share updates, it appears more is needed. I would like to improve in this area. I'm considering regular updates (weekly, bi-weekly, or monthly) and would appreciate your thoughts on this. Please share your ideas in the comments on how I could improve communication.
On a related note, we are excited to announce that we're currently developing a new version of the n-body code. This upgrade will allow for the fitting of additional parameters, such as orbit parameters, along with other minor improvements. We anticipate implementing these changes in the coming weeks.
Additionally, we are making plans to reintroduce support for Mac users. More details will be provided as soon as we have further information.
Once again, I apologize for the recent issues with MilkyWay@home and am very thankful for your patience.
Best regards,
Kevin
|
|
| 12-digit factor of P2203 has now been found by the project... |
|
...438884 times
|
|
| Migrating MilkyWay@home to a New Server |
Hello everyone,
We are preparing to migrate MilkyWay@home to a new server on 1 November 2023 at 2 pm UTC. This new server has better hardware (specifically more memory), which we expect will improve the performance of the website and the rate at which you can get new workunits. We are forced to perform this migration at a fast pace due to RPI requiring that we update the server OS to ensure proper security.
We expect that this migration will take one day to complete. If it looks like the downtime will be longer than that, we will update you on our Facebook page. It is possible that the server might experience some unexpected behavior after this migration, but I will be closely monitoring the situation to resolve any issues as they may come up. In particular, I will be watching the message boards closely, and I will make a thread for people to report issues with the new server.
That being said, there were some issues with getting BOINC to recognize the binary up on the new server, so we had to increment the binary version from 1.82 to 1.83. I am not sure what this means for workunits that are awaiting validation after the switch, but I will do what I can to make sure everyone gets as much credit as possible for their work. Unfortunately, it is plausible that you may lose some credit due to the migration, which we apologize for.
I apologize for the short notice and thank you in advance for your patience as I try and make this switch as smooth as possible.
Thank you,
Kevin
|
|
| P2203:260000000 wu's (of 10000 trials each equiv.) processed! |
|
Thanks to all the users. Please keep crunching!
|
|
| Server Maintenance 6/28/2023 12 PM EDT (4 PM UTC) |
Hey Everyone,
I'll be shutting the server down for about an hour or two tomorrow at noon EDT (4 PM UTC) to take care of the loads of WUs stuck waiting for validation. They are from leftover Separation WUs trickling in after the project was shut off. Unfortunately I do not think that credit will be given out for these stuck WUs, as they were turned in after the project was shut down, and the validator is not running to give people credit.
N-body WUs will not be affected by this, and all credit will be assigned as per usual for N-body WUs.
Best,
Tom
|
|
| Server upgrade |
|
The LHC@home BOINC servers have been upgraded to the latest server release, 1.4.2.
|
|
| Seasons greetings |
Many thanks to all our volunteers for your contributions to LHC@home over the last year!
We in the LHC@home team wish you a Merry Christmas and restful holidays.
|
|
| Finish Up Your Work |
|
I'll be losing my "computer room" in my basement this week while water seepage mitigation is done. After that, the house goes on the market as I'll be relocating to a state with nicer climate with fewer corrupt politicians and lower taxes. The result is that the Collatz project will be down for some time. Please set your machines to get no new work because you likely won't be able to return the work before it times out. The work starts Wednesday so I have to have everything cleared out prior to that so it may be Monday or Tuesday when it gets shut down. Once I move, I don't know how reliable the broadband will be, but I'm hoping that since it will be fiber and not cable TV based, it will be decent. It should be faster and less expensive, but I can't predict when the Collatz project will be back online at this time.
|
|
| [all] status update |
|
to bad
|
|
| Account deletion enabled |
Deleting your Moo! Wrapper account is now possible. It can be requested from your Account page or by going directly to https://moowrap.net/delete_account_request.php page. Your account will be deleted automatically after email address* verification that tries to make sure you are you. Note that this process will permanently delete your account and you will lose access to it. There's no way to restore an account so please be sure before requesting deletion.
*I know email verification requirement can cause problems for some users that can't receive emails. This includes emails protected with the Outlook services because MS/Outlook never accepts any email from our project server. Even their support services is not able to help figure out why that is. So if you are affected with this (please also check your Junk email folder) you can either try to complain to your email service provider or, preferably, switch to some email service provider that works. For Example Google Mail should work. Note that changing your email address will mean you have to wait a week before account deletion is possible due to security reasons.
|
|
| Hello, all! |
Good morning!
As I take over for Josh, please bear with me. I am aware there are currently some issues out there. I will do my best to to support you all and this project.
I look forward to working with you all.
Best,
Olivia
|
|
| Albert@Home migration to AEI |
We are migrating the Albert@Home project to AEI (Uni of Hannover). The project will be temporarily shutdown during this time, on 2020-04-28 Users will not need to do anything with their clients. Thanks for your patience as we move ourselves. |
|
| New works generators |
In next 7-10 days i would like to make some change in generators so it could be problem with getting new WU.
Acctuall generators are making too much IOPS on disk on my serwer and making it's very unstable and less performance that they could be.
One generator (and i have four of them working 24/7 ) can generate 300-350 (or even have peak to 450-500) IOPS and killing server <- after that change i hope it's decrease to 25-50 IOPS
|
|
| DHE suspended |
Hello everyone,
Unfortunately we are having to suspend DHE until we secure funding. A big thanks to all of you who crunched for our project, the BOINC team, and a special thanks to those who volunteered with us in many ways.
All the best,
Michael
|
|
| Down for a while... |
|
We're configuring a new upload server that will have more capacity than the current one. (Solid state drives, for example). We're going to test it on beta first, of course, so we'll be down while the transition happens. I expect a day or two.
|
|
| This project is finally over. |
The inability of the project to provide sufficient number of WUs for everyone provokes major server overloads during the WU generation each two weeks. These overloads significantly complicate downloading/uploading of the work. Continuing the project will cause an unpleasant experience for the participants.
Considering that the power of BOINC is actually not required for this project since the project reached its goal in September 2017, I think this is a right moment to finally end XANSONS for COD.
I would like to thank everyone for helping the project all that time!
|
|
| Server maintenance |
During 2 weeks (Jan 30 - Feb 12) the server can be temporarily unavailable because of the maintenence.
Ближайшие 2 недели (с 30 января по 13 февраля) сервер может быть временно недоступен из-за технических работ.
|
|
| Paper in the proceedings of GRID'2018 |
|
A new paper has been published: 'Oleg Zaikin, Pavel Petrov and Ilya Kurochkin. Application of BOINC-based volunteer computing for comparison of the geoacoustic inversion algorithms efficiency // Selected Papers of the 8th International Conference on Distributed Computing and Grid-technologies in Science and Education. CEUR-WS. 2018. Vol. 2267. pp. 298-301'
|
|
| New detectors... |
|
After long time I will like to order from professional company a set of around 100-150 detectors...
What you think about it?
(I know, map doesn't work as Google change its policy, we will move to OSM in January...)
New detectors cost will be around 30-33 Euros as we not assemble it manually ourselves but order it from selected company...
Edit: My Patrone profile (where Poll is): https://www.patreon.com/krzyszp
|
|
