As far as Asteroids it is NOT on your end, Kyong is having some personal issues going on right now and can't babysit the machine when it goes wonky, and for some reason it is doing that alot lately. As of this morning, my time on the East Coast of the US, I am able to send back all of my Asteroid units just fine. so he did get that part fixed at least. I do not know if he fixed the get units part or not as I have switched to doing PG units with most of my cpu's for right now.

Personal life comes first, and there are many other projects that can process if this project has a temporary error. I don't know how old the server actually is, but if it keeps having problems maybe it's time for a new one.

That, or its just an update that broke something.

I wrote that it was something bad in the latest BOINC source so upgrade did it.

... so upgrade did it.

If somebody still don't understand:
- there was no Hardware upgrade/change (the server is relatively new)
- this was "upgrade" of BOINC server code that broke things
      Returning to previous BOINC server code was the fix

(BOINC server code is what you see as 'scheduler', 'feeder', 'db_purge', ...
http://asteroidsathome.net/boinc/server_status.php
)

 

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Developers finally fixed the problem with scheduler so I have upgraded it again. According to log it seems to be working now. I hope that there is no other important bug now.

Yes, indeed, it works fine now.
THX!

Yes, indeed, it works fine now.
THX!

I cannot confirm that, one of my boxes that uses anon. platform because I want to enforce a specific CPU command set does not receive work anymore - no reason given.
It did receive work immediately after the comeback but today I wanted it to fetch some more results and the server won't give amy to me.
The application details page shows no limitations per day that would explain it.

Yes, indeed, it works fine now.
THX!

I cannot confirm that, one of my boxes that uses anon. platform because I want to enforce a specific CPU command set does not receive work anymore - no reason given.
It did receive work immediately after the comeback but today I wanted it to fetch some more results and the server won't give amy to me.
The application details page shows no limitations per day that would explain it.

This pc
http://asteroidsathome.net/boinc/show_host_detail.php?hostid=88984 uses anon platform (fma4 wu's) and works fine.
BM 7.3.15, win7 x64 sp1

Maybe some "minimum core client version" issue then?

Or it has to do with a somewhat older bug on server side, that didn't do any damage before :
Old client versions report only the CPU time, as the wallclock time is quite irrelevant. If no wallclock time is available, the server should transfer the CPU time into the wallclock time (some projects do that) - but it seems to override CPU time with the (empty) wallclock time instead, so all my results show 0:00 for both time values.

Or the new scheduler checks the user name and there's some hardcoded revenge action, when it's one of my hosts ... for fighting the heartbeat bug for so many years ;-)

Or the new scheduler checks the user name and there's some hardcoded revenge action, when it's one of my hosts ... for fighting the heartbeat bug for so many years ;-)

or you have done something against the nsa and made it to their watchlist now ;-)))


edit:
just to check the app_info.xml here is mine:
<app_info>
<app>
<name>period_search</name>
<user_friendly_name>Period Search Application FMA4</user_friendly_name>
<non_cpu_intensive>0</non_cpu_intensive>
</app>
<file_info>
<name>period_search_10210_windows_x86_64_bd_fma4_gcc.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>period_search</app_name>
<version_num>10211</version_num>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>5163094400.090000</flops>
<file_ref>
<file_name>period_search_10210_windows_x86_64_bd_fma4_gcc.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

---

I adjusted the version_num tag - the binary already has been 10210. I guess that had to do with some testing quite a while back.

I currently cannot restart any of my core clients though, extremely long running QMC workunits (the longest one currently > 34 days at 4%, but they usually end before 20%) and I'm not sure how they checkpoint.

I adjusted the version_num tag - the binary already has been 10210. I guess that had to do with some testing quite a while back. ...

Did the same on a XP x86 box that doesn't get any work anymore either - no luck. Removed app_info.xml completely but still - no luck. So it can only be either the oldish core client or it checks the operating system (well, or the host owner).

Even detach and re-attach doesn't help.

So I guess I'm out here :-(

Even detach and re-attach doesn't help.

So I guess I'm out here :-(

BOINC Version 5.10.28 ?? Other project work with that?

Even detach and re-attach doesn't help.

So I guess I'm out here :-(

BOINC Version 5.10.28 ?? Other project work with that?

My XP x86 pc works just fine here on the latest release version of Boinc.

...
BOINC Version 5.10.28 ?? Other project work with that?

There are very few projects (I would estimate, not more than three) that require a later version, one of them because they have only multithreaded applications, the second one has no CPU applications and 5.x doesn't support GPU.

One thing I like about that BOINC version is that it still works with BOINCview, the second one is the installer, it stays away from the system drive (BOINC data directory in HDD areas that might be roamed is an extremely nasty idea). The third reason is that they removed some of the remote commands, like changing short and long term debits. Imo. that debits stuff is implemented very crappy and this command allows me to override some limitations - without stopping the core client and editing the client state XML.

... so upgrade did it.

If somebody still don't understand:
- there was no Hardware upgrade/change (the server is relatively new)
- this was "upgrade" of BOINC server code that broke things
      Returning to previous BOINC server code was the fix

(BOINC server code is what you see as 'scheduler', 'feeder', 'db_purge', ...
http://asteroidsathome.net/boinc/server_status.php
)

 

Oh... NOW I understand. (don't you just love updates. for every fix, they break 10 other things)