| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: UD Windows Agent Support [Read Only]
Thread: Installer can't find .msi file |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
fredriley
Cruncher Joined: Feb 2, 2006 Post Count: 10 Status: Offline Project Badges: 
|
If you are able to perform secure transactioning in your web-browser, very probably port 443 is already activated. It's a question to find the web-browser settings and apply those. Firefox is set, in Tools |Options | Network | Settings to use http://wwwcache.nottingham.ac.uk/proxy.pac as the Automatic Proxy Configuration URL. However, UD Agent doesn't have a field for a proxy config, just for a proxy. Chances are that our university's proxy doesn't accept direct connections without going via the proxy config script. HTTPS is over port 443 btw, which is the channel the Agent uses outward to talk to the WCG servers. Did you try that port? I've tried it just now, both for the proxy and proxy script URLs, and no dice. I can't see that there are any other permutations to try, and we've all expended quite a few person-hours on this problem, so I think you'll just have to do without my miniscule contribution to WCG, at least when I'm at work :( - ta for trying anyhow. Cheers Fred |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Send an email to your sysadmins. University admins usually are quite fine answering questions like "How do I manually configure a proxy". Make sure you have checked your university computing FAQs and resources like that first.
Have you tried BOINC? One of the problems with UD is it uses port 443, but it doesn't use normal SSL, it uses a proprietary encryption scheme. Switching to BOINC sometimes solves problems, and allows us to troubleshoot better. Have you considered that your proxy may well require authorisation? Have you opened the proxy configuration file in a text editor and checked what it says? Sorry if any of these ideas have already been covered, but I thought I'd try to cover all the bases. |
||
|
|
fredriley
Cruncher Joined: Feb 2, 2006 Post Count: 10 Status: Offline Project Badges:
|
Thanks for the reply, and I do like the "Team Userfriendly" moniker :)
Send an email to your sysadmins. University admins usually are quite fine answering questions like "How do I manually configure a proxy". Make sure you have checked your university computing FAQs and resources like that first. I want to avoid that, not least because I've spent many hours on this already, and would prefer not to have to get into protracted negotiations with a paranoid (for there is no other sort ;-)) sysadmin wondering why I want to use a non-standard port. I'm not even sure who our sysadmin is, but when I've emailed our web team in the past for proper work issues they've been pretty brusque, not to say unhelpful, so I can't see them busting a gut over a non-work issue. Have you tried BOINC? Yep - see an earler post in this thread. I ran into exactly the same problem with the proxy script, posted to a support board, and got a reply along the lines of "BOINC always has problems with proxies" but with no suggested solution, so that was a few hours lost. Have you considered that your proxy may well require authorisation? Yes, but I don't know what it is, and don't want to hunt it down from our sysadmin (see above). Have you opened the proxy configuration file in a text editor and checked what it says? I'd not thought of that, so I've done that the noo, and it has a proxy IP and port of 128.243.220.20:3128 so I've tried that in UD Agent. There was a slight improvement, in that after "Analysing network" I got "Connecting to link server" which hadn't happened before, but after a couple of minutes the agent returned to the standard "agent paused" message. I've also tried that IP with port 443 - same result. Sorry if any of these ideas have already been covered, but I thought I'd try to cover all the bases. It's worth a try, and thanks, but I think I'll have to knock it on the head now, as I'm approaching the 'Concorde' point of no return where I'll have spent so much time trying to get it to work that to abandon the hunt for a solution would be to write off over 10 hours work, so I'd feel honour-bound to continue for as long as it takes, and it's really not worth it. Thanks to all for trying, anyhow. Cheers Fred |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If you want to take it to the next level, what you need to do is this:
First of all, switch back to BOINC. We can work out what is going on much better with BOINC, since some of us understand how the internals work, and there is loads more logging information available. UD is all proprietary, so if it doesn't work, we have to guess much of the time. You can turn on a load of extra debug flags in BOINC that will log extra information: http://boinc.berkeley.edu/trac/wiki/ClientMessages Use the IP and port you got from the config. If that doesn't work, try your normal domain credentials for the proxy username and password. That's what most proxys will use for authorisation. If that doesn't work, it's time to get Ethereal (or whatever they renamed it to - I forget). That will let you get a low level trace of the HTTP communications, and if you understand HTTP, hopefully you will be able to pinpoint the exact problem. If not, post the trace here: we should be able to help. I can probably give you some extra advice on using Ethereal if you get that far, so please ask if you find it as baffling as I did at first. |
||
|
|
fredriley
Cruncher Joined: Feb 2, 2006 Post Count: 10 Status: Offline Project Badges:
|
If you want to take it to the next level, what you need to do is this: First of all, switch back to BOINC. We can work out what is going on much better with BOINC, since some of us understand how the internals work, and there is loads more logging information available. UD is all proprietary, so if it doesn't work, we have to guess much of the time. You can turn on a load of extra debug flags in BOINC that will log extra information: http://boinc.berkeley.edu/trac/wiki/ClientMessages Use the IP and port you got from the config. A belated postscript to this - sorry, I've been too busy at work to put time aside for this. Anyway, I uninstalled the UD Agent and reinstalled BOINC, which as expected was initially unable to communicate with the server of the project I chose (proteins@home*). I then did as you suggested above, putting the proxy IP and port from my university's proxy config script into the BOINC prefs, and I nearly fell off my perch when it worked! So I can at last use my work machine for something useful, other than when I'm carrying out the useless crap I normally do at work ;-) Thanks to all for help and patience :) Cheers Fred * I did try to connect to WCG but BOINC reported a "HTTP internal server error" so maybe the server's feeling a bit poorly the now - I'll try it again in the future, honest |
||
|
|
|