climateprediction.net home page
Posts by old_user9685

Posts by old_user9685

21) Questions and Answers : Windows : 4.19 \"No schedulers responded\" behind http proxy (Message 9463)
Posted 17 Feb 2005 by old_user9685
Post:
> I have switched on the http and netxfer debugging, and a portion of the log is

I'd turn off the netxfer for the moment, as it generates a lot of output making the rest a bit hard to see.

> pasted below - hope this is useful, it doesn't reveal anything at all to me. I
> can't see any reference to the proxy - so is Boinc simply not trying to use
> the proxy? In terms of client, this is running on XP SP2.

Nope, BOINC is using the proxy, but in an invisible kind of way. The proxy's details do not get written to the log file, only the destination details are logged using this flag.

Ok, here's a bit of explanation of what's happening:

Client sends a request to the scheduler (via your proxy):

> 2005-02-17 12:44:23 [climateprediction.net] Sending request to scheduler:
> http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi

Here's the HTML that was written in an HTML POST format:

> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header: POST http://climateapps2.oucs.ox.ac.uk:80/cpdnboinc_cgi/cgi HTTP/1.0
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header: Pragma: no-cache
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header: Cache-Control: no-cache
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header: Host: climateapps2.oucs.ox.ac.uk:80
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header: Connection: close
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header: Content-Type: application/octet-stream
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header: Content-Length: 5638
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): request
> header:
> 2005-02-17 12:44:25 [DEBUG_HTTP ] HTTP_OP_SET::poll(): finished
> sending request body

And here's the reply from the scheduler:

> 2005-02-17 12:44:27 [DEBUG_HTTP ]
> HTTP_REPLY_HEADER::read_reply(): header: HTTP/1.0 200 OK
> 2005-02-17 12:44:27 [DEBUG_HTTP ]
> HTTP_REPLY_HEADER::read_reply(): header: Date: Thu, 17 Feb 2005 12:42:13 GMT
> 2005-02-17 12:44:27 [DEBUG_HTTP ]
> HTTP_REPLY_HEADER::read_reply(): header: Server: Apache/2.0.50 (Unix)
> PHP/4.3.8
> 2005-02-17 12:44:27 [DEBUG_HTTP ]
> HTTP_REPLY_HEADER::read_reply(): header: Content-Type: text/plain
> 2005-02-17 12:44:27 [DEBUG_HTTP ]
> HTTP_REPLY_HEADER::read_reply(): header: Content-Length: 799
> 2005-02-17 12:44:27 [DEBUG_HTTP ]
> HTTP_REPLY_HEADER::read_reply(): header:

Up to this point, I can confirm that your client is indeed talking to the scheduler via your proxy and is receiving a reply.

We'd need to see more data from your log file to understand where the failure is occuring.

Thx
22) Questions and Answers : Windows : 4.19 \"No schedulers responded\" behind http proxy (Message 9452)
Posted 17 Feb 2005 by old_user9685
Post:
> > Is there any other information I can provide to help?

A couple more questions.
Which Windows operating system is the client that is not working installed on?
Which BOINC version did you upgrade from?

TIA
23) Questions and Answers : Windows : 4.19 \"No schedulers responded\" behind http proxy (Message 9451)
Posted 17 Feb 2005 by old_user9685
Post:
> Thanks for your very swift reply...

No prob, but can't always promise it'll be that way. ;-)

> The proxy server is Novell BorderManager 3.7 - and I'm the IT Manager - so you

ok.

> Is there any other information I can provide to help?

Are you in a position to capture the network packets being sent between the host and the proxy?
If so, then you could examine the data part of the packet and see what reply is being returned to the host from the proxy.
If not, (and maybe less complicated :) you can turn on logging in the BOINC client. This page <a href="http://boinc.berkeley.edu/client_debug.php">Core client: debugging</a> describes how to set up a file called log_flags.xml and what debugging options are available. <b>Note:</b> You need to stop and start the client after creating the flags file, in order for the client to detect the debugging info.

There are quite a few debugging options and lots of data can be generated. I would suggest starting with &lt;http_debug/&gt;. The debug data will be in the stdout.txt file in your BOINC folder. You won't see it in the messages tab of the client. There's a size limit on the stdout.txt file, so if you leave the log_flags active for too long, the stdout file can wrap and useful data can be lost.

It's not necessary (nor advisable) for you to post the entire contents of the stdout.txt file here, but have a look for the http_debug sections and see if anything there makes sense and post the useful details. If not, we can work out a means for you to send the stdout file to either myself of one of the devs, so that we can examine it.
24) Questions and Answers : Windows : 4.19 \"No schedulers responded\" behind http proxy (Message 9448)
Posted 17 Feb 2005 by old_user9685
Post:
Hi Richard

The BOINC dev team are trying to track down exactly what's going on with these proxy problems.

Can you please advise which proxy application you're using and as much other technical detail as possible?

Please use caution regarding the tech details and please don't post anything that you feel might compromise your security. Feel free to post excerpts from message logs, but you can hash out specifics that might be compromising.
e.g.
Internal IP of proxy = 192.1.1.1
Hostname of proxy = ####.ox.ac.uk

Thanks
25) Message boards : Number crunching : Why doesn\'t BOINC work? (Message 8989)
Posted 9 Feb 2005 by old_user9685
Post:
&gt; How do I check the events viewer? I have run memtest on the computer which
Right click "my computer" and select manage. This will open a Microsoft Management Console.
Navigate to "System Tools-&gt;Event Viewer" and expand it.
Browse through "Application" and "System", looking for events with a red circle and white X. These are errors. Compare the date and time to those times when you installed the software, ran excel (and it caused the reboot), and when the computer restarted.

A thorough explanation of the event viewer is beyond this thread, however you would be well advised to learn a bit about it, if you intend to continue in a Microsoft environment.

&gt; times, which presumably means it has been installed at different places on the
&gt; hard drive.
If you have never checked the drive, you ought to check it sometime anyway.
26) Message boards : Number crunching : Are you using AnalogX proxy? (Message 8840)
Posted 7 Feb 2005 by old_user9685
Post:
Hi there

Sorry about posting this off topic for this board, but I'm trying to reach a wider audience.

If you're using AnalogX proxy, or know someone that does, please visit this thread <a href="http://setiweb.ssl.berkeley.edu/forum_thread.php?id=11410">here</a> in the SETI@home forums.

Again, sorry for the intrusion.
27) Message boards : Number crunching : Why doesn\'t BOINC work? (Message 8839)
Posted 7 Feb 2005 by old_user9685
Post:
&gt; (and perhaps other programs of this suite). However, once Excel has run,
&gt; BOINC cause the computer to reboot everytime the computer has finished
&gt; booting.

Could you tell us the version of BOINC that you installed, and also the operating system that you are using?

I have to admit that I'm surprised that the computer gets stuck in a reboot cycle.
Presuming XP/2000/NT, does it reboot after you've logged in?
Did you try to install as a service?
Are there any events in event viewer that might explain what is happening when your computer starts?
Have you tried checking your disk for errors? It may be that the application is installed into a bad sector.
28) Message boards : Number crunching : BOINC 4.19 (Message 8519)
Posted 3 Feb 2005 by old_user9685
Post:
&gt; No problem if you're only running one machine but more than a little
&gt; irritating when you're updating a 'farm'...

I'm reminded of those owners of flashy sports cars that grumble when they get the bill for a service... ;-)
29) Message boards : Number crunching : BOINC 4.19 (Message 8427)
Posted 2 Feb 2005 by old_user9685
Post:
&gt; Agree - BOINC 4.62 seems to be better in terms of directory structure.

FYI
A prerequisite to installing the later versions (4.5x &amp; 4.6x) is an uninstall of the older client. The uninstall removes the language folders.
30) Message boards : Number crunching : Can I gracefully leave? (Message 7881)
Posted 28 Jan 2005 by old_user9685
Post:
&gt; You can also in the General Preferences change <b>Connect to network about
&gt; every x days</b> to zero days. Of course, you will not download nothing of
&gt; other projects if you have them.

This would be the logical method, but when I've tried this method in the past, the client often still requests at leaset 1 second of work (per cpu). So in CPDN's case I could end up with 2 * 2 months of work on an HT box.

That's the reason why I advocate the Leave at least setting.
31) Message boards : Number crunching : Can I gracefully leave? (Message 7879)
Posted 28 Jan 2005 by old_user9685
Post:
&gt; time. Sorry, couldn't remember who wrote it or I would have just pointed to
&gt; it. Thanks.

LOL, I feel secure in my obscurity. :)
32) Message boards : Number crunching : Can I gracefully leave? (Message 7704)
Posted 27 Jan 2005 by old_user9685
Post:
&gt; I want to quit crunching ClimatePrediction after my current two WU are up. Is
&gt; there a way to not download new WU after I upload the results of my current
&gt; ones? Otherwise I will be sitting on two WU that will never get done by me.

I wrote a little bit about this in another thread.
Have a look here: <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=1282#6212">Decommissioning a machine</a>

If anything is not clear, feel free to post your queries.
33) Message boards : Number crunching : BOINC 4.14 (Message 7332)
Posted 17 Jan 2005 by old_user9685
Post:
&gt; I resource share CPDN 52.5%, Pred 30.8% and SAH 16.7% on my computer. Will
&gt; V4.14 make things go horribly wrong with any of those projects if I install
&gt; it?
&gt;
&gt; I hear that it screws cpdn. Does this mean that if I don't upgrade then I
&gt; will not get Pred wu's?

I don't recall seeing it being mandatory anywhere, but since the topic spans multiple discussion areas it's probable that I could have missed something. Should it become mandatory, you would (should?) be advised via the project-to-client communication mechanism.

So far, I have seen more good reports for CPDN &amp; 4.14 than bad ones.

IMHO, right now the decision to upgrade really rests with the individual. If you're a long way into a CPDN wu and would rather not risk losing many hours of work, it would be unwise to upgrade simply for the sake of upgrading.

I also just checked and found that 4.14 has been pulled from the official <a href="http://boinc.berkeley.edu/download.php">Download BOINC client software</a> page. Not quite sure what to read into that tho.

&gt; Live long and crunch!
If only my system could live as long as I intend to... ;)
34) Message boards : Number crunching : BOINC 4.14 (Message 7287)
Posted 14 Jan 2005 by old_user9685
Post:
&gt; Interesting. Does that mean that ver 4.5x is likely to be significantly
&gt; delayed?

The 4.14 release is to fix a bug that is serious enough to warrant a new release in the public source tree. As previously noted, it really only affects the users for some other projects, because of the specific way that these projects handle data. The two projects involved are still in Alpha status, so if you're not involved in them, it's not likely you'd need to upgrade at this point.

The same fix has been incorporated into the development (4.x) tree.

The two trees are reasonably independent, thus it's not likely that there will be any delay in the 4.x release. Well, not as a result of this bugfix anyway.
35) Message boards : Number crunching : BOINC 4.14 (Message 7286)
Posted 14 Jan 2005 by old_user9685
Post:
&gt; has anyone at CPDN tried it yet?
&gt; I noticed that the new download has yet to appear on the SETI download page.

One user has already reported a CPDN WU error out, after upgrading to 4.14.

You'd be wise to give it a few days, otherwise tread with caution....
36) Questions and Answers : Windows : Upgrade to 4.13 (Message 6544)
Posted 4 Dec 2004 by old_user9685
Post:
I wrote a little bit about this in another thread.
Have a look here: <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=1282#6212">Decommissioning a machine</a>

If anything is not clear, feel free to post your queries.
37) Message boards : Number crunching : Forums Should Be OK Now (Message 6345)
Posted 24 Nov 2004 by old_user9685
Post:
Is it just me, or is the "Jump to first new post in thread automatically" preference being ignored on the message forums?
38) Questions and Answers : Windows : Decommissioning a machine (Message 6293)
Posted 21 Nov 2004 by old_user9685
Post:
&gt; Thanks for all your help folks. I'm trying the "Leave At Least" technique. I
&gt; believe I've now successfully convinced the machine in question to leave 500

You can always check this by going to the disk tab and reviewing your 'BOINC free space' setting. It should be 0 while trying this technique.

&gt; GB, taken it back off line and restored my preferences to 'proper' values for
&gt; my other BOINC machine. Now I just have to wait for the model finish...

Please don't forget to set it to 500GB <i>before</i> you enable network access on the machine in question, otherwise during the course of the upload (which can take a bit of time) it may send a scheduler request, get your non-restrictive settings and start downloading another CPDN wu.

Good Luck.
39) Questions and Answers : Windows : Decommissioning a machine (Message 6212)
Posted 18 Nov 2004 by old_user9685
Post:
I find that using <b>Leave at least</b> instead of <b>Use no more than</b> is an easier option.

Set it to a ridiculous figure (500GB) and when BOINC requests more work (which can occur a few days before your current model is uploaded, depending on your <b>Connect to network about every</b> setting) you will see a message along the lines of "Message from server: No work available (there was work but you don't have enough disk space allocated)"

I have never seen the <b>Leave at least</b> setting have any impact on running projects. It only affects the client when it tries to obtain new work.

Your current model should be uploaded without any problem. (If they can get that Swiss server running again, but that's another story...)

Make sure that you update your CPDN project from the client so that the new preferences are applied, before it requests more work.

I would suggest the following approach:
a.) Change your general prefs <b>Leave at least</b> setting to a value higher than the disk space on your system.
b.) As soon as the update has been confirmed on the server, perform a project update from the client in question.
When you see the message:
General prefs: from CPDN (last modified YOURDATE YOURTIME)
in your messages tab, disable network access on that client.
c.) Change your general prefs <b>Leave at least</b> setting back to your normal setting.
d.) Wait until the climate model has completed.
e.) Go back to step a.) but enable network access in step b.) instead of disabling it.

Once you've enabled the network access the model will upload and BOINC will not request any more work from CPDN.
Once the upload has completed successfully, detach from CPDN.

This assumes that you're only running one project on that host. If not, you could follow these steps for each project, detaching from each one once you've completed their uploads.

If you are running any other projects, you can experiment by changing the settings on another project, since they all have short running WU's.

<i>Just don't forget to set the <b>Leave at least</b> setting back to normal after you've updated the client, otherwise your other projects/hosts will be affected.</i>

Kind Regards
40) Questions and Answers : Windows : Which firewall ports do I need open to send back results? (Message 6065)
Posted 12 Nov 2004 by old_user9685
Post:
Port 80 should be open for TCP protocol, however if you are returning results to other projects, this is probably not your problem.

There is another thread here discussing current upload problems, reason being a server that is down for maintenance.

I'd suggest that you follow that thread, and once other people report that they can again successfully upload, you should retry your own upload.

[edit]
a link to the <a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=1208">thread</a> just for easier click through.
[edit/]


Previous 20 · Next 20

©2024 climateprediction.net