Server Issues

Hello everyone,

Looks like the server had some issues. I rebooted the server and it seems like everything should be running as it should.

Thanks,
Kevin

Hello everyone,

Looks like the server had some issues. I rebooted the server and it seems like everything should be running as it should.

Thanks,
Kevin

Thank you very much!!

I have to regretfully inform you that seemed to not have a measureable effect:

I have 300 WUs to report

but the update command generate those mewssages

10/22/2022 8:07:36 AM | Milkyway@Home | Fetching scheduler list
10/22/2022 8:07:38 AM | | Project communication failed: attempting access to reference site
10/22/2022 8:07:39 AM | | Internet access OK - project servers may be temporarily down.

and communication deferred 24 hours

The website loads quickly now , yesterday it was slow as glue and sometimes with page load timeouts .

I still get the message:
Oct 24 22:53:34 81-7-18-96 boinc[19031]: 24-Oct-2022 22:53:34 [---] Project communication failed: attempting access to reference site
Oct 24 22:53:37 81-7-18-96 boinc[19031]: 24-Oct-2022 22:53:37 [---] Internet access OK - project servers may be temporarily down.

and for a few days my computer does not calculate any new tasks!?

I still get the message:
Oct 24 22:53:34 81-7-18-96 boinc[19031]: 24-Oct-2022 22:53:34 [---] Project communication failed: attempting access to reference site
Oct 24 22:53:37 81-7-18-96 boinc[19031]: 24-Oct-2022 22:53:37 [---] Internet access OK - project servers may be temporarily down.

and for a few days my computer does not calculate any new tasks!?

Keep trying by clicking update in the Projects tab and eventually it will do it's thing

Now server feeder is down, which cannot accept any reporting

72: 25-Oct-2022 19:24:56 (low) [Milkyway@Home] Sending scheduler request: To report completed tasks.
73: 25-Oct-2022 19:24:56 (low) [Milkyway@Home] Reporting 1 completed tasks
74: 25-Oct-2022 19:24:56 (low) [Milkyway@Home] Not requesting tasks: "no new tasks" requested via Manager
75: 25-Oct-2022 19:25:00 (low) [Milkyway@Home] Scheduler request completed
76: 25-Oct-2022 19:25:00 (low) [Milkyway@Home] Server error: feeder not running
77: 25-Oct-2022 19:25:00 (low) [Milkyway@Home] Project requested delay of 400 seconds

---

Kevin,
I have 22 completed tasks to report. Here are the log entries I found after I requested a transfer. It seems to indicate something is not running on the server. Would that be a process on the server on your side or something in my BOINC client?

10/25/2022 7:54:12 AM | Milkyway@Home | Sending scheduler request: To report completed tasks.
10/25/2022 7:54:12 AM | Milkyway@Home | Reporting 21 completed tasks
10/25/2022 7:54:12 AM | Milkyway@Home | Requesting new tasks for NVIDIA GPU
10/25/2022 7:54:13 AM | Milkyway@Home | Scheduler request completed: got 0 new tasks
10/25/2022 7:54:13 AM | Milkyway@Home | Server error: feeder not running
10/25/2022 7:54:13 AM | Milkyway@Home | Project requested delay of 400 seconds
Todd

Main components are down, shown on server status as Not Running.

Kevin,
I have 22 completed tasks to report. Here are the log entries I found after I requested a transfer. It seems to indicate something is not running on the server. Would that be a process on the server on your side or something in my BOINC client?

10/25/2022 7:54:12 AM | Milkyway@Home | Sending scheduler request: To report completed tasks.
10/25/2022 7:54:12 AM | Milkyway@Home | Reporting 21 completed tasks
10/25/2022 7:54:12 AM | Milkyway@Home | Requesting new tasks for NVIDIA GPU
10/25/2022 7:54:13 AM | Milkyway@Home | Scheduler request completed: got 0 new tasks
10/25/2022 7:54:13 AM | Milkyway@Home | Server error: feeder not running
10/25/2022 7:54:13 AM | Milkyway@Home | Project requested delay of 400 seconds
Todd

There were some server issues at the time you posted but everything should be running fine now. Are you still unable to report your completed tasks?

can confirm - as of 25.X.22 - regularly getting the error internet access ok ut project servers are unreachable from BOINC logs on the Milkyway@Home project
did some drive crash again?

can confirm - as of 25.X.22 - regularly getting the error internet access ok ut project servers are unreachable from BOINC logs on the Milkyway@Home project
did some drive crash again?

Server status shows everything running at 7pm East Coast US time

can confirm - as of 25.X.22 - regularly getting the error internet access ok ut project servers are unreachable from BOINC logs on the Milkyway@Home project
did some drive crash again?

Server status shows everything running at 7pm East Coast US time

Server status shows everything is still running at 11pm Eastern Time.
We're on a roll!!!

This message goes out to Tom and the new admins. When you get to the job of rebuilding the servers software, you should try and implement the newest code pull request for fixing the overfetch situation with MT N-body tasks.

https://boinc.berkeley.edu/forum_thread.php?id=14827#110278

https://github.com/BOINC/boinc/pull/4992

---

This message goes out to Tom and the new admins. When you get to the job of rebuilding the servers software, you should try and implement the newest code pull request for fixing the overfetch situation with MT N-body tasks.

Thanks! Noted.

Hy everyone...

Since I use Science-United project organization I repeatedly get the following error.


Milkyway@Home: Notice from BOINC
This project is using an old URL. When convenient, remove the project, then add http://milkyway.cs.rpi.edu/milkyway/


How can I solve that?


thx in advance

---

Hy everyone...

Since I use Science-United project organization I repeatedly get the following error.


Milkyway@Home: Notice from BOINC
This project is using an old URL. When convenient, remove the project, then add http://milkyway.cs.rpi.edu/milkyway/


How can I solve that?


thx in advance

just ignore it is the best thing or you can remove Milkyway thru Science United and then add it back in again which should fix the problem, the key to removing the Project though is any Milkyway tasks on your computer will be removed and you will have to get all new ones after your sign back up again. In Linux there is a way to go in and edit the file that has the Project listings but I don't know if that works in Windows or not, if you could edit the Project listings then all you have to do is shut down and then restart Boinc after you are done editing and no tasks would be lost.

In Linux there is a way to go in and edit the file that has the Project listings but I don't know if that works in Windows or not, if you could edit the Project listings then all you have to do is shut down and then restart Boinc after you are done editing and no tasks would be lost.

BOINC uses same files on Windows, so the procedure is exactly the same, but you have to shut down BOINC first, than edit the files, otherwise the changes will be overwritten when BOINC shuts down.

You need to edit

client_state.xml
account_milkyway.cs.rpi.edu_milkyway.xml
statistics_milkyway.cs.rpi.edu_milkyway.xml (optional)

Change the current Milkyway Master-URL in those to

<master_url>http://milkyway.cs.rpi.edu/milkyway/</master_url>

If you have any tasks running from milkyway, you also need to edit boinc_task_state.xml in the corresponding slot directories and change the Master-URL in each of those files to

<project_master_url>http://milkyway.cs.rpi.edu/milkyway/</project_master_url>

That step can be omitted if you suspend all not started Milkyway tasks and finish the running ones before shutting down BOINC.

Or like mikey said, ignore the message, although one day you might need to make those changes.

---

.

In Linux there is a way to go in and edit the file that has the Project listings but I don't know if that works in Windows or not, if you could edit the Project listings then all you have to do is shut down and then restart Boinc after you are done editing and no tasks would be lost.

BOINC uses same files on Windows, so the procedure is exactly the same, but you have to shut down BOINC first, than edit the files, otherwise the changes will be overwritten when BOINC shuts down.

Thanks Link I now know the answer!!