My tasks come to standstill with "Waiting for swap space" all of a sudden.
Same system worked without error before.
Installing ZRAM didn't help either.

BOINC version 8.2.14
RAM 31.14 GB
Cache 6144 KB
Virtual memory 19.57 GB
Total disk space 915.53 GB
Free disk space 559.7 GB

My distro made me update to 8.2.15: same behaviour

[quote]This site is being SPAMMED in a big way, can measures be taken to stop it please.

Conan

Those are not permanent badges. Based off RAC, if you're in the top % you'll have one of three badges. I think Top 1/5/25%. But if you stop then it goes away and it depends on how many users there are.

As the title states...can we possibly get an Android application? There are fewer and fewer Android supported projects out there. It would be nice to have more options.

What about spacious@home? Will they require more computing power and could potentially benefit?

Gaia 4 have empty inputs for new jobs, so it is finished developed jobs.
I upgrade Gaia6 generator and app (job generator have problem with contact with JPL Horision - fixed, app was problem calculate physical parameters with specyfic situations - now is testing).
I plan to waiting for last active jobs, cleaning database and disc space, upload new app and start generator for Gaia 6.

Any updates?

+1
They seem to come in waves, maybe the feeder is full of 6 most of the time and many only want 4.
I am just able to keep working most of the time.

@ADMINS ANY UPDATES ??
Still receiving same "-195 errors" with the _4 tasks.

"195" error is a generic error from BOINC, not specifically in regard to the app.

your CPU is over 15 years old and lacks modern features such as SSE4 and AVX. this probably the reason they all fail.

the Gaia_5 and Gaia_6 apps probably do not require this, which is why they work.

That could be an interesting research Project to be done here on the returns

i checked 20 of the successful resends from his most recent 20 errors. and all were newer systems with more modern instruction sets. the oldest system that a resend successfully completed was on an i5-4250U, which supports SSE4/AVX/AVX2.

there's a strong correlation here. but also very unlikely that many people are running such old hardware anyway so pretty unlikely that a resend would go to such an old system.

More work loaded for 4 & 6.

That may be all the work there is for these batches (4 & 6) :)

@ADMINS ANY UPDATES ??
Still receiving same "-195 errors" with the _4 tasks.

"195" error is a generic error from BOINC, not specifically in regard to the app.

your CPU is over 15 years old and lacks modern features such as SSE4 and AVX. this probably the reason they all fail.

the Gaia_5 and Gaia_6 apps probably do not require this, which is why they work.

Simple solution.
Run this project in a VM or multi BOINC install.
No BOINC queue management headaches.
The queue was setup for a single core machine and does not allow multiple queues assigned to groupings of cores. It's clunky and needs to be completely reworked.

I guess I could but was hoping a simple app_config would solve the whole thing!!

That server is running a custom stripped down Windows 10, with minimal services and maximal RAM available, so the subsystem fails.
I just built a minimal AntiX Linux VM and maintain it (good learning experience for low skill Linux tech like me)..
That VM has been a nice addition as it sits there waiting for a Linux only project to generate rare WU's and not a serious issue to share 16 cores of the 48 available, for a while, unless it's prime number searching. Those are a race.

Oh, some projects ignore the 0 resource anyway and might send you tasks. NFS is one. Yoyo used to.

(Nice seeing you here. We WUPropers get around!!!).

Conan, this is an app_config. An app_info needs a client restart.

If you run out of Gaia 4 tasks then you'll only be running a single task. The client will see work available to run (it does not know about max_concurrent preferences) and not download any backup project at 0 priority. Just something to watch out for.

I have setup a zero resource Project that would take over so it's okay, but thanks for the warning.

It won't since the client still shows that you have work available from a non-zero project and will not download work.

.

Simple solution.
Run this project in a VM or multi BOINC install.
No BOINC queue management headaches.
The queue was setup for a single core machine and does not allow multiple queues assigned to groupings of cores. It's clunky and needs to be completely reworked.

Conan, this is an app_config. An app_info needs a client restart.

[quote]If you run out of Gaia 4 tasks then you'll only be running a single task. The client will see work available to run (it does not know about max_concurrent preferences) and not download any backup project at 0 priority. Just something to watch out for.

I have setup a zero resource Project that would take over so it's okay, but thanks for the warning.

Known applications:
4_Gaia@home[20241019.1457]
5_Gaia@home[20241023.2232]
6_Gaia@home[20241102.2234]
4_Gaia@home[20241102.1102]
4_Gaia@home[20241130.0949] ----

I'm guessing only the last one is the correct one for Gaia 4 as it matches the date on the apps.php page of 11/30. If not, then keep adding apps to the config file for any "known" apps the log shows.

I would also like an app selection in preferences. I am near my WUProp hours goal for Gaia 6 so will no longer want those tasks.

This is what I used to currently control how many gaia_4 and gaia_6 tasks that I want to run since there are the only two apps currently available. Edit as needed when new apps appear. It works fine on my PC.

<app_config>
<app>
<name>6_Gaia@home[20241102.2234]</name>
<max_concurrent>4</max_concurrent>
</app>
<app>
<name>4_Gaia@home[20241130.0949]</name>
<max_concurrent>4</max_concurrent>
</app>
</app_config>

Thank you VERY much!!!

If you run out of Gaia 4 tasks then you'll only be running a single task. The client will see work available to run (it does not know about max_concurrent preferences) and not download any backup project at 0 priority. Just something to watch out for.