Admins, every time my host wants work it gets this response:

16/08/2020 12:57:03 | MLC@Home | Sending scheduler request: To fetch work.
16/08/2020 12:57:03 | MLC@Home | Requesting new tasks for CPU
16/08/2020 12:57:04 | MLC@Home | Scheduler request failed: Couldn't resolve host name
16/08/2020 12:57:04 | MLC@Home | Sending scheduler request: To fetch work.
16/08/2020 12:57:04 | MLC@Home | Requesting new tasks for CPU
16/08/2020 12:57:05 | | Project communication failed: attempting access to reference site
16/08/2020 12:57:06 | | Internet access OK - project servers may be temporarily down.
16/08/2020 12:57:06 | MLC@Home | Scheduler request completed: got 1 new tasks
16/08/2020 12:57:06 | MLC@Home | Project requested delay of 202 seconds
16/08/2020 12:57:08 | MLC@Home | Started download of ParityModified-1594579975-12198-9
16/08/2020 12:57:09 | MLC@Home | Finished download of ParityModified-1594579975-12198-9

I get work but "Couldn't resolve host name" and "Project communication failed" should not be there.
It think there is somekind of mismatch between the host work request and the response from the server.
Please check your settings for this. Thank you.

"Couldn't resolve host name" and "Project communication failed" should not be there

Agreed. The question is, why are they there?

It think there is somekind of mismatch between the host work request and the response from the server.

If the host name can't be resolved there is no request and thus no response. The problem is on your side.

16/08/2020 12:57:03 | MLC@Home | Sending scheduler request: To fetch work.

16/08/2020 12:57:04 | MLC@Home | Sending scheduler request: To fetch work.

What are you doing? Hammering the update button? Stop that, take a deep breath, that may be all you need to do. It could well be a temporary issue with your ISP, or you being impatient. If time doesn't help, check your own system.

"Couldn't resolve host name" and "Project communication failed" should not be there

Agreed. The question is, why are they there?

It think there is somekind of mismatch between the host work request and the response from the server.

If the host name can't be resolved there is no request and thus no response. The problem is on your side.

16/08/2020 12:57:03 | MLC@Home | Sending scheduler request: To fetch work.

16/08/2020 12:57:04 | MLC@Home | Sending scheduler request: To fetch work.

What are you doing? Hammering the update button? Stop that, take a deep breath, that may be all you need to do. It could well be a temporary issue with your ISP, or you being impatient. If time doesn't help, check your own system.

Wrong answer and since I don't think your are one of the Admins please don't give uninformed answers.

This is a clean work request made by the Boinc manager and it happens every time.
Have you checked your own host eventlog? You will likely find the same thing.

So my question to the Admins still stands.

Edit: In the client_state.xml file I found these 2 lines wich where inserted in this file during the Add Project process.

<scheduler_url>https://www.mlcathome.org/mlcathome_cgi/cgi</scheduler_url>
<scheduler_url>https://www.mldsathome.org/mlcathome_cgi/cgi</scheduler_url>

I checked on simular entrys for other projects and these have only 1 scheduler url entry.
There is possible an error in the Attach setup for the project that is send to the host.

If I am correct the Admins first have to fix the Attach setup and then everybody will need to detach en reattach to the project.

I don't think your are one of the Admins

You are right, I am not one of the Admins. By the way, as far as I know "the Admins" still is a single person and it's Sunday.

please don't give uninformed answers

If you have better information, which is not surprising since this is your problem, why not give it right away.

Have you checked your own host eventlog? You will likely find the same thing.

Oh, you're making uninformed guesses.

Edit: In the client_state.xml file I found these 2 lines wich where inserted in this file during the Add Project process.

<scheduler_url>https://www.mlcathome.org/mlcathome_cgi/cgi</scheduler_url>
<scheduler_url>https://www.mldsathome.org/mlcathome_cgi/cgi</scheduler_url>

Now that is interesting information. I could share some too, but since you're not talking to me anyway ...

If I am correct

... I'll respectfully wait for the relevant person(s) to show up and tell you that you're not completely correct.

https://www.mlcathome.org/mlcathome_cgi/cgi
https://www.mldsathome.org/mlcathome_cgi/cgi

How long ago did you join the project? For the first 2 or 3 weeks, there there was a misconfiguration that could have caused the second, erroneous scheduler url entry (my original name for the project was mlds at home, and I missed changing a name before I went live). But that's been fixed for some time, and a grep over the project dir for that string returns nothing. Could you try detatching/re-attaching to the project and seeing if that helps?

Thanks

<scheduler_url>https://www.mlcathome.org/mlcathome_cgi/cgi</scheduler_url>
<scheduler_url>https://www.mldsathome.org/mlcathome_cgi/cgi</scheduler_url>

How long ago did you join the project? For the first 2 or 3 weeks, there there was a misconfiguration that could have caused the second, erroneous scheduler url entry (my original name for the project was mlds at home, and I missed changing a name before I went live). But that's been fixed for some time, and a grep over the project dir for that string returns nothing. Could you try detatching/re-attaching to the project and seeing if that helps?

Thanks

I joined the project on 9-jul-2020 so I got the misconfiguration.

As asked I detached and reattached and after that there was no longer a second scheduler url.
The work fetch now gave no errors.
Thanks for the info.

PS @floyd I was correct there was a misconfiguration The only reason you did not had it is that you joined the project several weeks later than I did.

PS @floyd I was correct there was a misconfiguration The only reason you did not had it is that you joined the project several weeks later than I did.

I hope you're not trying to insult me by suggesting I don't know what I'm talking about. After you'd shown that second URL I would have agreed that this was probably the result of a misconfiguration, if I hadn't had the impression that you didn't care about my opinion at all. At the same point I could have shown where your conclusions were wrong and I still could do it. Save us that. I just want to make clear that I do understand where you were correct and I do understand where you were not. You wanted an official reaction, now you have one and that's it.