LHC@home

We had some database problems this morning, where connections from the BOINC server to the database timed out. Daemons have been restarted and the feeder is running again, but the queries are really slow, so in between the feeder updates, the scheduler memory buffer may run out of tasks. During these periods, your BOINC client will report "no tasks available".

Sorry for this, we're investigating the underlying cause with our database experts.

During these periods, your BOINC client will report "no tasks available".
Sorry for this, we're investigating the underlying cause with our database experts.

Thanks for news!!

Thanks for the update, please let us know when things are sorted out!

---

Why mine when you can research? - GRIDCOIN - Real cryptocurrency without wasting hashes! https://gridcoin.us

Sorry for this, we're investigating the underlying cause with our database experts.

still no results?

Sorry for this, we're investigating the underlying cause with our database experts.

still no results?

???

Ref. the news posting, our DB was back again around 5pm our local time. The feeder query is still slow, though, so there will be moments with no tasks in the scheduler buffer.

while before BOINC said "no tasks available", now it says (like at the time the problem started): "server error: feeder not running".

Besides, there must something else be rather wrong: while before I could manually try to download tasks in about 1-minute intervals, now comes the notice "communication deferred: 01:00:00" - which means work can be fetched only one time per hour. How come ???

Because after a daemon restart, it takes time for the feeder to execute on the server and to fill the shared memory buffer for the scheduler. During the initial feeder run, the scheduler will report "feeder not running" until it has received tasks.

Then later you may have other messages, like no tasks available, if the scheduler memory at the time of your request has no tasks left for the particular application you happen to request.

That the BOINC client defers communication by 1 hour is good, it is designed to be resilient and to resume work later.

... During the initial feeder run, the scheduler will report "feeder not running" until it has received tasks.

Then later you may have other messages, like no tasks available, if the scheduler memory at the time of your request has no tasks left for the particular application you happen to request.

thanks for the explanation.

However, what makes me wonder is that now it's the other way round: after "feeder not running" at the beginning of the problem, and "no tasks available" lateron, we are not back at "feeder not running".

good morning, Nils

all night long no new tasks could be downloaded. It still does not work.
What's wrong?

Erich,
fyi Sixtrack is running well.

Since the Native Theory started here I can no longer get ANY of the VB Theory tasks on ANY of my 10 pc's


5/13/2019 11:16:38 PM | LHC@home | No tasks are available for Theory Simulation

That is all I get on all of the hosts here and all I can get are the Sixtracks

So I am about to run out of work here and Sixtracks usually don't last very long here.

I did get Sixtracks on the old X86 pc and they all failed to do anything <core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073741511 (0xc0000139)</message>
]]> all crashed with zero seconds running .......not that I wanted any of them......they are ALL set to get VB Theory tasks and nothing was changed in my settings so they will just be sitting here doing nothing AND the server says there is plenty of VB tasks (I even tried to get CMS tasks and still NOTHING)

Erich,
fyi Sixtrack is running well.

thanks for the information.
Sixtrack really seems the only subtask that can be downloaded. For all others - no way.

at this point of time, the Server Status Page shows that everything except the scheduler has been stopped.
What's going on there? According to Nils' message from yesterday afternoon, everything should have been okay from that time on.

Nils will just tell you that you are wrong......but then he doesn't
actually run thousands of these VB tasks like we do and over 8 years 24/7 in my case.

Right Now as I check the server page this is now what it says as of this second


Status of remote daemons is missing

I guess you quickly try to change the server status just to fake like you were right telling us we are wrong.

And to pretend that it hasn't actually been like this for over 18 hours