Weã¢â‚¬â„¢re Sorry but There Was an Error Processing Your Request Please Try Again Later

Writer Message
Profile cereus
Send message
Joined: 16 May 99
Posts: 6
Credit: 190,644
RAC: 0
United States

Bulletin 691297 - Posted: fourteen December 2007, 4:44:44 UTC

My account summarizes below:

SETI@domicile member since sixteen May 1999
SETI@home classic workunits 3,147
SETI@home archetype CPU time 60,350 hours

I registered with BOINC when it became available 2 or three years ago. I ran it for a couple of months, but it didn't seem to be producing results. I stopped participating for nearly a year considering I kept getting error messages (like the ones shown in the many lines below).

Then I tried a second time; I ran a couple of months; and stopped again because of error messages like below.

This is my tertiary try to go BOINC operational,
BUT
what I am getting is an error message that go along recurring.
I have flagged the error message down about xx inches into all the verbiage that follows.
It is flagged between lines of dashes, like this: ------------ etc.
I use to stand for with SETI and they'd reply questions.
But with BOINC, I've non establish how to get answers yet.
Can anyone advise me on the questions I raise about a foot downward, located between the lines of dashes?

What follows is the Messages text that appears on my auto that results from downloading a piece of work unit:

Work UNIT DOWNLOADED:

Midweek Dec 12 19:10:29 2007||Starting BOINC client version 5.10.29 for powerpc-apple-darwin
Wed Dec 12 19:ten:29 2007||log flags: task, file_xfer, sched_ops
Wed Dec 12 xix:x:29 2007||Libraries: libcurl/7.17.0 OpenSSL/0.9.7l zlib/1.2.3
Wednesday Dec 12 nineteen:10:29 2007||Data directory: /Library/Application Support/BOINC Data
Wed December 12 19:10:29 2007||Processor: 2 Power Macintosh Power Macintosh [Power Macintosh Model PowerMac3,3] [AltiVec]
Wed Dec 12 19:10:29 2007||Processor features:
Wednesday Dec 12 19:10:29 2007||Bone: Darwin: 8.10.0
Wed December 12 19:ten:29 2007||Retentiveness: 896.00 MB concrete, 25.96 GB virtual
Wed Dec 12 19:10:29 2007||Disk: 31.71 GB full, 25.72 GB free
Wed Dec 12 19:10:29 2007||Local time is UTC -6 hours
Wed Dec 12 19:ten:29 2007||No general preferences found - using BOINC defaults
Midweek Dec 12 19:10:29 2007||Preferences limit retention usage when active to 448.00MB
Wednesday Dec 12 nineteen:ten:29 2007||Preferences limit memory usage when idle to 806.40MB
Midweek Dec 12 19:ten:29 2007||Preferences limit deejay usage to 9.31GB
Wed December 12 xix:ten:29 2007||This computer is not attached to any projects
Wed Dec 12 19:ten:29 2007||Visit http://boinc.berkeley.edu for instructions
Wednesday Dec 12 19:xi:58 2007||Fetching configuration file from http://setiathome.berkeley.edu/get_project_config.php
Wed Dec 12 19:12:52 2007||Running CPU benchmarks
Wed Dec 12 19:12:52 2007||Suspending computation - running CPU benchmarks
Wed December 12 19:12:59 2007|SETI@home|Principal file download succeeded
Midweek Dec 12 nineteen:13:04 2007|SETI@home|Sending scheduler request: Project initialization. Requesting 1 seconds of work, reporting 0 completed tasks
Wed Dec 12 nineteen:13:09 2007|SETI@home|Scheduler asking succeeded: got i new tasks
Wed Dec 12 xix:thirteen:09 2007|SETI@home|New host venue: home
Wed Dec 12 19:xiii:09 2007||General prefs: from SETI@home (concluding modified 15-January-2006 02:38:54)
Wed Dec 12 19:13:09 2007||Host location: dwelling house
Wednesday Dec 12 xix:13:09 2007||General prefs: no carve up prefs for home; using your defaults
Wed Dec 12 19:thirteen:09 2007||Preferences limit memory usage when agile to 448.00MB
Wed Dec 12 19:13:09 2007||Preferences limit memory usage when idle to 806.40MB
Wed Dec 12 19:13:09 2007||Preferences limit deejay usage to 25.15GB
Wed Dec 12 19:thirteen:11 2007|SETI@home|Started download of setiathome_5.28_powerpc-apple-darwin
Wednesday Dec 12 nineteen:13:xi 2007|SETI@home|Started download of seti_528.jpg
Wed December 12 19:thirteen:12 2007|SETI@home|Finished download of seti_528.jpg
Wed Dec 12 19:13:12 2007|SETI@home|Started download of setiathome-5.28_AUTHORS
Wed December 12 19:xiii:13 2007|SETI@habitation|Finished download of setiathome-5.28_AUTHORS
Wednesday Dec 12 19:13:thirteen 2007|SETI@habitation|Started download of setiathome-5.28_COPYING
Wed December 12 19:13:14 2007|SETI@home|Finished download of setiathome-v.28_COPYING
Wed December 12 19:xiii:14 2007|SETI@home|Started download of setiathome-5.28_COPYRIGHT
Wed Dec 12 19:13:15 2007|SETI@abode|Finished download of setiathome-5.28_COPYRIGHT
Wed Dec 12 19:13:15 2007|SETI@dwelling house|Started download of setiathome-five.28_README
Wed December 12 19:13:16 2007|SETI@home|Finished download of setiathome-v.28_README
Midweek December 12 nineteen:xiii:xvi 2007|SETI@habitation|Started download of 23mr07ad.1965.16023.7.6.48
Wed Dec 12 19:13:19 2007|SETI@home|Finished download of 23mr07ad.1965.16023.seven.6.48
Midweek December 12 xix:thirteen:19 2007|SETI@dwelling house|Started download of arecibo_181.png
Wed Dec 12 19:13:22 2007|SETI@home|Finished download of arecibo_181.png
Wednesday Dec 12 19:xiii:22 2007|SETI@home|Started download of sah_40.png
Wed Dec 12 xix:thirteen:23 2007|SETI@home|Finished download of sah_40.png
Wed Dec 12 xix:13:23 2007|SETI@abode|Started download of sah_banner_290.png
Wed Dec 12 19:13:24 2007|SETI@home|Finished download of sah_banner_290.png
Wed Dec 12 19:13:24 2007|SETI@home|Started download of sah_ss_290.png
Wed Dec 12 nineteen:13:25 2007|SETI@home|Finished download of sah_ss_290.png
Wed Dec 12 19:xiii:29 2007|SETI@home|Finished download of setiathome_5.28_powerpc-apple tree-darwin
Wed Dec 12 xix:17:53 2007||[error] CPU benchmarks timed out, using default values
Wed Dec 12 19:17:54 2007||Resuming computation
Wed Dec 12 19:17:54 2007|SETI@habitation|Starting 23mr07ad.1965.16023.seven.vi.48_1
Wed December 12 19:17:55 2007|SETI@home|Starting chore 23mr07ad.1965.16023.7.half dozen.48_1 using setiathome_enhanced version 528
Wed Dec 12 19:17:55 2007||Running CPU benchmarks
Wed Dec 12 nineteen:17:55 2007||Suspending computation - running CPU benchmarks
Wed Dec 12 19:17:58 2007|SETI@home|Sending scheduler asking: To fetch piece of work. Requesting 30240 seconds of work, reporting 0 completed tasks
Wed Dec 12 19:xviii:04 2007|SETI@home|Scheduler request succeeded: got 1 new tasks
Midweek Dec 12 19:18:06 2007|SETI@dwelling|Started download of 23mr07ad.1965.16841.7.6.110
Wed Dec 12 19:18:09 2007|SETI@domicile|Finished download of 23mr07ad.1965.16841.7.6.110
Wed December 12 nineteen:22:56 2007||[fault] CPU benchmarks timed out, using default values
Midweek Dec 12 xix:22:57 2007||Resuming computation
Wednesday Dec 12 nineteen:22:57 2007|SETI@dwelling|Starting 23mr07ad.1965.16841.vii.6.110_0
Midweek Dec 12 19:22:57 2007|SETI@home|Starting job 23mr07ad.1965.16841.vii.6.110_0 using setiathome_enhanced version 528
Wed Dec 12 nineteen:22:57 2007||Running CPU benchmarks
Midweek Dec 12 19:22:57 2007||Suspending computation - running CPU benchmarks
Midweek Dec 12 xix:27:57 2007||[error] CPU benchmarks timed out, using default values
Wednesday Dec 12 19:27:58 2007||Resuming computation
Wed Dec 12 19:27:58 2007||Running CPU benchmarks
Wed December 12 19:27:58 2007||Suspending computation - running CPU benchmarks
Wednesday December 12 xix:28:29 2007||Benchmark results:
Wed Dec 12 19:28:29 2007|| Number of CPUs: 2
Wed Dec 12 19:28:29 2007|| 337 floating point MIPS (Whetstone) per CPU
Wed Dec 12 xix:28:29 2007|| 746 integer MIPS (Dhrystone) per CPU
Wednesday Dec 12 19:28:30 2007||Resuming computation
----------------------------------------------------------

Here is fault message that runs through the next 15 hours of download. I don't know what it means. The first line, below the line of dashes, says:
Can't rename client_state_next.xml...

Is my download going to produce worthwhile (and consummate) results?
My Mac is processing the current work unit now.

Another recurring message below is:
Couldn't write state file: system rename
That is the final line of this entire study.

----------------------------------------------------------
Wednesday Dec 12 20:03:fifteen 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Wed December 12 twenty:03:15 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Wed Dec 12 20:03:15 2007||[error] Couldn't write state file: system rename
Wed December 12 20:22:27 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Wed Dec 12 twenty:22:27 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Wed Dec 12 20:22:27 2007||[error] Couldn't write state file: organisation rename
Wednesday Dec 12 20:33:46 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Wednesday December 12 20:33:46 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Wed Dec 12 twenty:33:46 2007||[mistake] Couldn't write state file: system rename
Wed Dec 12 20:35:46 2007||Can't rename client_state_next.xml to client_state.xml; cheque file and directory permissions
Midweek December 12 20:35:46 2007||rename client_state_next.xml to client_state.xml returned mistake 2: No such file or directory
Midweek Dec 12 20:35:46 2007||[fault] Couldn't write state file: system rename
Wed Dec 12 20:39:07 2007||Can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Wednesday Dec 12 xx:39:07 2007||rename client_state_next.xml to client_state.xml returned fault 2: No such file or directory
Midweek Dec 12 20:39:07 2007||[error] Couldn't write country file: arrangement rename
Wed Dec 12 xx:43:07 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Wed Dec 12 twenty:43:07 2007||rename client_state_next.xml to client_state.xml returned fault 2: No such file or directory
Wednesday Dec 12 20:43:07 2007||[error] Couldn't write land file: system rename
Wed Dec 12 22:24:44 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Wed Dec 12 22:24:44 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Wed Dec 12 22:24:44 2007||[error] Couldn't write state file: system rename
Wed December 12 22:40:07 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Wed Dec 12 22:40:07 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Wednesday December 12 22:forty:07 2007||[error] Couldn't write state file: system rename
Wed Dec 12 22:51:05 2007||Can't rename client_state_next.xml to client_state.xml; cheque file and directory permissions
Wed Dec 12 22:51:05 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Wednesday Dec 12 22:51:05 2007||[error] Couldn't write state file: organization rename
Wed Dec 12 23:08:39 2007||General prefs: from SETI@dwelling house (concluding modified 15-Jan-2006 02:38:54)
Wed Dec 12 23:08:39 2007||Host location: habitation
Wed December 12 23:08:39 2007||General prefs: no separate prefs for home; using your defaults
Midweek Dec 12 23:08:39 2007||Reading preferences override file
Wed December 12 23:08:39 2007||Preferences limit memory usage when agile to 448.00MB
Wednesday Dec 12 23:08:39 2007||Preferences limit memory usage when idle to 806.40MB
Wed Dec 12 23:08:39 2007||Preferences limit disk usage to 25.70GB
Wed December 12 23:ten:29 2007||Tin't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Wed Dec 12 23:10:29 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Wed Dec 12 23:ten:29 2007||[error] Couldn't write land file: system rename
Wed December 12 23:thirteen:09 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Midweek Dec 12 23:xiii:09 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Wed Dec 12 23:xiii:09 2007||[error] Couldn't write country file: arrangement rename
Wed Dec 12 23:57:03 2007||Can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Wed Dec 12 23:57:03 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Midweek December 12 23:57:03 2007||[fault] Couldn't write state file: system rename
Thu Dec xiii 00:35:53 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December 13 00:35:53 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec thirteen 00:35:53 2007||[error] Couldn't write state file: system rename
Thu Dec 13 00:48:59 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 00:48:59 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu December 13 00:48:59 2007||[error] Couldn't write state file: arrangement rename
Thu Dec 13 00:53:59 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 00:53:59 2007||rename client_state_next.xml to client_state.xml returned mistake two: No such file or directory
Thu Dec 13 00:53:59 2007||[error] Couldn't write country file: organization rename
Thu Dec 13 01:08:forty 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December 13 01:08:40 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu December 13 01:08:40 2007||[mistake] Couldn't write state file: system rename
Thu Dec thirteen 01:25:01 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December 13 01:25:01 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Thu Dec 13 01:25:01 2007||[error] Couldn't write land file: organization rename
Thu December 13 01:33:14 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 01:33:14 2007||rename client_state_next.xml to client_state.xml returned fault 2: No such file or directory
Thu December 13 01:33:14 2007||[error] Couldn't write state file: system rename
Thu December 13 01:46:57 2007||Can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu Dec 13 01:46:57 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 01:46:57 2007||[mistake] Couldn't write state file: system rename
Thu Dec xiii 02:15:04 2007||Can't rename client_state_next.xml to client_state.xml; cheque file and directory permissions
Thu Dec 13 02:15:04 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu December thirteen 02:15:04 2007||[error] Couldn't write land file: system rename
Thu Dec 13 02:32:20 2007||Can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu December 13 02:32:twenty 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu December 13 02:32:20 2007||[error] Couldn't write land file: system rename
Thu Dec 13 03:07:twenty 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December 13 03:07:xx 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec thirteen 03:07:20 2007||[error] Couldn't write state file: system rename
Thu Dec 13 03:08:49 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec xiii 03:08:49 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Thu December 13 03:08:49 2007||[error] Couldn't write state file: arrangement rename
Thu Dec 13 03:15:45 2007||Tin't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu Dec 13 03:fifteen:45 2007||rename client_state_next.xml to client_state.xml returned mistake 2: No such file or directory
Thu Dec 13 03:15:45 2007||[fault] Couldn't write state file: system rename
Thu Dec 13 03:twenty:35 2007||Tin't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu Dec 13 03:20:35 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 03:twenty:35 2007||[error] Couldn't write state file: system rename
Thu Dec thirteen 03:58:36 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 03:58:36 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu December 13 03:58:36 2007||[fault] Couldn't write land file: system rename
Thu Dec 13 04:15:51 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec xiii 04:15:51 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec xiii 04:15:51 2007||[error] Couldn't write country file: system rename
Thu Dec xiii 04:26:11 2007||Tin can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu Dec 13 04:26:eleven 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu December 13 04:26:11 2007||[error] Couldn't write state file: organisation rename
Thu December 13 04:51:57 2007||Can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu Dec thirteen 04:51:57 2007||rename client_state_next.xml to client_state.xml returned fault two: No such file or directory
Thu December 13 04:51:57 2007||[error] Couldn't write state file: organisation rename
Thu Dec thirteen 05:49:41 2007||Can't rename client_state_next.xml to client_state.xml; cheque file and directory permissions
Thu Dec xiii 05:49:41 2007||rename client_state_next.xml to client_state.xml returned error ii: No such file or directory
Thu Dec 13 05:49:41 2007||[mistake] Couldn't write state file: system rename
Thu Dec 13 06:33:28 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec xiii 06:33:28 2007||rename client_state_next.xml to client_state.xml returned error ii: No such file or directory
Thu December thirteen 06:33:28 2007||[error] Couldn't write state file: organization rename
Thu Dec 13 06:49:33 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 06:49:33 2007||rename client_state_next.xml to client_state.xml returned mistake 2: No such file or directory
Thu Dec 13 06:49:33 2007||[fault] Couldn't write land file: system rename
Thu Dec thirteen 06:59:xx 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec thirteen 06:59:20 2007||rename client_state_next.xml to client_state.xml returned fault 2: No such file or directory
Thu Dec 13 06:59:20 2007||[error] Couldn't write land file: arrangement rename
Thu Dec 13 07:34:27 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 07:34:27 2007||rename client_state_next.xml to client_state.xml returned mistake two: No such file or directory
Thu December 13 07:34:27 2007||[error] Couldn't write country file: system rename
Thu Dec xiii 07:48:07 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec xiii 07:48:07 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 07:48:07 2007||[error] Couldn't write country file: organization rename
Thu Dec 13 08:04:16 2007||Can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu December thirteen 08:04:sixteen 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec xiii 08:04:16 2007||[mistake] Couldn't write country file: organization rename
Thu Dec 13 09:03:00 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December 13 09:03:00 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Thu Dec 13 09:03:00 2007||[error] Couldn't write state file: system rename
Thu Dec 13 09:28:21 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December thirteen 09:28:21 2007||rename client_state_next.xml to client_state.xml returned error ii: No such file or directory
Thu December 13 09:28:21 2007||[error] Couldn't write state file: system rename
Thu December 13 09:41:58 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 09:41:58 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu December thirteen 09:41:58 2007||[error] Couldn't write country file: system rename
Thu Dec 13 ten:02:12 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 10:02:12 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec thirteen 10:02:12 2007||[error] Couldn't write state file: system rename
Thu Dec 13 10:13:42 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec xiii 10:thirteen:42 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 10:13:42 2007||[error] Couldn't write state file: system rename
Thu December thirteen 10:52:52 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December xiii 10:52:52 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Thu Dec xiii 10:52:52 2007||[error] Couldn't write state file: organisation rename
Thu December 13 eleven:01:32 2007||Tin can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 11:01:32 2007||rename client_state_next.xml to client_state.xml returned fault two: No such file or directory
Thu Dec xiii 11:01:32 2007||[fault] Couldn't write state file: system rename
Thu Dec 13 12:05:23 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December 13 12:05:23 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 12:05:23 2007||[fault] Couldn't write state file: arrangement rename
Thu Dec 13 12:18:26 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec xiii 12:18:26 2007||rename client_state_next.xml to client_state.xml returned fault 2: No such file or directory
Thu Dec xiii 12:18:26 2007||[error] Couldn't write state file: system rename
Thu Dec 13 thirteen:19:10 2007||Can't rename client_state_next.xml to client_state.xml; bank check file and directory permissions
Thu December thirteen xiii:19:10 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 thirteen:nineteen:10 2007||[error] Couldn't write land file: system rename
Thu Dec 13 thirteen:33:29 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 13:33:29 2007||rename client_state_next.xml to client_state.xml returned error ii: No such file or directory
Thu Dec xiii 13:33:29 2007||[error] Couldn't write country file: system rename
Thu Dec 13 13:51:46 2007||Can't rename client_state_next.xml to client_state.xml; cheque file and directory permissions
Thu Dec 13 thirteen:51:46 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 13:51:46 2007||[error] Couldn't write country file: organisation rename
Thu Dec 13 13:53:l 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December thirteen 13:53:50 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec thirteen thirteen:53:50 2007||[fault] Couldn't write country file: organisation rename
Thu December 13 15:59:48 2007||Can't rename client_state_next.xml to client_state.xml; cheque file and directory permissions
Thu Dec 13 15:59:48 2007||rename client_state_next.xml to client_state.xml returned error two: No such file or directory
Thu Dec thirteen 15:59:48 2007||[mistake] Couldn't write land file: system rename
Thu Dec 13 17:45:04 2007|SETI@home|Sending scheduler request: To fetch work. Requesting 94 seconds of work, reporting 0 completed tasks
Thu Dec 13 17:45:09 2007|SETI@dwelling house|Scheduler asking succeeded: got 1 new tasks
Thu Dec 13 17:45:11 2007|SETI@home|Started download of 26mr07ab.3555.11115.12.half-dozen.32
Thu Dec xiii 17:45:14 2007|SETI@abode|Finished download of 26mr07ab.3555.11115.12.6.32
Thu Dec 13 17:45:36 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December 13 17:45:36 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec 13 17:45:36 2007||[fault] Couldn't write country file: organisation rename
Thu December 13 18:03:32 2007|SETI@home|Sending scheduler request: To fetch piece of work. Requesting 118 seconds of work, reporting 0 completed tasks
Thu Dec 13 18:03:53 2007|SETI@dwelling|Scheduler request succeeded: got ane new tasks
Thu Dec 13 eighteen:03:55 2007|SETI@home|Started download of 26mr07ab.32096.7843.15.6.110
Thu Dec xiii eighteen:03:57 2007|SETI@home|Finished download of 26mr07ab.32096.7843.fifteen.6.110
Thu Dec thirteen 18:22:41 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 18:22:41 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Thu Dec xiii 18:22:41 2007||[error] Couldn't write state file: arrangement rename
Thu Dec 13 19:57:35 2007||Tin can't rename client_state_next.xml to client_state.xml; cheque file and directory permissions
Thu Dec 13 19:57:35 2007||rename client_state_next.xml to client_state.xml returned fault two: No such file or directory
Thu Dec thirteen 19:57:35 2007||[error] Couldn't write state file: system rename
Thu Dec 13 20:17:46 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec 13 20:17:46 2007||rename client_state_next.xml to client_state.xml returned mistake two: No such file or directory
Thu Dec 13 20:17:46 2007||[error] Couldn't write state file: organisation rename
Thu December 13 20:32:12 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu December xiii 20:32:12 2007||rename client_state_next.xml to client_state.xml returned mistake 2: No such file or directory
Thu Dec 13 twenty:32:12 2007||[error] Couldn't write state file: system rename
Thu Dec 13 twenty:58:46 2007||Tin can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Thu Dec thirteen 20:58:46 2007||rename client_state_next.xml to client_state.xml returned fault 2: No such file or directory
Thu Dec thirteen 20:58:46 2007||[mistake] Couldn't write state file: organisation rename


ID: 691297 · Report as offensive

Profile Keith
Send message
Joined: 19 May 99
Posts: 483
Credit: 938,268
RAC: 0
United Kingdom

Bulletin 691343 - Posted: fourteen Dec 2007, 7:29:18 UTC - in response to Message 691297.
Last modified: xiv Dec 2007, 7:32:01 UTC

Cereus

I think you mat have chosen an unfortunate fourth dimension to restart when there were issues at the server.

I suggest y'all try downloading BOINC Manager again, now that normality has returned.

This should resolve the permissions problem you seem to have experienced.

In the unlikely result that permissions notwithstanding need to be stock-still, you can do so as follows:-

Quit BOINC Manager.
Select the "setiathome.berkeley.edu" file.
     This is to exist found on Difficult Disk in folder at Library/Application Support/BOINC Information/projects
Get Info from the Finder File menu (or Cmd I).
Open "Ownership & Permissions", and so "Details".
If not already correct,
      Unlock the padlock and set Owner to "boinc_master" and Group to "boinc_project" and lock padlock.
Now that permissions for this folder are correct, click on "Employ to Enclosed Items" and close "Get Info".
      (during this change of permissions, you will be asked for your password)
Then restart BOINC Manager (from the dock) and all should be fine.

Keith

ID: 691343 · Report as offensive

Dotsch
Volunteer tester
Avatar
Send bulletin
Joined: 9 Jun 99
Posts: 2422
Credit: 919,393
RAC: 0
Germany

Message 691346 - Posted: 14 December 2007, 7:35:56 UTC

Could y'all please cease the BOINC client and repair the permitions with the disk utility.


ID: 691346 · Report as offensive

Dotsch
Volunteer tester
Avatar
Send message
Joined: 9 Jun 99
Posts: 2422
Credit: 919,393
RAC: 0
Germany

Message 691347 - Posted: xiv Dec 2007, 7:37:07 UTC - in response to Bulletin 691343.


I think you lot mat have chosen an unfortunate time to restart when in that location were problems at the server.

Practise you know some more details virtually the server problems ?


ID: 691347 · Report as offensive

Profile Keith
Send message
Joined: 19 May 99
Posts: 483
Credit: 938,268
RAC: 0
United Kingdom

Bulletin 691356 - Posted: xiv Dec 2007, 9:03:13 UTC - in response to Message 691347.


I think y'all mat accept chosen an unfortunate time to restart when in that location were problems at the server.

Do you know some more details near the server problems ?

Dotsch

Yous may non take noticed that at about this time that Cereus was downloading his BOINC files, the server was repeatedly giving error letters of "no piece of work", and this might well have affected the downloads that Cereus was making. (Mayhap not, but information technology'south worth taking a bet on that.)

Your recommendation of using Deejay Utility is not usually the recommended procedure for BOINC Manager installation preference bug, but information technology might be worth a try in spite of being a lot more "long winded". But I have a strong feeling that Disk Utility is not designed to pick up the sort of permissions mistake encountered here.

Keith

P.S. permiSSions non permiTions (and I typed maT instead of maY !!)

ID: 691356 · Report as offensive

Dotsch
Volunteer tester
Avatar
Send message
Joined: 9 Jun 99
Posts: 2422
Credit: 919,393
RAC: 0
Germany

Message 691357 - Posted: 14 December 2007, 9:17:17 UTC - in response to Message 691356.


I think you mat have chosen an unfortunate time to restart when there were problems at the server.

Do you know some more details well-nigh the server problems ?

Dotsch

You lot may not have noticed that at about this time that Cereus was downloading his BOINC files, the server was repeatedly giving error messages of "no work", and this might well accept affected the downloads that Cereus was making. (Possibly not, but it's worth taking a bet on that.)

I take seen this, but I am have testing some new BOINC client builds and accept some connection problems. This is why I am asked for details.
Practice you know if the feeder issues are repaired ?


ID: 691357 · Report as offensive

Profile Keith
Ship bulletin
Joined: xix May 99
Posts: 483
Credit: 938,268
RAC: 0
United Kingdom

Message 691362 - Posted: fourteen Dec 2007, x:15:57 UTC - in response to Bulletin 691357.


I think you mat take chosen an unfortunate time to restart when there were problems at the server.

Do you know some more than details about the server problems ?

Dotsch

You may not accept noticed that at about this time that Cereus was downloading his BOINC files, the server was repeatedly giving error messages of "no work", and this might well take affected the downloads that Cereus was making. (Perhaps not, simply it'due south worth taking a bet on that.)


I take seen this, merely I am have testing some new BOINC client builds and take some connexion problems. This is why I am asked for details.
Practice you know if the feeder issues are repaired ?

============================================================
Dotsch
I've sent a private message marked "Download difficulties subsequently outage" with all entries on my log covering the problem menses and hope y'all may glean some useful information from that. I'll be interested to hear of any conclusions if you could have time to let me know, and I'll let you have farther information if y'all require it for your testing piece of work.
Keith

ID: 691362 · Report as offensive

Profile cereus
Transport message
Joined: 16 May 99
Posts: 6
Credit: 190,644
RAC: 0
United States

Bulletin 691444 - Posted: 14 December 2007, 18:02:23 UTC - in response to Message 691362.


I think you mat take chosen an unfortunate time to restart when there were issues at the server.

Do you know some more details about the server problems ?

Dotsch

You may not have noticed that at virtually this time that Cereus was downloading his BOINC files, the server was repeatedly giving error messages of "no work", and this might well take affected the downloads that Cereus was making. (Maybe not, but it's worth taking a bet on that.)


I take seen this, but I am have testing some new BOINC customer builds and accept some connectedness bug. This is why I am asked for details.
Do y'all know if the feeder issues are repaired ?

============================================================
Dotsch
I've sent a individual message marked "Download difficulties after outage" with all entries on my log roofing the problem period and hope you may glean some useful information from that. I'll exist interested to hear of any conclusions if y'all could accept time to let me know, and I'll let you take farther information if y'all crave it for your testing work.
Keith

Keith and Dotsch,
Thank both of you for chiming in with your thoughts.
I am stunned and surprised by your cheerful responses
to my original, 50-o-n-g and fifty-due east-n-g-t-h-y question.
I figured I needed to present as much info as was avialable to me.
Thank you for trying to resolve my puzzlement.

I will try your suggestions later tonight when things are a bit calmer for me to practise computer work.

Your responses are much in the manner of the folks who ran SETI.
They were prompt and complete.
And so are yous.
I am a happier starsearcher.

I'll become back to you in a few days


ID: 691444 · Report as offensive

Profile cereus
Send message
Joined: 16 May 99
Posts: 6
Credit: 190,644
RAC: 0
United States

Message 691524 - Posted: 15 December 2007, 0:17:eleven UTC - in response to Message 691444.


I think you mat have chosen an unfortunate time to restart when there were issues at the server.

Exercise you lot know some more details nigh the server issues ?

Dotsch

You may not take noticed that at well-nigh this time that Cereus was downloading his BOINC files, the server was repeatedly giving error messages of "no work", and this might well have affected the downloads that Cereus was making. (Possibly not, but it'due south worth taking a bet on that.)


I have seen this, but I am have testing some new BOINC client builds and have some connection problems. This is why I am asked for details.
Do you know if the feeder issues are repaired ?

============================================================
Dotsch
I've sent a private message marked "Download difficulties after outage" with all entries on my log covering the problem period and hope you may glean some useful information from that. I'll be interested to hear of any conclusions if you could have time to let me know, and I'll let you have further data if you lot require it for your testing piece of work.
Keith

Keith and Dotsch,
Thank both of y'all for chiming in with your thoughts.
I am stunned and surprised by your cheerful responses
to my original, l-o-due north-k and l-eastward-n-g-t-h-y question.
I figured I needed to present as much info as was avialable to me.
Thanks for trying to resolve my puzzlement.

I will endeavour your suggestions later this night when things are a bit calmer for me to practise computer piece of work.

Your responses are much in the fashion of the folks who ran SETI.
They were prompt and complete.
So are you.
I am a happier starsearcher.

I'll go back to you in a few days

Hey guys,

My "Job" screen shows that the above jabberwocky that I cited
to bear witness the trouble that I was experiencing [as I cited to a higher place}
with the work unit beingness downloaded to my Mac, well...

We now advance to the next stride.

My Mac has candy all the in a higher place jabberwocky
and the "Tasks" screen now shows that two files are "Ready to Study."

Nether SETI, reporting was done automatically.
I don't remember what BOINC is supposed to exist doing.
So I'm stuck with what to do side by side,
if anything,
with the two files that have read, "Gear up to Report."
They take said, "Set to Report" for the last 15 hours.

How do I go the 2 files to move on to their greater glory within Berkeley's reckoner?


ID: 691524 · Report as offensive

Odysseus
Volunteer tester
Avatar
Send bulletin
Joined: 26 Jul 99
Posts: 1808
Credit: 6,701,347
RAC: six
Canada

Message 691642 - Posted: 15 Dec 2007, 4:30:40 UTC - in response to Message 691524.
Last modified: xv Dec 2007, iv:35:22 UTC

Under SETI, reporting was done automatically.
I don't think what BOINC is supposed to be doing.
Then I'm stuck with what to do next,
if anything,
with the two files that have read, "Ready to Study."
They have said, "Prepare to Written report" for the last fifteen hours.

How do I go the two files to motion on to their greater glory within Berkeley'southward calculator?

Not to worry: BOINC volition opportunistically written report these tasks next time it contacts the database server. The files themselves should already be safely on a file server—yous should see some messages associated with these transactions appearing soon later on each ciphering-finished entry in the log. Since reporting results (different uploading the associated data files) involves a lot of overhead for the database server, BOINC tries to batch the reports in order to get as much business organization as possible washed in each transaction. The system so retrieves the results from the upload server and puts them in the validation queue. Just how often it will written report depends on your host’s throughput and the connection interval in your general preferences. Typical behaviour is to inquire for more than work when the tasks on board are nearly finished, reporting everything at that time that’s been done since the last connection. There are other circumstances nether which it will study, including an impending deadline (within 24 hours IIANM) and a user-initiated project update.

To hurry things along you can become to the Projects tab of BOINC Manager (Avant-garde view), select the project and hit the Update push button. This is not recommended every bit a routine practice, but can be useful when troubleshooting or for following up on tasks that produced errors or anomalous behaviour.


ID: 691642 · Report as offensive

Profile cereus
Send message
Joined: xvi May 99
Posts: 6
Credit: 190,644
RAC: 0
United States

Message 692351 - Posted: 17 Dec 2007, 20:39:47 UTC - in response to Message 691642.

Under SETI, reporting was done automatically.
I don't remember what BOINC is supposed to exist doing.
Then I'm stuck with what to do adjacent,
if annihilation,
with the 2 files that have read, "Ready to Report."
They have said, "Prepare to Study" for the final fifteen hours.

How do I go the ii files to move on to their greater glory inside Berkeley's figurer?


Non to worry: BOINC volition opportunistically report these tasks next time it contacts the database server. The files themselves should already be safely on a file server—you should see some messages associated with these transactions actualization before long after each computation-finished entry in the log. Since reporting results (unlike uploading the associated data files) involves a lot of overhead for the database server, BOINC tries to batch the reports in order to become as much business as possible done in each transaction. The system then retrieves the results from the upload server and puts them in the validation queue. Just how often information technology will report depends on your host’south throughput and the connectedness interval in your general preferences. Typical behaviour is to ask for more piece of work when the tasks on board are almost finished, reporting everything at that time that’southward been done since the last connection. There are other circumstances nether which it volition report, including an impending borderline (within 24 hours IIANM) and a user-initiated project update.

To hurry things forth you lot can get to the Projects tab of BOINC Managing director (Avant-garde view), select the project and hit the Update push. This is not recommended every bit a routine practice, but can be useful when troubleshooting or for following up on tasks that produced errors or anomalous behaviour.

Odysseus and Keith,

Thank you for your responses.
You were right, Odysseus.
BOINC collected my reports within a few more hours.
I'thousand withal suspicious, all the same, if BOINC can utilise the data my Mac has processed,
considering I go along to get the bulletin on my BOINC "Messages" tab:

Mon Dec 17 13:47:25 2007||[error] Couldn't write state file: system rename
Monday December 17 thirteen:58:03 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Mon Dec 17 thirteen:58:03 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory
Mon December 17 13:58:03 2007||[error] Couldn't write state file: system rename

So my question relates to that message.
Is my data written report worth anything to BOINC if the state file info can't be written?

Keith, I followed all your advice to change info on the control-i
except for your final words: click on "Utilise to Enclosed Items" and close "Get Info".
I couldn't find where to click on "Apply to Enclosed Items" and shut "Get Info".
Then I failed to do that.
I also ran my Os X disc and ran the Disk Utility Repair Permissions,
equally recommended past Dotsch.
Even having followed your suggestions,
I'g nevertheless getting the message that says, as above,
Mon Dec 17 xiii:58:03 2007||[error] Couldn't write state file: arrangement rename

Cheers to all of yous for your responses.
Exercise yous take whatever other thoughts on these matters?
Happy Holidays.


ID: 692351 · Report as offensive

Profile Keith
Ship message
Joined: 19 May 99
Posts: 483
Credit: 938,268
RAC: 0
United Kingdom

Message 692390 - Posted: 17 Dec 2007, 23:16:00 UTC - in response to Message 692351.

Under SETI, reporting was done automatically.
I don't recall what BOINC is supposed to be doing.
So I'thousand stuck with what to do side by side,
if anything,
with the two files that have read, "Fix to Study."
They have said, "Gear up to Written report" for the last 15 hours.

How practice I get the two files to move on to their greater glory inside Berkeley'due south computer?


Non to worry: BOINC will opportunistically report these tasks side by side time it contacts the database server. The files themselves should already be safely on a file server—you lot should encounter some letters associated with these transactions appearing shortly after each computation-finished entry in the log. Since reporting results (unlike uploading the associated data files) involves a lot of overhead for the database server, BOINC tries to batch the reports in lodge to get as much business equally possible done in each transaction. The system and then retrieves the results from the upload server and puts them in the validation queue. Just how often it will report depends on your host’south throughput and the connection interval in your general preferences. Typical behaviour is to ask for more work when the tasks on board are well-nigh finished, reporting everything at that time that’s been done since the concluding connexion. There are other circumstances under which it volition report, including an impending deadline (within 24 hours IIANM) and a user-initiated project update.

To bustle things forth yous can go to the Projects tab of BOINC Managing director (Advanced view), select the project and hitting the Update button. This is not recommended equally a routine do, only can be useful when troubleshooting or for following upwardly on tasks that produced errors or anomalous behaviour.

Odysseus and Keith,

Thanks for your responses.
You lot were correct, Odysseus.
BOINC collected my reports within a few more hours.
I'm still suspicious, however, if BOINC can use the data my Mac has processed,
because I proceed to get the message on my BOINC "Letters" tab:

Mon Dec 17 thirteen:47:25 2007||[error] Couldn't write land file: system rename
Monday Dec 17 13:58:03 2007||Tin't rename client_state_next.xml to client_state.xml; check file and directory permissions
Mon Dec 17 xiii:58:03 2007||rename client_state_next.xml to client_state.xml returned fault ii: No such file or directory
Monday December 17 thirteen:58:03 2007||[error] Couldn't write land file: organization rename

So my question relates to that message.
Is my data study worth anything to BOINC if the state file info can't be written?

Keith, I followed all your communication to alter info on the control-i
except for your final words: click on "Apply to Enclosed Items" and shut "Get Info".
I couldn't discover where to click on "Apply to Enclosed Items" and close "Get Info".
So I failed to do that.
I too ran my Bone X disc and ran the Disk Utility Repair Permissions,
as recommended by Dotsch.
Fifty-fifty having followed your suggestions,
I'chiliad notwithstanding getting the message that says, as above,
Mon December 17 thirteen:58:03 2007||[mistake] Couldn't write state file: organisation rename

Thanks to all of you for your responses.
Do you lot have any other thoughts on these matters?
Happy Holidays.

Cereus

At the bottom of the Cmd-I dialogue box you saw "Buying & Permission" and then "Details".
I assume y'all were irresolute permissions on individual files if there was no "Apply to Enclosed Items".

I suggested you brand sure permissions are set to Owner "Boinc_master" and Grouping "Boinc_project" for the folder called "setiathome.berkeley.edu".
Brand sure that the "setiathome.berkeley.edu" folder is selected earlier the Command-I is pressed.
Then (most importantly) click "Apply to Enclosed Items" which is shown at the very lesser of the dialogue box. This makes sure that all the files within that folder are correctly ready to the right permissions.

I am pretty confident this volition cure your permissions problem.

Keith

ID: 692390 · Report as offensive

Profile Keith
Send message
Joined: 19 May 99
Posts: 483
Credit: 938,268
RAC: 0
United Kingdom

Message 692513 - Posted: eighteen Dec 2007, 7:53:17 UTC - in response to Bulletin 692351.
Last modified: xviii Dec 2007, seven:54:11 UTC

Cereus

Another thought has crossed my heed relating to the letters yous noted as:

Mon Dec 17 thirteen:47:25 2007||[error] Couldn't write state file: organisation rename
Mon December 17 13:58:03 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions
Mon Dec 17 13:58:03 2007||rename client_state_next.xml to client_state.xml returned error ii: No such file or directory
Mon December 17 13:58:03 2007||[fault] Couldn't write state file: system rename

Did you endeavor downloading BOINC Manager five.10.29 before trying correcting permissions?
This should right permissions automatically on installation. Practise this, even if already running five.10.29.
Although not recommended by some, there is no need to quit BOINC Manager on doing this update.

Is there any possibility that you have moved whatever of the files or folders, or renamed any of them?
The download and reinstallation of BOINC Manager 5.ten.29 may well correct these anyway.

The path of the SETI binder should exist as follows:
Mac Hard disk drive/Library/Application Support/BOINC Information/projects/setiathome.berkeley.edu
This folder has to be selected, non opened, when using Get Info (Cmd-I) for future reference, if needed.

Keith

ID: 692513 · Report as offensive

Odysseus
Volunteer tester
Avatar
Ship message
Joined: 26 Jul 99
Posts: 1808
Credit: 6,701,347
RAC: 6
Canada

Message 692674 - Posted: 19 Dec 2007, 2:58:42 UTC - in response to Message 692351.

Monday Dec 17 13:47:25 2007||[error] Couldn't write state file: organisation rename Mon Dec 17 13:58:03 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions Mon Dec 17 thirteen:58:03 2007||rename client_state_next.xml to client_state.xml returned error ii: No such file or directory Monday Dec 17 13:58:03 2007||[fault] Couldn't write state file: organisation rename

So my question relates to that message.
Is my data report worth anything to BOINC if the state file info can't be written?

You’re getting a lot of compute errors—just a few good results as well. (The tasks that failed volition be reissued, but your daily quota will be reduced for each ane. OTOH each success doubles the quota.) The mistake you’re seeing isn’t necessarily fatal: others accept reported getting it without ciphering errors causing invalid results—I judge it’southward sometimes a transient matter that clears upwardly on a retry.

Are you running any virus scanners, file indexing programs, or the like? Just in case resetting the ownership doesn’t assistance, that’s about all I can call back of right now …

ID: 692674 · Report as offensive

Profile cereus
Ship message
Joined: xvi May 99
Posts: vi
Credit: 190,644
RAC: 0
United States

Message 692835 - Posted: 19 Dec 2007, 17:19:fifteen UTC - in response to Message 692674.

Mon Dec 17 13:47:25 2007||[error] Couldn't write state file: system rename Mon Dec 17 13:58:03 2007||Tin can't rename client_state_next.xml to client_state.xml; check file and directory permissions Mon Dec 17 xiii:58:03 2007||rename client_state_next.xml to client_state.xml returned error 2: No such file or directory Monday December 17 thirteen:58:03 2007||[error] Couldn't write state file: organization rename

And then my question relates to that bulletin.
Is my data report worth annihilation to BOINC if the land file info can't be written?

You’re getting a lot of compute errors—only a few proficient results as well. (The tasks that failed volition be reissued, only your daily quota volition exist reduced for each one. OTOH each success doubles the quota.) The error you’re seeing isn’t necessarily fatal: others have reported getting it without ciphering errors causing invalid results—I guess it’s sometimes a transient thing that clears up on a retry.

Are you running any virus scanners, file indexing programs, or the like? Just in case resetting the ownership doesn’t help, that’south about all I can recollect of right now …

Keith,

I realized that I needed to have clicked on the SETI Folder, not i of the SETI files.
That is where "Utilize to enclosed items" is to be found, and that's where I have now, ultimately, clicked.
But then over the next 12 hours,
equally my Mac tried to d/l another Piece of work Unit of measurement from SETI
and do the number crunching associated with working on a work unit,
all I got were mistake bulletin: "Can't write land file..."

I went dorsum, once more than since your communication) and reinstalled SETI v.2.29.
I made no changes in the command-i boxes, I left whatever loaded with the new five.2.29.
I cut off my anti-virus programme, every bit advised by Odysseus.

Subsequently, I seem to be working properly.
So I think over the side by side 24 hrs, if all is going okay, I'll terminate this thread.

That y'all, Odysseus and Dotsch, cared plenty to offer some suggestions
gave me encouragement to continue trying.

Odysseus,

your words were really encouraging.
I take wanted for a couple of years to continue the SETI,
only BOINC'due south erratic beliefs during that fourth dimension, was a big Turn Off.
And I couldn't discover any help at the time (like what you have offered).
And at that signal, I just cut it all off.

Merely now that things are finally working, seemingly, I'll stick with it.
I am impressed by the numbers that are attached to your name!
And that you have time for a problem like mine is a testament
to your grapheme and friendliness.
Many, many thanks for steering me.

Oh, I also cutting off my anti-virus plan near 20 hours ago.
And, after, things are working without the Mistake Messages
I had been receiving for the last week.


ID: 692835 · Report as offensive

Profile cereus
Ship message
Joined: 16 May 99
Posts: 6
Credit: 190,644
RAC: 0
United States

Bulletin 692845 - Posted: 19 Dec 2007, eighteen:06:51 UTC - in response to Bulletin 692835.

Monday Dec 17 thirteen:47:25 2007||[error] Couldn't write state file: system rename Mon Dec 17 13:58:03 2007||Can't rename client_state_next.xml to client_state.xml; check file and directory permissions Mon Dec 17 13:58:03 2007||rename client_state_next.xml to client_state.xml returned mistake two: No such file or directory Monday Dec 17 13:58:03 2007||[error] Couldn't write state file: system rename

Then my question relates to that message.
Is my data report worth anything to BOINC if the country file info can't exist written?

You’re getting a lot of compute errors—just a few good results as well. (The tasks that failed will be reissued, but your daily quota volition be reduced for each one. OTOH each success doubles the quota.) The fault you’re seeing isn’t necessarily fatal: others have reported getting it without computation errors causing invalid results—I gauge it’southward sometimes a transient thing that clears up on a retry.

Are y'all running any virus scanners, file indexing programs, or the like? Just in case resetting the ownership doesn’t aid, that’s virtually all I can call up of right now …

Keith,

I realized that I needed to accept clicked on the SETI FOLDER, non ane of the SETI files.
That is where "Utilize to enclosed items" is to be found, and that's where I have now, ultimately, clicked.
But then over the next 12 hours,
as my Mac tried to d/l another Work Unit from SETI
and do the number crunching associated with working on a piece of work unit,
all I got were error bulletin: "Tin't write state file..."

I went back, once more than since your communication) and reinstalled SETI five.10.29.
I made no changes in the command-i boxes, I left any loaded with the new 5.x.29.
I cut off my anti-virus programme, equally brash by Odysseus.

Subsequently, I seem to be working properly.
And so I remember over the next 24 hrs, if all is going okay, I'll stop this thread.

That you, Odysseus and Dotsch, cared enough to offering some suggestions
gave me encouragement to keep trying.

Odysseus,

your words were really encouraging.
I take wanted for a couple of years to continue the SETI,
but BOINC's erratic beliefs during that fourth dimension, was a big Turn Off.
And I couldn't detect any help at the time (like what you have offered).
And at that point, I just cut it all off.

But at present that things are finally working, seemingly, I'll stick with it.
I am impressed past the numbers that are attached to your name!
And that you have time for a problem like mine is a testament
to your character and friendliness.
Many, many thanks for steering me.

Oh, I also cut off my anti-virus program about twenty hours ago.
And, subsequently, things are working without the Error Messages
I had been receiving for the terminal calendar week.

ID: 692845 · Report as offensive

Odysseus
Volunteer tester
Avatar
Transport message
Joined: 26 Jul 99
Posts: 1808
Credit: 6,701,347
RAC: six
Canada

Message 692973 - Posted: 20 December 2007, iii:17:33 UTC - in response to Message 692835.

Many, many thanks for steering me.

Non at all: glad to help—especially another PPC-Mac-user. ;)

Oh, I also cut off my anti-virus programme about 20 hours agone.
And, subsequently, things are working without the Error Messages
I had been receiving for the concluding calendar week.

Deplorable it didn’t occur to me sooner: I don’t run a continuous antivirus monitor. (I just practice occasional scans with ClamAV.) You may be able to keep using it, though, if you can tell it to ignore the BOINC Information folder; such programs normally have an exceptions list.

ID: 692973 · Report as offensive

Powered by BOINC

  ©2022 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 role by the NSF through grant AST-0307956.

sanchezpicarmention.blogspot.com

Source: https://setiathome.ssl.berkeley.edu/forum_thread.php?id=44086

0 Response to "Weã¢â‚¬â„¢re Sorry but There Was an Error Processing Your Request Please Try Again Later"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel