Migrating MilkyWay@home to a New Server
Message boards :
News :
Migrating MilkyWay@home to a New Server
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5
| Author | Message |
|---|---|
|
Send message Joined: 16 Dec 07 Posts: 37 Credit: 24,521,553 RAC: 4,884   
|
BAM (BOINCStats) has been getting Milkyway updates again since 14 - Nov. Kevin posted https://milkyway-new.cs.rpi.edu/milkyway/forum_thread.php?id=5051&postid=76610 saying as much in the Number Crunching Server Migration Thread. |
|
Send message Joined: 9 Nov 23 Posts: 1 Credit: 931,405 RAC: 7,373 
|
See that milkyway-new.cs.rpi.edu is not resolving to an IP? ;milkyway-new.cs.rpi.edu. IN A added line to hosts to map the milkyway.cs.rpi.edu to -new 128.113.126.54 milkyway-new.cs.rpi.edu And that allowed complete work unit to be uploaded. Don't know if a new update needs to be done?? |
 Kevin Roux Send message Joined: 9 Aug 22 Posts: 72 Credit: 1,230,287 RAC: 8,087   |
See that milkyway-new.cs.rpi.edu is not resolving to an IP? We have changed the DNS setting such that milkyway-new no longer exists and the url milkyway.cs.rpi.edu points directly to the server IP and is not longer a cname for the server. I am going through and changing everything on the server to reflect that change. |
mikey Send message Joined: 8 May 09 Posts: 3321 Credit: 520,650,942 RAC: 32,682    
|
See that milkyway-new.cs.rpi.edu is not resolving to an IP? So how do we return completed work now that the -new address which is where the 'new' client is pointing too? If we remove and reattach all of our work will be lost. |
|
Kevin Roux Send message Joined: 9 Aug 22 Posts: 72 Credit: 1,230,287 RAC: 8,087 |
So how do we return completed work now that the -new address which is where the 'new' client is pointing too? If we remove and reattach all of our work will be lost. I'm really sorry for all the headaches this DNS change has caused. I was advised to change the URL for the project to be milkyway and not milkyway-new since that would cause issues for all users. I did not realize how much this would affect. So again, I'm really sorry about this. I have been advised by a BOINC admin to add a DNS entry for milkyway-new which points to the same IP. This should allow for the download of WU's that sill want milkyway-new url and hopefully, report completed workunits that want to send to milkyway-new. This change might take a while to propagate (I was not given a timeline). |
|
Kevin Roux Send message Joined: 9 Aug 22 Posts: 72 Credit: 1,230,287 RAC: 8,087 |
So how do we return completed work now that the -new address which is where the 'new' client is pointing too? If we remove and reattach all of our work will be lost. I am now able to crunch WU's on my BOINC client. I believe the changes have propagated. |
|
HRFMguy Send message Joined: 12 Nov 21 Posts: 236 Credit: 575,038,236 RAC: 2,071 
|
I was just now able to upload about 250 WU's. And a lot of them had credits. A lot were also _0 tasks, so not expecting any wingman activity for a while. But I am getting this funkiness: Valid tasks for computer 981567 Next 20 State: All (678) · In progress (300) · Validation pending (0) · Validation inconclusive (219) · Valid (89) · Invalid (70) · Error (0) Task name: Warning: Attempt to read property "appid" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 83 Warning: Attempt to read property "platformid" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 84 Warning: Attempt to read property "user_friendly_name" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 85 Warning: Attempt to read property "version_num" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 86 Warning: Attempt to read property "version_num" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 86 Warning: Attempt to read property "plan_class" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 87 Warning: Attempt to read property "name" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 92 Warning: Attempt to read property "appid" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 83 Warning: Attempt to read property "platformid" on null in /home/boinc/boinc/milkyway/html/inc/result.inc on line 84 If i scroll down through the funk, the regular status display is there, and seems good. 
|
|
Send message Joined: 14 Aug 23 Posts: 1 Credit: 457,423 RAC: 0
|
So first we're told to update our clients to change to the -new address, now we're being told to change back to the original address. Wish someone would make up their mind what the address we're supposed to use should be. |
|
Kevin Roux Send message Joined: 9 Aug 22 Posts: 72 Credit: 1,230,287 RAC: 8,087 |
I was just now able to upload about 250 WU's. And a lot of them had credits. A lot were also _0 tasks, so not expecting any wingman activity for a while. But I am getting this funkiness: Another user also noted this issue. " These problems occur only when certain "older" tasks are shown in the selected table. E.g. tasks which were downloaded at 29 Nov 2023, 18:23:26 UTC are bad, tasks which were downloaded at 29 Nov 2023, 21:13:27 UTC are good." is what xii5ku noted. I think this has to do with when I deleted the binaries from the database and put them back up with the correct URL. Is this causing issues with WU's? |
©2024 Astroinformatics Group