| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Scheduler request failed: Failure when receiving data from the peer |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 14
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This may be the same libCurl + Squid + NTLM auth problem we have seen before. I'm afraid it is beyond our power to fix, but a workaround is to use a local forwarding proxy as an intermediary.
|
||
|
|
Pienasola
Cruncher Joined: Feb 8, 2007 Post Count: 7 Status: Offline |
libCurl + Squid + NTLM auth problem ???
How do I use a local forwarding proxy? Thanks Leo |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
Just to give folks an update on the NTLM auth problem. We are working right now on nailing down exactly where the problem is. It is not clear if it is due to the underlying libCurl package or if BOINC needs to set the libCurl environment up properly. I spent a few days before the holidays digging deep into this and handed it over to the BOINC devs. They didn't get any further so I will be getting deep into this again (as one of our top priorities).
If there are any libCurl experts out there who have some time to dig into the BOINC code and libCurl to help us figure out what is going on that would be awesome! This isn't for the fainthearted though...... |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
Good news on the NTLM front. We have been working with the libCurl team to resolve this issue and there has been some good progress.
We will be releasing a new version of the client in the next 2-3 weeks that will support NTLM authentication. At the moment there will still be one problem that will require a workaround the user must do (i.e. manually set a flag in the cc_config.xml file). We are continuing to work to eliminate the workaround and hope to have that resolved in the next day or two. If we cannot get it resolved quickly, then we will go ahead and have the BOINC team go ahead and release a version of the client for testing that will allow NTLM to at least work with this workaround. Then in some future release we can hopefully fix the problem in its entirety so that NTLM auth will work automatically. |
||
|
|
|