I hope! If anybody finds anything wrong with the upgrade today, please post in this thread, thanks!

---

Not quite sure- sorry, I\'m a noob. The thing is that my model trickled for the first time today and according to my BOINC the server was contacted successfully. That was half an hour ago and I don\'t see anything about that trickle under \"my results\". Nor did I get any credit. Is that normal or is something wrong?

Click update, that worked for me.

The trickle program runs twice a day, and the credits program once a day.

Okay, so it\'s normal that I have to wait. No problem then, thanks for explaining.

Okay, so it\'s normal that I have to wait. No problem then, thanks for explaining.

it could be a problem in that you seem to have received a workunit when there was a BOINC server bug that caused you to download hundreds of \"blank\" workunits (which you can see on your results page). can you type in what workunit name you are running, i.e. hadcm3oh_0j50_00002342 or similar.

I got that one afterwards, on the 16th when everything was up and running again- by contrast to the other 250 *lol*. So I hope there is no problem.
The name of the WU is hadcm3ohc_0b9p_05562964_0

Sorry for the server downtime today, I ended up redoing the database server to speed things up, so hopefully things are up now and back to normal if not faster!

Just wanted to get back saying everything is okay with my model. The trickle and credit finally arrived. Sorry for getting worried ;-) but as I said, I\'m all new to CPDN so be patient.

Trickle times are wrong by one hour now:

1. On 17 Oct, my latest trickle was listed as:
17 Oct 2006 03:02:27 474022 5386942 hadcm3lbm_c326_05333105_0 1 1,581,120 5,674,232 3.5887
now it is listed as:
17 Oct 2006 04:02:27 474022 5386942 hadcm3lbm_c326_05333105_0 1 1,581,120 5,674,232 3.5887

2. My latest trickle today is listed on the messages tab as:
20-10-2006 14:55:26|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
20-10-2006 14:55:26|climateprediction.net|Reason: To send trickle-up message
20-10-2006 14:55:26|climateprediction.net|(not requesting new work or reporting completed tasks)
20-10-2006 14:55:36|climateprediction.net|Scheduler request succeeded
but on the website as:
20 Oct 2006 13:55:51 474022 5386942 hadcm3lbm_c326_05333105_0 1 1,658,880 5,942,953 3.5825
which isn\'t correct as my time zone is +2 hours.

3. One of my results is listed as:
1141954 709423 23 Oct 2005 15:53:31 UTC 21 Nov 2005 15:35:24 UTC Over Success Done 2,382,215.30 6,805.26 6,805.26
while its last trickle is listed as:
21 Nov 2005 15:49:28 57923 1141954 08zf_200036695_1 3 259,248 2,382,213 3.0630
which looks like having occurred later.

---

Carl, et al,

Thank you for all your time on this project. The pages load nicely, the credits are again flowing, and the XML file has been updated. So all pieces are back in place, and it looks like we are back in production.

I hope now that this is closer to home, it\'s easier to maintain. I know remote administration is a headach in it\'s self. I applaud all who help run this project, and keep it a fun thing to keep coming back to.

I hope when (if) Climate Predicting does end, you people work on another project just as enjoyable as this one has been.

---

Hi, Alex,

Checked my record for HadSM3 Models and found a similar time offset as you note. Possibly something to do with logging the last Trickle (remember how small they were?) and not processing final Run information until the Uploads were finished and other server processes had time to do their thing. (Or, it could be something amiss with the way times are logged, then or now, perhaps [inadvertantly] using different rules in different parts of the bookkeeping.) Just a guess.

As to the first items mentioned, I\'ve long had an hour offset during Daylight Savings Time (as it\'s called in the US; BST, I think, in the UK [or just in England?]). The Time Zone parameter seems \"hard wired\" at Z-8 for my Time Zone. In fact, it\'s Z-7 for half of the year.

Don\'t know whether this is what you see or not but, because it has to do with bookkeeping/credits things on the boinc side, not the science side, I\'ve always dismissed it as a minor annoyance; it would probably be a major undertaking to construct a time adjustment table for everywhere on earth -- it would be tough enough just for the US.

[Edited for typo.]

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

I did some more research. I made copies of all my trickle results. Times were correct before the upgrade. Now they\'re different.

On http://climateapps2.oucs.ox.ac.uk/cpdnboinc/trickle.php?resultid=347418 the times from 23 to 30 October are one hour too high, but correct from 31 October to 23 November.

On http://climateapps2.oucs.ox.ac.uk/cpdnboinc/trickle.php?resultid=663068 they are correct from 24 to 26 March, but one hour too high from 27 March to 21 April.

So the times are correct for trickles uploaded during winter time, and wrong for trickles uploaded during summer time. In other words: what is displayed isn\'t UTC but UK local time.

---

As Carl initiated this Thread and asked for problem posts, I presume he\'ll see your posts, so I won\'t send an email to him at this time.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Anyone who received dozens, hundreds or even thousands (!) of phantom models on their results web pages during last week\'s work on the server (12-13 Oct) should read the last blue post here:

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=4963

---

Cpdn news

I wonder whether Carl has anticipated the UK clocks going back on Sunday 29 Oct. Maybe he has to adjust the time manually and is for once planning a non-working weekend.

---

Cpdn news

What I already expected did happen. Trickle times collected during summer time are wrong by one hour again, just like before winter time started.

---

With the new server upgrade, trickle times seem to be correct now.

---