Posts by Chas Woodhams

1) Message boards : Cafe SETI : Forum Disappearance (Message 874447)
Posted 10 Mar 2009 by Profile Chas Woodhams
Post:
..................................................









not a lot of news - well, basically nothing.




I emailed again - still waiting for a reply.


Keep watching
2) Message boards : Cafe SETI : Forum Disappearance (Message 869139)
Posted 24 Feb 2009 by Profile Chas Woodhams
Post:
I got this email reply:
________________________________________________________________

Hi Chas,

In the process of moving web hosts! Saving about £560 a year, just a few
glitches while databases are moved etc.

Jonathan
__________________________________________________________________

The "Locktons" site came up as "being rebuilt" but is now acting like an FTP host!

@Kenzie - PM me if you know anything else. Ta.


Dammid .......... hand shakes are starting again! Cooold turkey hell!

3) Message boards : Technical News : Pickup (May 11 2007) (Message 565440)
Posted 12 May 2007 by Profile Chas Woodhams
Post:
Hey, I'm slightly upset with this... Since the server breakdown, my average work done (or credit) has been going down at a very quick speed, and it's not fair!!! I don't want it to decrease, since it's not my fault and I was on a high average! Please, I want this solved!


The answer is to attach to some other projects. PrimeGrid is good for slower computers, because the WU's are relatively easy to process. I run this on my fast rig, and also on a much slower Celeron rig. Leiden
WU's seem to be anywhere from about 1/2 to about the same as SETI. With all the problems with SETI, I also added Einstein, though I would warn people that don't have reasonably fast computers, the WUs take about 25 times as long for my computer to process than SETI My computer is a single-core AMD 3700+ "San Diego", and it takes approximately 40 or 50 CPU hours to process one Einstein WU




I'm processing the same old WU this year on my clunky old Dell P4/350Mhz uni-core, for Climate Prediction (CPDN) ... 690 hours done / only 2700 to go! It's a great fall-back for times like these.

For what it's worth, I've switched SETI off (No new tasks) and I'll be leaving it off until Wednesday or Thursday, at the earliest .... my contribution to sparing the servers
4) Message boards : Technical News : Waiting Game (May 10 2007) (Message 565115)
Posted 11 May 2007 by Profile Chas Woodhams
Post:
Should something about this be put on the home page?


I think this is a good idea. It would probably do a lot of good to announce new versions right on the home page so everyone knows.


Which Home page

When did you last take a look at the BOINC Home page ... that is the only appropriate place for that info. I agree, it would be helpful if "they" (the BOINC team) posted the latest version (link) there.

The SETI forums are not the best place to discuss general BOINC things and this particular forum is actually about Matt keeping the crunchin'grunts (you, me and us) up to date on the can-of-worms-opening-and-labelling project {for which, much thanks}
5) Message boards : Technical News : On the Horizon (May 07 2007) (Message 563760)
Posted 9 May 2007 by Profile Chas Woodhams
Post:
So long and thanks for all the fish.


Don't Panic...make sure you know where your towel is... ;-)

Hi,
what happened to trillian?
If she's dissappeared are the mice responsible???

hmmm


42



What is the meaning of life, the universe and everything?


Meet you all at "The Restaraunt at the end of the Universe"


Here's an appropriate Douglas Adams quote:

"New Technology" is the name we give to "stuff that doesn't work yet".
6) Message boards : Technical News : Slowly Approaching... (May 08 2007) (Message 563758)
Posted 9 May 2007 by Profile Chas Woodhams
Post:
I thought we might enjoy a quick communal sing-song: are we ready...all together now...

Fly me to the moon...let me play among the stars.
Let me see what life is like
on Jupiter and Mars

Aaah Thenkyoo

I will see your Fly me and raise you ..

Its cold outside,
There's no kind of atmosphere,
I'm all alone,
More or less.
Let me fly,
Far away from here,
Fun, fun, fun,
In the sun, sun, sun.



How about '2000 light years from home' by the Strolling Bones?


.... and for us oldies, dig out the early Pink Floyd vinyls and ....

Set the Controls for the Heart of the Sun
7) Message boards : Technical News : Unusual suspects (Feb 06 2007) (Message 514588)
Posted 7 Feb 2007 by Profile Chas Woodhams
Post:


Until you've opened a can of worms, you have no idea that there are worms in the can ... ignorance is never a good excuse

Keep up the good work.
8) Message boards : Cafe SETI : The last Person to post Wins Part Nine Closed! (Message 476654)
Posted 8 Dec 2006 by Profile Chas Woodhams
Post:
Who's winning now?


Ooooooh! Me!!!!!!!!!
9) Message boards : Cafe SETI : The last Person to post Wins Part Nine Closed! (Message 475740)
Posted 7 Dec 2006 by Profile Chas Woodhams
Post:
... leaving me, the winner
10) Message boards : Cafe SETI : Pop your clogs...English/Yanklish/Aussie translations (Message 471174)
Posted 3 Dec 2006 by Profile Chas Woodhams
Post:
OK... here's another one.

When witnessing something great, such as a remarkable goal or (Unlikely) a pay rise, an Aussie will say: "You ripper!"

Is there an equivalent expression in UK English or Yanklish? There has to be.

you pass out as it is on par with a miracle

The "Lanky" (Lancashire dialect) equivalents of "ripper" are "crackin'" and "belter"/"beltin'" (omitting the terminal-G is mandatory ;-) )

Sammie's "pass out" has a double emaning:
1. Graduation from a military academy like Sandhurst (not the US school type).
2. Fainting.
So, .... after a long day on parade, it has been known for Sandhurst graduates to pass out before they have passed out
11) Questions and Answers : Windows : No new downloads (Message 396541)
Posted 13 Aug 2006 by Profile Chas Woodhams
Post:
Thanks guys,

Unfortunately, not too sure you have the cause ...

The real time split between CPDN and SETI has been 1:2 (respectively); LHC has obviously been at zero for an age.

The prefs split is CPDN : SETI : LHC - 200 : 500 : 500.

By my simple minded maths, SETI is underprocessing by 30 minutes in any given 3 hour period.



So, where next?
12) Questions and Answers : Windows : No new downloads (Message 396361)
Posted 13 Aug 2006 by Profile Chas Woodhams
Post:
When all current WU's have completed and uploaded and reported ... NOTHING downloads

Other projects:
- CPDN, 1 wu, running, deadline sometime in the next millenium.
- LHC, out of work for over a month (or is it two?).

Prefs set to "3 days" (to allow for weekend downtime). "global_prefs_NOToverride.xml" (i.e. no overrides).

This problem keeps coming back - it will only go away +/- 6hrs after Reseting project; and then it downloads everything.

Happened in v. 5.4.9 and still happens in v. 5.4.11

Any thoughts would be appreciated.
13) Message boards : Number crunching : Firefox Extension: BOINC Stats (Message 324020)
Posted 2 Jun 2006 by Profile Chas Woodhams
Post:
BOINC Stats v0.2.3 has been approved and is now available on the Firefox add-ons site.

This is the same version as has been available on the mozdev site since May 18th.



Detected and updated ... thanks
14) Message boards : Number crunching : Firefox Extension: BOINC Stats (Message 323117)
Posted 2 Jun 2006 by Profile Chas Woodhams
Post:
@ tekwyzrd
Thanks for that .... it ain't me (for once) ;-)

I'll hold back on getting it direct and let you know if the change works (and when) - sometime next week... maybe?
15) Message boards : Number crunching : Firefox Extension: BOINC Stats (Message 322239)
Posted 1 Jun 2006 by Profile Chas Woodhams
Post:
BOINC Stats v0.2.3 is available on the mozdev server and awaiting approval from the Mozilla Add-ons site. No major changes in functionality but I have tested it with Firefox v2.0a2 (Bonecho) and v3.0a1 (Minefield) and increased the max version to 3.0 . If you are running a version of Firefox that refuses to allow installation please let me know.

Running Firefox 1.5.0.3 with XP-SP1 +fixes and BOINC Stats 0.2.2.1 (re-installed from FF-Extensions, way back when ... )

Still no sign of an update being found by FF.

Is it me or Mozilla?
16) Message boards : Number crunching : CLOSED - SETI/BOINC Milestonesâ„¢ VII - CLOSED (Message 288097)
Posted 23 Apr 2006 by Profile Chas Woodhams
Post:
OMG! How did I get to be U-O-T-D????
What next ... did I win last night's Lottery????

What criterion/criteria is/are used to pick the U-O-T-D ... can't be anything to do with super-crunching.





17) Message boards : Number crunching : Firefox extension: SAH Userstats (Message 242960)
Posted 5 Feb 2006 by Profile Chas Woodhams
Post:
@ whoever ... if anybody is picking up the pieces ;-)

Glitch/bug report:
when I select LHC@Home on the right-click,I get "Data Unavailable".
However, Siran's (wonderful) Projects News Site shows LHC as "Online" and when I go to My Account on LHC, I can see my data is OK.

This may be down to LHC being "Out of work" - but, hey, what do I know?
18) Questions and Answers : Windows : dial-up problems (Message 231405)
Posted 15 Jan 2006 by Profile Chas Woodhams
Post:
Hi, All,

Basically - NO PROGRESS!

Run ...and... Network activity based on preferences - but the actual activity looks like this:

BOINC Messages

15/01/2006 01:13:50|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
15/01/2006 02:37:51||request_reschedule_cpus: process exited
15/01/2006 02:37:51|LHC@home|Computation for result woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2 finished
15/01/2006 02:37:51|SETI@home|Restarting result 05oc03ab.24335.8001.492326.1.24_3 using setiathome version 418
15/01/2006 02:37:53|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:37:55||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:37:55|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:37:55|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:38:55|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:38:55||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:38:56|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:38:56|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:39:56|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:39:56||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:39:57|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:39:57|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:40:57|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:40:57||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:40:58|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:40:58|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:41:58|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:41:58||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:41:59|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:41:59|LHC@home|Backing off 2 minutes and 20 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:44:20|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:44:20||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:44:21|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:44:21|LHC@home|Backing off 2 minutes and 18 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:46:40|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:46:40||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:46:41|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:46:41|LHC@home|Backing off 17 minutes and 53 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:52:13||request_reschedule_cpus: process exited
15/01/2006 02:52:13|SETI@home|Computation for result 05oc03ab.24335.8001.492326.1.24_3 finished
15/01/2006 02:52:14|SETI@home|Starting result 05se04aa.9555.23298.17324.1.1_2 using setiathome version 418
15/01/2006 02:52:16|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:52:16||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:52:17|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:52:17|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:53:17|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:53:17||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:53:18|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:53:18|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:54:18|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:54:18||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:54:19|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:54:19|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:55:19|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:55:19||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:55:20|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:55:20|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:56:20|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:56:20||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:56:21|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:56:21|SETI@home|Backing off 2 minutes and 8 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:58:30|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:58:30||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:58:31|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:58:31|SETI@home|Backing off 5 minutes and 5 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:03:37|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:03:37||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 03:03:38|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 03:03:38|SETI@home|Backing off 7 minutes and 26 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:04:36|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 03:04:36||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 03:04:37|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 03:04:37|LHC@home|Backing off 27 minutes and 42 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 03:11:05|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:11:05||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 03:11:06|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 03:11:06|SETI@home|Backing off 12 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:23:07|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:23:07||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 03:23:08|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 03:23:08|SETI@home|Backing off 36 minutes and 52 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:32:20|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 03:32:20||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 03:32:21|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 03:32:21|LHC@home|Backing off 1 hours, 38 minutes, and 56 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 04:00:01|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:00:01||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 04:00:02|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 04:00:02|SETI@home|Backing off 19 minutes and 25 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:19:28|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:19:28||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 04:19:29|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 04:19:29|SETI@home|Backing off 53 minutes and 36 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:52:14|climateprediction.net|Restarting result sulphur_g69o_000754620_0 using sulphur_cycle version 422
15/01/2006 04:52:14|SETI@home|Pausing result 05se04aa.9555.23298.17324.1.1_2 (removed from memory)
15/01/2006 04:52:15||request_reschedule_cpus: process exited
15/01/2006 04:52:20|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:52:20|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:52:20|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:52:20||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:52:25|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:52:25|climateprediction.net|No schedulers responded
15/01/2006 04:53:25|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:53:25|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:53:25|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:53:26||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:53:30|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:53:30|climateprediction.net|No schedulers responded
15/01/2006 04:54:31|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:54:31|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:54:31|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:54:31||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:54:36|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:54:36|climateprediction.net|No schedulers responded
15/01/2006 04:55:36|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:55:36|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:55:36|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:55:37||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:55:41|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:55:41|climateprediction.net|No schedulers responded
15/01/2006 04:56:41|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:56:41|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:56:41|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:56:42||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:56:46|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:56:46|climateprediction.net|No schedulers responded
15/01/2006 04:58:36|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:58:36|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:58:36|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:58:37||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:58:41|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:58:41|climateprediction.net|No schedulers responded
15/01/2006 05:02:06|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 05:02:06|climateprediction.net|Reason: To send trickle-up message
15/01/2006 05:02:06|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 05:02:07||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 05:02:11|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 05:02:11|climateprediction.net|No schedulers responded
15/01/2006 05:10:27|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 05:10:27|climateprediction.net|Reason: To send trickle-up message
15/01/2006 05:10:27|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 05:10:27||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 05:10:32|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 05:10:32|climateprediction.net|No schedulers responded
15/01/2006 05:11:18|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 05:11:19||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 05:11:19|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 05:11:19|LHC@home|Backing off 3 hours, 49 minutes, and 51 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 05:13:06|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 05:13:07||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 05:13:07|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 05:13:07|SETI@home|Backing off 2 hours, 13 minutes, and 11 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 05:40:47|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 05:40:47|climateprediction.net|Reason: To send trickle-up message
15/01/2006 05:40:47|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 05:40:48||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 05:40:52|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 05:40:52|climateprediction.net|No schedulers responded
15/01/2006 06:52:15|climateprediction.net|Pausing result sulphur_g69o_000754620_0 (removed from memory)
15/01/2006 06:52:18|LHC@home|Starting result woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4 using sixtrack version 467
15/01/2006 06:52:22||request_reschedule_cpus: process exited
15/01/2006 07:01:06|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 07:01:06|climateprediction.net|Reason: To send trickle-up message
15/01/2006 07:01:06|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 07:01:07||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 07:01:11|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 07:01:11|climateprediction.net|No schedulers responded
15/01/2006 07:26:19|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 07:26:19||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 07:26:20|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 07:26:20|SETI@home|Backing off 1 hours, 50 minutes, and 21 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 08:35:55||request_reschedule_cpus: process exited
15/01/2006 08:35:55|LHC@home|Computation for result woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4 finished
15/01/2006 08:35:55|SETI@home|Restarting result 05se04aa.9555.23298.17324.1.1_2 using setiathome version 418
15/01/2006 08:35:57|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:35:58||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:35:58|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:35:58|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:36:58|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:36:59||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:36:59|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:36:59|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:37:59|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:38:00||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:38:00|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:38:00|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:39:00|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:39:01||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:39:01|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:39:01|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:40:01|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:40:02||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:40:02|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:40:02|LHC@home|Backing off 2 minutes and 12 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:42:15|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:42:16||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:42:16|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:42:16|LHC@home|Backing off 3 minutes and 41 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:45:58|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:45:59||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:45:59|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:45:59|LHC@home|Backing off 3 minutes and 30 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:49:30|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:49:31||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:49:31|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:49:31|LHC@home|Backing off 42 minutes and 47 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:01:11|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 09:01:11||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 09:01:12|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 09:01:12|LHC@home|Backing off 2 hours, 35 minutes, and 35 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 09:10:15|SETI@home|Result 05se04aa.9555.23298.17324.1.1_2 exited with zero status but no 'finished' file
15/01/2006 09:10:15|SETI@home|If this happens repeatedly you may need to reset the project.
15/01/2006 09:10:15||request_reschedule_cpus: process exited
15/01/2006 09:10:15|SETI@home|Restarting result 05se04aa.9555.23298.17324.1.1_2 using setiathome version 418
15/01/2006 09:16:41|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:16:42||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 09:16:42|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 09:16:42|SETI@home|Backing off 36 minutes and 22 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:32:19|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:32:20||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 09:32:20|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 09:32:20|LHC@home|Backing off 26 minutes and 17 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:43:21|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 09:43:21|climateprediction.net|Reason: To send trickle-up message
15/01/2006 09:43:21|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 09:43:21||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 09:43:26|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 09:43:26|climateprediction.net|No schedulers responded
15/01/2006 09:44:26|climateprediction.net|Fetching master file
15/01/2006 09:44:26||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:44:31|climateprediction.net|Master file fetch failed
15/01/2006 09:44:31|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:45:31|climateprediction.net|Fetching master file
15/01/2006 09:45:31||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:45:36|climateprediction.net|Master file fetch failed
15/01/2006 09:45:36|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:47:01|climateprediction.net|Fetching master file
15/01/2006 09:47:01||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:47:06|climateprediction.net|Master file fetch failed
15/01/2006 09:47:06|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:49:26|climateprediction.net|Fetching master file
15/01/2006 09:49:26||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:49:31|climateprediction.net|Master file fetch failed
15/01/2006 09:49:31|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:53:06|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:53:06||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 09:53:07|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 09:53:07|SETI@home|Backing off 53 minutes and 54 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:58:38|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:58:38||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 09:58:39|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 09:58:39|LHC@home|Backing off 58 minutes and 28 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 10:05:01|climateprediction.net|Fetching master file
15/01/2006 10:05:01||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 10:05:06|climateprediction.net|Master file fetch failed
15/01/2006 10:05:06|climateprediction.net|Too many backoffs - fetching master file



Corresponding Modem Log, as at 10:24 15/01/2006

01-15-2006 01:25:59.984 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-15-2006 01:25:59.984 - Initializing modem.
01-15-2006 01:26:00.000 - Send: AT<cr>
01-15-2006 01:26:00.000 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.000 - Interpreted response: OK
01-15-2006 01:26:00.000 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
01-15-2006 01:26:00.156 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.156 - Interpreted response: OK
01-15-2006 01:26:00.171 - Send: ATS7=120L1M0+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
01-15-2006 01:26:00.187 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.187 - Interpreted response: OK
01-15-2006 01:26:00.187 - Waiting for a call.
01-15-2006 01:26:00.203 - Send: at+vcid=1<cr>
01-15-2006 01:26:00.218 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.218 - Interpreted response: OK
01-15-2006 01:26:00.234 - Send: ATS0=0<cr>
01-15-2006 01:26:00.250 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.250 - Interpreted response: OK
01-15-2006 01:26:00.250 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
01-15-2006 01:26:00.250 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
01-15-2006 01:26:00.250 - TSP Completing Async Operation(0x000100c6) Status 0x00000000
01-15-2006 01:26:00.250 - TSP(0000): Dropping Call
01-15-2006 01:26:00.250 - TSP Completing Async Operation(0x000100d7) Status 0x00000000
01-15-2006 01:26:00.250 - TSP(0000): Closing Call
01-15-2006 01:26:00.250 - Session Statistics:
01-15-2006 01:26:00.250 - Reads : 30 bytes
01-15-2006 01:26:00.250 - Writes: 99 bytes

When I manually connected and hit the "Retry communications" option, everything cleared.

Secondary problem:
On the odd occassion BOINC does dial-out, comms are initiated before connection is made; errors ensue; as soon as connection completes, BOINC disconnects!!

Not a lot of help.
19) Questions and Answers : Windows : dial-up problems (Message 227968)
Posted 8 Jan 2006 by Profile Chas Woodhams
Post:
Ageless,

Thanks for your thoughts.

I have (always) disabled the XP Firewall - just don't trust Microsoft.

Because of the shut-downs at Berkley, followed by the one on CPDN, I have not been able to do any real testing - doing manual control dial-up and start BOINC access a couple of times a day! Otherwise, my messages would be a sea of red (and give me a bigger headache ;-) ).

I'll come back with more, later in the week.
20) Questions and Answers : Windows : dial-up problems (Message 225146)
Posted 3 Jan 2006 by Profile Chas Woodhams
Post:
Well, if you are on dialup, you better should use the setting "Use my Dial-up ..." instead of the automatic detection. It is told that the detection does not work quite well if mutiple network devices are installed.

Had it on "Use my Dial-up..." for a while with similar success - that's why I changed to "Auto..." - so that's not the reason/answer.

Besides that: does the firewall REALLY allow connects from boinc.exe via port 80 to any internet host address?

Unless ZoneAlarm is lying (always possible), all BOINC programs have access - so, no joy there, either.

Sorry for being so negative but if it ain't the answer, it ain't the answer


Next 20


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.