There are some errors in the pages with all the tasks. For example here Deprecated: Implicit conversion from float-string "637.401947" to int loses precision in /home/boinc/boinc/milkyway/html/inc/util.inc on line 424 Deprecated: Implicit conversion from float-string "1753.75" to int loses precision in /home/boinc/boinc/milkyway/html/inc/util.inc on line 424 https://milkyway-new.cs.rpi.edu/milkyway/result.php?resultid=930340479

This error should be fixed now.

Thank you for all the hard work. On my Linux machines, I have now added MilkyWay@home back successfully.

Question - Is credit for work done now working as well?

Not that I was aware of.
Are validated runs not awarding credit?

Are validated runs not awarding credit?

They are here.

Thanks for the reply, and clearing that up. :-)

---

Thank you for all the hard work. On my Linux machines, I have now added MilkyWay@home back successfully.

Question - Is credit for work done now working as well?

Not that I was aware of.
Are validated runs not awarding credit?

Credit "on" project appears to be fine. Credit and Stat's Export have not resumed yet

Last update user XML 2023-10-31 17:04:29 UTC (5 days 23:30:05 old)
Last update host XML 2023-10-30 17:04:30 UTC (6 days 23:30:04 old)
Last update team XML 2023-10-31 17:04:29 UTC (5 days 23:30:05 old)

Thanks
Bill F

It's definitely certificate related on my Linux Docker.
Running this command on my mac works, but on my container it returns an error.

curl https://milkyway-new.cs.rpi.edu/milkyway/get_project_config.php -v

Results on Docker:

root@84d5ad767049:/tmp/certs# curl https://milkyway.cs.rpi.edu/milkyway/get_project_config.php -v
*   Trying 128.113.126.54:443...
* Connected to milkyway.cs.rpi.edu (128.113.126.54) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

The root CA is in my ca-certificates.crt file, so I am not sure what is going on yet.

The bad Certificate is on the Server side so unless you are a MilkyWay Admin you can't fix it, give them time

Thank you for all the hard work. On my Linux machines, I have now added MilkyWay@home back successfully.

Question - Is credit for work done now working as well?

Not that I was aware of.
Are validated runs not awarding credit?

Credit "on" project appears to be fine. Credit and Stat's Export have not resumed yet

Last update user XML 2023-10-31 17:04:29 UTC (5 days 23:30:05 old)
Last update host XML 2023-10-30 17:04:30 UTC (6 days 23:30:04 old)
Last update team XML 2023-10-31 17:04:29 UTC (5 days 23:30:05 old)

Thanks
Bill F

Is there any updated information available regarding the resumption of Stat's Exporting ? Current time stamps below.

Last update user XML 2023-10-31 17:04:29 UTC (8 days 21:37:30 old)
Last update host XML 2023-10-30 17:04:30 UTC (9 days 21:37:29 old)
Last update team XML 2023-10-31 17:04:29 UTC (8 days 21:37:30 old)

Thank you
Bill F

I'm on WIndows 10 with latest BOINC client and can't get any work. I'm using BAM so it still is pointed to the HTTPS site instead of the HTTP site I keep messages to point to.

From my log:

11/11/23 8:24:02 AM |  | Project communication failed: attempting access to reference site
11/11/23 8:24:02 AM | Milkyway@home | Scheduler request to url failed: Couldn't resolve host name
11/11/23 8:24:02 AM | Milkyway@home | Sending scheduler request: Requested by user.
11/11/23 8:24:02 AM | Milkyway@home | Requesting new tasks for CPU
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] CPU work request: 28505.99 seconds; 0.44 devices
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
11/11/23 8:24:03 AM |  | Internet access OK - project servers may be temporarily down.
11/11/23 8:24:04 AM | Milkyway@home | Scheduler request completed: got 0 new tasks
11/11/23 8:24:04 AM | Milkyway@home | [sched_op] Server version 721
11/11/23 8:24:04 AM | Milkyway@home | This project seems to have changed its URL.  When convenient, remove the project, then add http://milkyway-new.cs.rpi.edu/milkyway/

(I'm not currently running any GPU work for ANY project)

Best,

Yav

I'm on WIndows 10 with latest BOINC client and can't get any work. I'm using BAM so it still is pointed to the HTTPS site instead of the HTTP site I keep messages to point to.

From my log:

11/11/23 8:24:02 AM |  | Project communication failed: attempting access to reference site
11/11/23 8:24:02 AM | Milkyway@home | Scheduler request to url failed: Couldn't resolve host name
11/11/23 8:24:02 AM | Milkyway@home | Sending scheduler request: Requested by user.
11/11/23 8:24:02 AM | Milkyway@home | Requesting new tasks for CPU
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] CPU work request: 28505.99 seconds; 0.44 devices
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
11/11/23 8:24:03 AM |  | Internet access OK - project servers may be temporarily down.
11/11/23 8:24:04 AM | Milkyway@home | Scheduler request completed: got 0 new tasks
11/11/23 8:24:04 AM | Milkyway@home | [sched_op] Server version 721
11/11/23 8:24:04 AM | Milkyway@home | This project seems to have changed its URL.  When convenient, remove the project, then add http://milkyway-new.cs.rpi.edu/milkyway/

(I'm not currently running any GPU work for ANY project)

Best,

Yav

This project no longer has any GPU work. Go to your preferences and enable tasks for Milkyway@home N-Body Simulation

Respectfully
Bill F

As mentioned by others, credit stats export is not working yet. I am not sure where 3rd party sites (free-dc, boincstats, …) got their stats files from before the maintenance downtime. But at least the expected place http://milkyway.cs.rpi.edu/milkyway/stats/ (or https, or/and milkyway-new if you will) is empty.

As mentioned by others, credit stats export is not working yet. I am not sure where 3rd party sites (free-dc, boincstats, …) got their stats files from before the maintenance downtime. But at least the expected place http://milkyway.cs.rpi.edu/milkyway/stats/ (or https, or/and milkyway-new if you will) is empty.

This should be working now (at least the stats seem to be in the directory). Let me know if there is still an issue with stats.

As mentioned by others, credit stats export is not working yet. I am not sure where 3rd party sites (free-dc, boincstats, …) got their stats files from before the maintenance downtime. But at least the expected place http://milkyway.cs.rpi.edu/milkyway/stats/ (or https, or/and milkyway-new if you will) is empty.

This should be working now (at least the stats seem to be in the directory). Let me know if there is still an issue with stats.

Mine showed up tonight thankyou very much!!

Today I got a Workunit 962969273 aborted by project. What does that mean?

Application
Milkyway@home N-Body Simulation 1.83 (mt)
Name
de_nbody_02_27_2023_v182_pal5__data__11_1688749648_2138300
State
Aborted by project
Received
11/13/2023 9:03:31 PM
Report deadline
11/25/2023 9:03:30 PM
Resources
4 CPUs
Estimated computation size
3,012 GFLOPs
CPU time
---
Elapsed time
---
Executable
milkyway_nbody_1.83_windows_x86_64__mt.exe

---

Everything stays
But it still changes
Ever so slightly
Daily and nightly
In little ways
When everything stays...

Today I got a Workunit 962969273 aborted by project. What does that mean?

It means the server decided your result wasn't needed, and as you hadn't started processing it when the server was next contacted it told your client to abort it!

This usually happens when a task is issued because a prior task goes to "No Reply" state but then returns late (often a day or more so!) -- that appears to be the case with your example.

Cheers - Al.

[quote]I'm on WIndows 10 ...

From my log:/quote]

This project no longer has any GPU work. Go to your preferences and enable tasks for Milkyway@home N-Body Simulation

Respectfully
Bill F

Okay, I'll give it a try. I forgotten I neeed to check that. I'm on a laptop and I don't like to run GPU tasks until it's get colder irregardless. :)

Been a little whiles since I ran MilkyWay, not runnng WCG full-time anymore so I've been bouncing between Einstein and Asteroids. Saw the server migration and thought I start running some Milky again too...

~Yav

I'm on WIndows 10 with latest BOINC client and can't get any work.

Go to your preferences and enable tasks for Milkyway@home N-Body Simulation

Respectfully
Bill F

Nbody was checked on both main and work preferences. The only thing not checked was run other applications on work. I checked it, saved it and tried it again...

First try, I had a moment and smacked myself for not turning work fetch on...

Second try client requested work, but didn't get any:

[11/15/23 7:26:44 PM | Milkyway@home | [sched_op] CPU work request: 34560.00 seconds; 1.00 devices
11/15/23 7:26:47 PM |  | Project communication failed: attempting access to reference site
11/15/23 7:26:47 PM | Milkyway@home | Scheduler request completed: got 0 new tasks
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Server version 721
11/15/23 7:26:47 PM | Milkyway@home | This project seems to have changed its URL.  When convenient, remove the project, then add http://milkyway-new.cs.rpi.edu/milkyway/
11/15/23 7:26:47 PM | Milkyway@home | No tasks sent
11/15/23 7:26:47 PM | Milkyway@home | Project requested delay of 91 seconds
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Deferring communication for 00:01:31
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Reason: requested by project
11/15/23 7:26:48 PM |  | Internet access OK - project servers may be temporarily down.

It did an auto-try a couple mins later and failed to get any work again.

I'm on WIndows 10 with latest BOINC client and can't get any work.

Go to your preferences and enable tasks for Milkyway@home N-Body Simulation

Respectfully
Bill F

Nbody was checked on both main and work preferences. The only thing not checked was run other applications on work. I checked it, saved it and tried it again...

First try, I had a moment and smacked myself for not turning work fetch on...

Second try client requested work, but didn't get any:

[11/15/23 7:26:44 PM | Milkyway@home | [sched_op] CPU work request: 34560.00 seconds; 1.00 devices
11/15/23 7:26:47 PM |  | Project communication failed: attempting access to reference site
11/15/23 7:26:47 PM | Milkyway@home | Scheduler request completed: got 0 new tasks
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Server version 721
11/15/23 7:26:47 PM | Milkyway@home | This project seems to have changed its URL.  When convenient, remove the project, then add http://milkyway-new.cs.rpi.edu/milkyway/
11/15/23 7:26:47 PM | Milkyway@home | No tasks sent
11/15/23 7:26:47 PM | Milkyway@home | Project requested delay of 91 seconds
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Deferring communication for 00:01:31
11/15/23 7:26:47 PM | Milkyway@home | [sched_op] Reason: requested by project
11/15/23 7:26:48 PM |  | Internet access OK - project servers may be temporarily down.

It did an auto-try a couple mins later and failed to get any work again.

You need to delete the Project from the Boinc Manager and then add it back in agaIn thru the Boinc Manager because it slightly changed it's name when it went to the new Server and your milkyway.xml file has the old name in it.

message double - posted due to error, deleting duplicate

another issue to report!
I am getting hostname resolution errors now:

34852: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Sending scheduler request: To report completed tasks.
34853: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Reporting 1 completed tasks
34854: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Not requesting tasks: don't need (job cache full)
34855: 19-Nov-2023 11:13:42 (low) [] Project communication failed: attempting access to reference site
34856: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Scheduler request failed: Couldn't resolve host name
34857: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Sending scheduler request: To report completed tasks.
34858: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Reporting 1 completed tasks
34859: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Not requesting tasks: don't need (job cache full)
34860: 19-Nov-2023 11:13:43 (low) [] Internet access OK - project servers may be temporarily down.
34861: 19-Nov-2023 11:13:43 (low) [Milkyway@home] Scheduler request completed
34862: 19-Nov-2023 11:13:43 (low) [Milkyway@home] Project requested delay of 91 seconds

this happens on multiple machines both linux as well as MacOS [even though MacOS gets no tasks now the project communication used to work ok ...
tested both on mobile hotspot as well as wired so it's not my internet or DNS acting up.....

the project is configured correctly with the new URL

boinccmd --get_simple_gui_info
======== Projects ========
1) -----------
   name: Milkyway@home
   master URL: http://milkyway-new.cs.rpi.edu/milkyway/
   user_name: Marcin
   team_name: Mac OS X
   resource share: 105.000000
   user_total_credit: 9459583.278168
   user_expavg_credit: 10600.251251
   host_total_credit: 1661439.140589
   host_expavg_credit: 1919.528553
   nrpc_failures: 0
   master_fetch_failures: 0
   master fetch pending: no
   scheduler RPC pending: no
   trickle upload pending: no
   attached via Account Manager: no
   ended: no
   suspended via GUI: no
   don't request more work: no
   disk usage: 14.09MB
   last RPC: Sun Nov 19 11:13:43 2023

   project files downloaded: 0.000000
GUI URL:
   name: Message boards
   description: Correspond with other users on the Milkyway@home message boards
   URL: http://milkyway-new.cs.rpi.edu/milkyway/forum_index.php
GUI URL:
   name: Your account
   description: View your account information
   URL: http://milkyway-new.cs.rpi.edu/milkyway/home.php
GUI URL:
   name: Your tasks
   description: View the last week or so of computational work
   URL: http://milkyway-new.cs.rpi.edu/milkyway/results.php?userid=47526
GUI URL:
   name: Your team
   description: View information about your team: Mac OS X
   URL: http://milkyway-new.cs.rpi.edu/milkyway/team_display.php?teamid=2603
   jobs succeeded: 47
   jobs failed: 0
   elapsed time: 834892.629568
   cross-project ID: 84fc0a2716954bd0415f99df95645be7

Marcin wrote:

another issue to report!
I am getting hostname resolution errors now:

34852: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Sending scheduler request: To report completed tasks.
34853: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Reporting 1 completed tasks
34854: 19-Nov-2023 11:13:37 (low) [Milkyway@home] Not requesting tasks: don't need (job cache full)
34855: 19-Nov-2023 11:13:42 (low) [] Project communication failed: attempting access to reference site
34856: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Scheduler request failed: Couldn't resolve host name
34857: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Sending scheduler request: To report completed tasks.
34858: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Reporting 1 completed tasks
34859: 19-Nov-2023 11:13:42 (low) [Milkyway@home] Not requesting tasks: don't need (job cache full)
34860: 19-Nov-2023 11:13:43 (low) [] Internet access OK - project servers may be temporarily down.
34861: 19-Nov-2023 11:13:43 (low) [Milkyway@home] Scheduler request completed
34862: 19-Nov-2023 11:13:43 (low) [Milkyway@home] Project requested delay of 91 seconds

this happens on multiple machines both linux as well as MacOS [even though MacOS gets no tasks now the project communication used to work ok ...
tested both on mobile hotspot as well as wired so it's not my internet or DNS acting up.....

This happens on most of my hosts too.

The reason is that client_state.xml on my hosts contains *two* scheduler URL entries now, instead of one:

<project>
    <master_url>http://milkyway-new.cs.rpi.edu/milkyway/</master_url>
    <project_name>Milkyway@home</project_name>
    [...]
    <scheduler_url>https://milkyway-new.cs.rpi.edu/milkyway_cgi/cgi</scheduler_url>
    <scheduler_url>url</scheduler_url>
    [...]
<project>

Therefore the client emits scheduler requests to both URLs.
But obviously, the hostname "url" cannot be resolved.

The project server's HTML code at the master URL looks broken:

<!DOCTYPE html>
        <html lang="en">
        <head>
    
        <meta name="viewport" content="width=device-width, initial-scale=1">
    
<!-- <scheduler>https://milkyway-new.cs.rpi.edu/milkyway_cgi/cgi</scheduler> -->"
<link rel="boinc_scheduler" href="url"">
        <title>MilkyWay@home</title>

        <meta charset="utf-8">
    
            <link type="text/css" rel="stylesheet" href="https://milkyway-new.cs.rpi.edu/milkyway//bootstrap.min.css" media="all">
        
        <link rel=alternate type="application/rss+xml" title="RSS 2.0" href="https://milkyway-new.cs.rpi.edu/milkyway/rss_main.php">
        </head>
    <body >
[...]

Evidently, the clients picked the bogus <scheduler_url>url</scheduler_url> item up from the <link rel=... href=...> line. Maybe you ( = the project admins) need to put the proper scheduler URL into the attribute. Or maybe you just need to balance the " in the attribute string, I don't know. I looked at two other random projects, and they show their properly expanded scheduler URL in the corresponding <link> element on their master page, enclosed in balanced ".

It seems that I can eliminate the issue locally in the client by shutting down the client, removing the <scheduler_url>url</scheduler_url> line from client_state.xml, and restarting the client. But that's just a workaround of course, the real fix needs to happen on the server.