Since this weekend new work got uploaded to the server I see a lot of messages "Project communication failed" on all my hosts resulting in my hosts being more idle than productive when trying to do the small tasks.

Thanks,
Ardo

Interesting. Is perhaps the database server "busy" which on its turn makes the web server "busy"?

By the way, I switched the hosts to long tasks and average tasks to keep them happily crunching...

To gather additional data: I did some tasks from Milkyway@Home and they all went through without any issues. Then I switched back to SRBase and the first update command resulted again in "failing to communicate".

Some further data: I rebooted all the hosts as well as all the networking equipment, up to and including the cable modem, and the issue persists.

Could this be an issue between the Internet and the host you're running this one, like e.g. a firewall?

The situation has not changed: Most of the uploads, reports and downloads are OK, but there are quite a few retries, double retries, and even triple retries. And once the uploads succeeds, then there is the wait for the reports to succeed and then there is the downloads with a similar number of retries.

I also noticed that some of the download issues are of the "project deferred for large number of minutes" category.

The cache is set to 0.1 day. For the (very) short tasks, say less than a minute, that is not sufficient, with the maximum of 7 WUs per core, to survive all the retries making the running idle from time to time. For the longer tasks the cache is sufficient to keep the cores busy continuously.

I put one of the hosts temporarily on PrimeGrid doing ESP/PSP/SoB sieving and it all went without any issue whatsoever. And in all the years of doing PrimeGrid WUs I never had this issue.

Maybe this project simply does not want me to process that many WUs... ;-)

Just FYI: I do not know what happened and what, if anything, got changed and/or cleared up where, but since yesterday the WUs are flowing as smooth as before I reported the issue in this thread. Life is good again. :-)

...
Good to hear, nothing changed on server side.

Just FYI Reb.
I get this when I try to look at my valid tasks:
"Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 64 bytes) in /home/boincadm/projects/sr5/html/inc/db_conn.inc on line 119"

Mankka*

Just FYI Reb.
I get this when I try to look at my valid tasks:
"Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 64 bytes) in /home/boincadm/projects/sr5/html/inc/db_conn.inc on line 119"

Mankka*

Its working for me but the current work creation with 1M WUs could make some issues with the php RAM reserveration.

Update:
I have changed the memory limit in php.ini to 1GB. Can you check if the error is still present?

Mankka*: I have restarted Apache but the work generation script is not running anymore. I hope the error is gone now.