Hello everyone,

Announcement
The server needs to be rebooted. This will happen on 6 September 2024 at 14:00 UTC. If this fixes the issue, the server will be down for less than an hour.

Thanks,
Kevin

Seems something is wrong, I'm almost out of work and there's no new work available.

Hello everyone,

Announcement
The server needs to be rebooted. This will happen on 6 September 2024 at 14:00 UTC. If this fixes the issue, the server will be down for less than an hour.

Thanks,
Kevin

Seems something is wrong, I'm almost out of work and there's no new work available.

Same thing here. :/

I am not seeing any shortage of available tasks. The server status page is showing the normal 1000+ tasks available.

Bill F

I am not seeing any shortage of available tasks. The server status page is showing the normal 1000+ tasks available.

I'm receiving tasks now.

@Kevin: you might need to check the disk limit for the current WUs, it might be necessary to increase it. I got EXIT_DISK_LIMIT_EXCEEDED errors on some of the de_nbody_orbit_fitting_03_25_2025_v186_OCS__data__33_1740880091_* tasks, the wingmen got them too. The slot directories of the running WUs seem to be quite a bit larger than what they used to be in the past as far as I remember, some of them close to or even over 30MB, the errored out tasks went over 50MB. Perhaps the current WU set needs 100-200MB as limit.

Examples: 1001559783, 1001630955.

---

Yes, the admins need to look into the task generation template and correct this error. I'm getting half a dozen a day of these errors on known good hardware and Boinc setups.

---

Still not fixed:
1002361354 Too many errors (may have bug)
1002146987 Stil in progress on other machines, EXIT_DISK_LIMIT_EXCEEDED on my computer.

This one is interesting, it errored out for me, but two other computers could finish it with 40.72 MB and 44.48 MB peak disk usage: 1002419239

---

@Kevin: you might need to check the disk limit for the current WUs, it might be necessary to increase it. I got EXIT_DISK_LIMIT_EXCEEDED errors on some of the de_nbody_orbit_fitting_03_25_2025_v186_OCS__data__33_1740880091_* tasks, the wingmen got them too. The slot directories of the running WUs seem to be quite a bit larger than what they used to be in the past as far as I remember, some of them close to or even over 30MB, the errored out tasks went over 50MB. Perhaps the current WU set needs 100-200MB as limit.

Examples: 1001559783, 1001630955.

I set the limit to 100MB.
Let me know if the issue persists.

Still seeing the errors. I have very low caches on each host but the older resends are still coming through with the misconfiguration. It will probably take a fairly long while to clear all the bad work with 8 possible resends for each task.

---

Still seeing the errors. I have very low caches on each host but the older resends are still coming through with the misconfiguration. It will probably take a fairly long while to clear all the bad work with 8 possible resends for each task.

The same applies to me. I have nearly 2,200 errors.

---

George

Still seeing the errors. I have very low caches on each host but the older resends are still coming through with the misconfiguration.

This was not a resend, it was _0 created more than 12 hours after Kevin's post.

The same applies to me. I have nearly 2,200 errors.

Nearly all of your errors are Aborted by user, 203 (0x000000CB) EXIT_ABORTED_VIA_GUI. Users aborting 2000 WUs is not an issue we are talking here about.

---

The same applies to me. I have nearly 2,200 errors.

Nearly all of your errors are Aborted by user, 203 (0x000000CB) EXIT_ABORTED_VIA_GUI. Users aborting 2000 WUs is not an issue we are talking here about.

Ooops! Sorry! I forgot that I did abort literally all of those in an effort to get Orbit Fitting to not give me single tasks when I have x4 CPUs in my app_config.xml file.

---

George

Ooops! Sorry! I forgot that I did abort literally all of those in an effort to get Orbit Fitting to not give me single tasks when I have x4 CPUs in my app_config.xml file.

Don't use app_config.xml anymore for setting the number of threads per WU, use MilkyWay@home preferences instead, than you will get what you want.

All that's left of my app_config.xml is this (to get better run time estimates):

<app_config>
 <app>
  <name>milkyway_nbody</name>
  <fraction_done_exact/>
 </app>
 <app>
  <name>milkyway_nbody_orbit_fitting</name>
  <fraction_done_exact/>
 </app>
</app_config>

---

Ooops! Sorry! I forgot that I did abort literally all of those in an effort to get Orbit Fitting to not give me single tasks when I have x4 CPUs in my app_config.xml file.

Don't use app_config.xml anymore for setting the number of threads per WU, use MilkyWay@home preferences instead, than you will get what you want.

All that's left of my app_config.xml is this (to get better run time estimates):

<app_config>
 <app>
  <name>milkyway_nbody</name>
  <fraction_done_exact/>
 </app>
 <app>
  <name>milkyway_nbody_orbit_fitting</name>
  <fraction_done_exact/>
 </app>
</app_config>

I already do use the Milkyway preferences for just that.[/img]

---

George

I already do use the Milkyway preferences for just that.

What settings do you have there? If you want 4-thread tasks, set "Max # of threads for each MilkyWay@home task" to 4, remove anything regarding number of threads from your app_config.xml and the server should not send you any single thread tasks. It used to work in the past at least. Do not use "no limit", that will result in a mix of MT and ST tasks.

---

@Kevin: you might need to check the disk limit for the current WUs, it might be necessary to increase it. I got EXIT_DISK_LIMIT_EXCEEDED errors on some of the de_nbody_orbit_fitting_03_25_2025_v186_OCS__data__33_1740880091_* tasks, the wingmen got them too. The slot directories of the running WUs seem to be quite a bit larger than what they used to be in the past as far as I remember, some of them close to or even over 30MB, the errored out tasks went over 50MB. Perhaps the current WU set needs 100-200MB as limit.

Examples: 1001559783, 1001630955.

I set the limit to 100MB.
Let me know if the issue persists.

1002940398, 1003025268 and 1002958647, all created 3-15 days after your post error out with EXIT_DISK_LIMIT_EXCEEDED after exceeding 50MB. You might need to check again.

---

Somewhat annoying...

https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1015374201

Somewhat annoying...

https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1015374201

Well, this WU was created before the change (well, at least before Kevin's message), not sure if the change applies to new results or just new WUs.

---

@Kevin: you might need to check the disk limit for the current WUs, it might be necessary to increase it. I got EXIT_DISK_LIMIT_EXCEEDED errors on some of the de_nbody_orbit_fitting_03_25_2025_v186_OCS__data__33_1740880091_* tasks, the wingmen got them too. The slot directories of the running WUs seem to be quite a bit larger than what they used to be in the past as far as I remember, some of them close to or even over 30MB, the errored out tasks went over 50MB. Perhaps the current WU set needs 100-200MB as limit.

Examples: 1001559783, 1001630955.

I set the limit to 100MB.
Let me know if the issue persists.

1002940398, 1003025268 and 1002958647, all created 3-15 days after your post error out with EXIT_DISK_LIMIT_EXCEEDED after exceeding 50MB. You might need to check again.

Seems like I might have changed the wrong thing?
I changed what I think should be the right setting now to 100MB.
Again, let me know if the issue persists.

Somewhat annoying...

https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1015374201

Well, this WU was created before the change (well, at least before Kevin's message), not sure if the change applies to new results or just new WUs.

Got another created after Kevin's message
https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1003011105