LHC@home

My win11 host has started to see server problems but my win10 host is still connecting OK and getting new work. I did a project reset on problem host but the problem persists. Here is what I see on the message log:

86	LHC@home	17-09-2025 20:54	[sched_op] Starting scheduler request	
87	LHC@home	17-09-2025 20:54	Sending scheduler request: To fetch work.	
88	LHC@home	17-09-2025 20:54	Requesting new tasks for CPU and NVIDIA GPU	
89	LHC@home	17-09-2025 20:54	[sched_op] CPU work request: 95040.00 seconds; 0.00 devices	
90	LHC@home	17-09-2025 20:54	[sched_op] NVIDIA GPU work request: 1001.00 seconds; 0.00 devices	
91	LHC@home	17-09-2025 20:54	[sched_op] AMD/ATI GPU work request: 0.00 seconds; 0.00 devices	
92	LHC@home	17-09-2025 20:54	Scheduler request completed: got 0 new tasks	
93	LHC@home	17-09-2025 20:54	Server can't open log file (../log_boinc01/scheduler.log)	
94	LHC@home	17-09-2025 20:54	[sched_op] Deferring communication for 00:03:34	
95	LHC@home	17-09-2025 20:54	[sched_op] Reason: project is down	

This host has BOINC 8.0.2. So the problem seems to be Server can't open log file (../log_boinc01/scheduler.log) but how to resolve this situation?
[edit] The same message appeared also before project reset.
[edit2] The situation started when I aborted a Theory task that had gone past the deadline and server had marked it: Timed out - no response. Here is the host: https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10858236 I am not sure if the project reset went through as the host shows still that it has all the same tasks as before.
[edit3] I will try to detach and reattach the host .

---

Removing LHC@home and adding it again didn't help. Same error appears: Server can't open log file (../log_boinc01/scheduler.log)

---

Getting the same error here as well

9/17/2025 12:18:06 PM | LHC@home | Server can't open log file (../log_boinc01/scheduler.log)

Same here

This is server side, not client side, issue is with LHC server.

---

Paul.

Oddly the win10 host (BOINC 7.16.5) is still communicating normally with server and getting new Atlas work. The problem host didn't get even a host id from server after adding LHC as a new project. Boinc Manager shows host id as 0.

---

I was able to fix this by going out to my boinc data folder and just making a file called scheduler.log
Edit: Nevermind I just realized that error message was coming from the server and I just got lucky when I tried that .

I can't speak for everyone but the reason I mentioned it was so that people on the server side would see us saying this and then they would do their part to take care of that.
If we don't do that it doesn't get fixed and next thing it is a weekend and nobody looks at anything until the next monday at best.

Thu 18 Sep 2025 13:53:37 | LHC@home | update requested by user
Thu 18 Sep 2025 13:53:41 | LHC@home | Sending scheduler request: Requested by user.
Thu 18 Sep 2025 13:53:41 | LHC@home | Requesting new tasks for CPU
Thu 18 Sep 2025 13:53:42 | LHC@home | Scheduler request completed: got 0 new tasks
Thu 18 Sep 2025 13:53:42 | LHC@home | Server can't open log file (../log_boinc01/scheduler.log)

Still happening here

This is a server side issue on boinc01.cern.ch.
So far boinc02.cern.ch is not affected.

It can't be solved on the client side without tweaking the own DNS since load balancing between both is done via DNS, hence by random.
It's not worth to do so.

Admins are informed.

For me the problem was solved about an hour and a half ago. Crunching is going on and cache is full :-)
The nice people at Cern got it going, I didn't do anything. Thank you!

---

Any info on why all servers besides scheduler, upload and download are offline?

---

Any info on why all servers besides scheduler, upload and download are offline?

Here CMS tasks were uploaded, but could not get reported. When pushing the Update button on the left hand side of the BOINC manager, in the status column it says "communication deferred - and the time counts downwards from 1 hour).
The BOINC event log says "Project server temporarily down for maintenance" and "project requested delay of 3600 seconds".

Also, the number of unsent CMS tasks on the server status page is shrinking.

All systems seem to be working now, validation queue is gone.

---

All systems seem to be working now, validation queue is gone.

here, too :-)