To all those guys having a real lot of machines -- poor you!

Wurgl (speak^Wcrunching for Special: Off-Topic)
Wurgl (speak^Wc...
Joined: 11 Feb 05
Posts: 321
Credit: 140550008
RAC: 0

RE: So it looks like the op

Message 28064 in response to message 28062

Quote:
So it looks like the op of this thread must have been hitting the update button in order to get to that point because I don't think the outage was long enough to drive it to that point.

Dude, I was sleeping during the outage. I have no idea what happend in my dreams, nor do I remember if there was any dream :-) But I am sure, I did not dream about hitting any kind of button ;^)

The outage started (for me) at 4:18 in the very morning, which is 2:18 UTC until 8:23. During this time I did not touch anything on the computer.

Do 13 Apr 2006 04:18:32 CEST|Einstein@Home|Requesting 5 seconds of new work
Do 13 Apr 2006 04:20:34 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:20:37 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:20:37 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:21:37 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:21:37 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:21:37 CEST|Einstein@Home|Requesting 466 seconds of new work
Do 13 Apr 2006 04:23:40 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:23:40 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:23:40 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:24:41 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:24:41 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:24:41 CEST|Einstein@Home|Requesting 917 seconds of new work
Do 13 Apr 2006 04:26:42 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:26:44 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:26:44 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:27:46 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:27:46 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:27:46 CEST|Einstein@Home|Requesting 1370 seconds of new work
Do 13 Apr 2006 04:29:47 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:29:51 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:29:51 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:30:52 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:30:52 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:30:52 CEST|Einstein@Home|Requesting 1825 seconds of new work
Do 13 Apr 2006 04:32:53 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:32:57 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:32:57 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:35:04 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:35:04 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:35:04 CEST|Einstein@Home|Requesting 2438 seconds of new work
Do 13 Apr 2006 04:37:06 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:37:10 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:37:10 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:38:20 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:38:20 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:38:20 CEST|Einstein@Home|Requesting 2916 seconds of new work
Do 13 Apr 2006 04:40:21 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:40:21 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:40:21 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:46:06 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:46:06 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:46:06 CEST|Einstein@Home|Requesting 4026 seconds of new work
Do 13 Apr 2006 04:48:08 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:48:11 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:48:11 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:49:58 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 04:49:58 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 04:49:58 CEST|Einstein@Home|Requesting 4577 seconds of new work
Do 13 Apr 2006 04:51:59 CEST||Network error: a timeout was reached
Do 13 Apr 2006 04:52:02 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 04:52:02 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 04:59:58 CEST|QMC@HOME|Restarting result one_st2dna_nodelete.538_0 using Amolqc-alpha version 506
Do 13 Apr 2006 04:59:58 CEST|Einstein@Home|Pausing result r1_1462.0__1634_S4R2a_1 (removed from memory)
Do 13 Apr 2006 05:01:40 CEST||Rescheduling CPU: application exited
Do 13 Apr 2006 05:01:40 CEST|Einstein@Home|Computation for result r1_1462.0__1635_S4R2a_2 finished
Do 13 Apr 2006 05:01:40 CEST|QMC@HOME|Pausing result one_st2dna_nodelete.538_0 (removed from memory)
Do 13 Apr 2006 05:01:40 CEST|Einstein@Home|Restarting result r1_1462.0__1634_S4R2a_1 using albert version 455
Do 13 Apr 2006 05:01:40 CEST|Einstein@Home|Starting result r1_1462.0__1633_S4R2a_1 using albert version 455
Do 13 Apr 2006 05:01:42 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:03:44 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:03:44 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:03:44 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:04:45 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:06:46 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:06:47 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:06:47 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:07:47 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:09:48 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:09:48 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:09:48 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:10:48 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:12:50 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:12:50 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:12:50 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:13:50 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:15:51 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:15:52 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:15:52 CEST|Einstein@Home|Backing off 2 minutes and 25 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:18:19 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:20:21 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:20:23 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:20:23 CEST|Einstein@Home|Backing off 6 minutes and 22 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:26:45 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:28:46 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:28:47 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:28:47 CEST|Einstein@Home|Backing off 11 minutes and 12 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:40:00 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 05:42:01 CEST||Network error: a timeout was reached
Do 13 Apr 2006 05:42:01 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 05:42:01 CEST|Einstein@Home|Backing off 18 minutes and 12 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 06:00:15 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 06:01:40 CEST|QMC@HOME|Restarting result one_st2dna_nodelete.538_0 using Amolqc-alpha version 506
Do 13 Apr 2006 06:01:40 CEST|Einstein@Home|Pausing result r1_1462.0__1633_S4R2a_1 (removed from memory)
Do 13 Apr 2006 06:02:16 CEST||Network error: a timeout was reached
Do 13 Apr 2006 06:02:16 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 06:02:16 CEST|Einstein@Home|Backing off 37 minutes and 20 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 06:39:37 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 06:41:38 CEST||Network error: a timeout was reached
Do 13 Apr 2006 06:41:38 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 06:41:38 CEST|Einstein@Home|Backing off 14 minutes and 40 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 06:49:01 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 06:49:01 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 06:49:01 CEST|Einstein@Home|Requesting 19148 seconds of new work
Do 13 Apr 2006 06:51:02 CEST||Network error: a timeout was reached
Do 13 Apr 2006 06:51:06 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 06:51:06 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 06:56:19 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 06:58:20 CEST||Network error: a timeout was reached
Do 13 Apr 2006 06:58:20 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 06:58:20 CEST|Einstein@Home|Backing off 1 hours, 23 minutes, and 5 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 07:01:40 CEST|QMC@HOME|Pausing result one_st2dna_nodelete.538_0 (removed from memory)
Do 13 Apr 2006 07:01:40 CEST|Einstein@Home|Restarting result r1_1462.0__1633_S4R2a_1 using albert version 455
Do 13 Apr 2006 07:06:36 CEST||Rescheduling CPU: application exited
Do 13 Apr 2006 07:06:36 CEST|Einstein@Home|Computation for result r1_1462.0__1634_S4R2a_1 finished
Do 13 Apr 2006 07:06:36 CEST|Einstein@Home|Starting result r1_1462.0__1632_S4R2a_0 using albert version 455
Do 13 Apr 2006 07:06:38 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:08:41 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:08:41 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:08:41 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:09:41 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:11:42 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:11:42 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:11:42 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:12:42 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:14:42 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:14:42 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:14:42 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:15:42 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:17:44 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:17:44 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:17:44 CEST|Einstein@Home|Backing off 1 minutes and 0 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:18:44 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:20:46 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:20:46 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:20:46 CEST|Einstein@Home|Backing off 1 minutes and 53 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:22:40 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:24:41 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:24:41 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:24:41 CEST|Einstein@Home|Backing off 1 minutes and 57 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:26:40 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:28:41 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:28:41 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:28:41 CEST|Einstein@Home|Backing off 2 minutes and 56 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:31:38 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:33:39 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:33:39 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 07:33:39 CEST|Einstein@Home|Backing off 36 minutes and 15 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 07:45:53 CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Do 13 Apr 2006 07:45:53 CEST|Einstein@Home|Reason: To fetch work
Do 13 Apr 2006 07:45:53 CEST|Einstein@Home|Requesting 26890 seconds of new work
Do 13 Apr 2006 07:47:55 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:47:55 CEST|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi failed: http error
Do 13 Apr 2006 07:47:55 CEST|Einstein@Home|No schedulers responded
Do 13 Apr 2006 07:48:55 CEST|Einstein@Home|Fetching scheduler list
Do 13 Apr 2006 07:50:56 CEST||Network error: a timeout was reached
Do 13 Apr 2006 07:51:00 CEST|Einstein@Home|Scheduler list fetch failed: http error
Do 13 Apr 2006 07:51:00 CEST|Einstein@Home|4 consecutive failures fetching scheduler list - deferring 604800 seconds
Do 13 Apr 2006 08:09:55 CEST|Einstein@Home|Started upload of r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 08:11:57 CEST||Network error: a timeout was reached
Do 13 Apr 2006 08:11:57 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1634_S4R2a_1_0: http error
Do 13 Apr 2006 08:11:57 CEST|Einstein@Home|Backing off 1 hours, 44 minutes, and 45 seconds on upload of file r1_1462.0__1634_S4R2a_1_0
Do 13 Apr 2006 08:21:26 CEST|Einstein@Home|Started upload of r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 08:23:28 CEST||Network error: a timeout was reached
Do 13 Apr 2006 08:23:28 CEST|Einstein@Home|Temporarily failed upload of r1_1462.0__1635_S4R2a_2_0: http error
Do 13 Apr 2006 08:23:28 CEST|Einstein@Home|Backing off 3 hours, 58 minutes, and 28 seconds on upload of file r1_1462.0__1635_S4R2a_2_0
Do 13 Apr 2006 09:09:31 CEST||Rescheduling CPU: application exited

BTW: It is funny, that the machine still uploads results. It just does not love the scheduler any more.

Steve Cressman
Steve Cressman
Joined: 9 Feb 05
Posts: 104
Credit: 139654
RAC: 0

@Wurgl It is very rude to

@Wurgl
It is very rude to refer to anyone as "boy".
I am an old man with grandchildren. I got 2 words for you but I can't say them or I would be rude too! I only tried to offer an explaination for what occured!

The part that you cut and pasted only shows one request for the master file but near the bottom it says it tried 4 times, so you get the one week backoff. That 4 may be in error but since it thinks it was 4 you can't argue with it. Check back farther in your messages and see if there where 3 more times, if not there submit a bug report.

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

archae86
archae86
Joined: 6 Dec 05
Posts: 3145
Credit: 7023624931
RAC: 1809255

RE: Not sure but I think

Message 28066 in response to message 28062

Quote:

Not sure but I think the scheduler after 10 failed attempts to get work it trys to get the master file(scheduler list) to make sure that it is trying the right address. Then ten more attempts before it tries to get master file again. This is repeated until after the 4th failure to get the master file at which point it backs off for a week(604800sec). There are also incremental backoffs between attempts to get work.

So it looks like the op of this thread must have been hitting the update button in order to get to that point because I don't think the outage was long enough to drive it to that point.

However I do agree that a week long backoff is excessive. After 4 failures to get master file it should backoff no more than 24hrs IMO.

I had two machines hit the six day thing.

For one appears that the attempt to get the scheduler list came after four failed attempts to get work--with relatively modest backoffs:

9:15:08 p.m. request 2897 seconds work/report 1
9:22:37 p.m. request 3846 seconds work/report 1
9:58:04 p.m. request 6812 seconds work/report 1
11:43:18 p.m. request 16524 seconds work/report 1
(these stayed at report 1 despite new result completions, since the subsequent uploads were failing)

So after just 2.5 hours after the first failure, I got the seven-day penalty flag thrown regarding work requests. Zero updates or other micromanagement was involved. It may or may not be somehow relevant that my "connect to network about every" parameter is set to 0.1 days.

The upload requests appeared to operating on an independent schedule and backoff scheme. It appears to me that each result attempting to upload has its own independent backoff. My last upload attempt failure was attempted at 12:57:29 a.m., while the very next try at 01:34:09 a.m. was successful. All my pending uploads subsequently succeeded on their first attempt, with the last cleared at 2:53:08 a.m.

[later edit] After making my post on the results on my primary machine, I examined the message logs for my other three.

Case 2: Machine made just two requests for more work before the scheduler list request was posted, failed, and the seven-day penalty was declared--about twenty minutes after the first failed work request.

Case 3: Machine totalled eleven work request -- scheduler list was never requested, resumed normal work fetching without intervention. Failed requests spanned a three hour ten minute interval from first failure through last.

So I think the number "4" may refer to multiple tries to a single scheduler list request. It certainly does not correlate with failed work requests across my sample of three machines.

It may be relevant that all my machines run trux's calibrating client at the tx36 revision level. So does the one host of the Original Poster that I checked.

Wurgl (speak^Wcrunching for Special: Off-Topic)
Wurgl (speak^Wc...
Joined: 11 Feb 05
Posts: 321
Credit: 140550008
RAC: 0

RE: The part that you cut

Message 28067 in response to message 28065

Quote:
The part that you cut and pasted only shows one request for the master file but near the bottom it says it tried 4 times, so you get the one week backoff. That 4 may be in error but since it thinks it was 4 you can't argue with it. Check back farther in your messages and see if there where 3 more times, if not there submit a bug report.

I have all the output of boinc starting with 10th of May 2005.

$ grep Fetching nohup.out
2006-01-15 22:04:32 [orbit@home] Fetching master file
2006-01-15 22:04:32 [orbit@home] Fetching master file
2006-01-25 22:06:07 [orbit@home] Fetching master file
2006-01-25 22:06:07 [orbit@home] Fetching master file
2006-02-02 22:43:02 [orbit@home] Fetching master file
2006-02-02 22:43:02 [orbit@home] Fetching master file
2006-02-12 22:44:40 [orbit@home] Fetching master file
2006-02-12 22:44:40 [orbit@home] Fetching master file
2006-02-18 02:02:26 [Einstein@Home] Fetching master file
2006-02-18 02:02:26 [Einstein@Home] Fetching master file
2006-02-22 22:46:18 [orbit@home] Fetching master file
2006-02-22 22:46:18 [orbit@home] Fetching master file
2006-03-04 22:47:59 [orbit@home] Fetching master file
2006-03-04 22:47:59 [orbit@home] Fetching master file
2006-03-14 22:49:36 [orbit@home] Fetching master file
2006-03-14 22:49:36 [orbit@home] Fetching master file
2006-03-24 22:51:15 [orbit@home] Fetching master file
2006-03-24 22:51:15 [orbit@home] Fetching master file
2006-04-13 07:48:55 [Einstein@Home] Fetching scheduler list

Sorry, there is no second attempt to fetch the scheduler list since ever.

BTW: Sorry, is dude better?

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6534
Credit: 284710168
RAC: 110462

RE: RE: Well, not

Message 28068 in response to message 28059

Quote:
Quote:
Well, not exactly. :-)
I know with Windoze there is BoincView - a great farm implement - so you can retry any/all Boinc functions across one's connected flock to invoke said behaviour, with I think at most two mouse clicks for the entire crew! It works for me anyhows.

With BoincView you cannot upload all your results where the upload failed, with two click. :(
You need two clicks for every result, that's true, because you can't mark more than one.

cu,
Michael


Nah! :-)
- You select 'all locations' on the left....
- hit the 'Transfers' tab which will show the outstanding up/downloads in the big pane....
- then the second from the right icon along the top row of buttons....
- tooltip will say 'Retry selected file transfer'....
- but press and hold the little down arrow ( very small, hard to see ) which is part of the right hand side of this control....
- drop down shows 'Retry all transfers'...
- hit it, then just confirm 'yes' with the pop-up....

Earlier on it took me a month to find that little down arrow, and I was doing precisely that ( two clicks per result ) up til then! :-(
Then I discovered all the other little down arrows for the other functions...... :-)
Cheers, Mike.

(edit) I also recall that the schedulers and the uploaders are quite asynchronous - different machines in fact - so there's a possible source of confusion due to that.

I have made this letter longer than usual because I lack the time to make it shorter ...

... and my other CPU is a Ryzen 5950X :-) Blaise Pascal

m.mitch
m.mitch
Joined: 11 Feb 05
Posts: 187
Credit: 11025628
RAC: 0

RE: @Wurgl It is very rude

Message 28070 in response to message 28065

Quote:
@Wurgl
It is very rude to refer to anyone as "boy".
I am an old man with grandchildren. I got 2 words for you but I can't say them or I would be rude too! I only tried to offer an explaination for what occured!

Now that is very much a nationality thing. Here, it can be a term of endearment, "I like the boy!"

Although the same statement in the USoA seems to provoke a fight. I don't understand why and I don't want too.

networkman
networkman
Joined: 22 Jan 05
Posts: 98
Credit: 7140649
RAC: 0

I like visiting each of my

I like visiting each of my machines. Occasionally I'll even talk to them, just like the plants. I think they like the company and they seem to produce very well. :)

"You're just jealous because the voices don't talk to you."

"Chance is irrelevant. We will succeed."
- Seven of Nine

M. Schmitt
M. Schmitt
Joined: 27 Jun 05
Posts: 478
Credit: 15872262
RAC: 0

RE: Nah! :-) - You select

Message 28072 in response to message 28068

Quote:

Nah! :-)
- You select 'all locations' on the left....
- hit the 'Transfers' tab which will show the outstanding up/downloads in the big pane....
- then the second from the right icon along the top row of buttons....
- tooltip will say 'Retry selected file transfer'....
- but press and hold the little down arrow ( very small, hard to see ) which is part of the right hand side of this control....
- drop down shows 'Retry all transfers'...
- hit it, then just confirm 'yes' with the pop-up....

Earlier on it took me a month to find that little down arrow, and I was doing precisely that ( two clicks per result ) up til then! :-(
Then I discovered all the other little down arrows for the other functions...... :-)
Cheers, Mike.

(edit) I also recall that the schedulers and the uploaders are quite asynchronous - different machines in fact - so there's a possible source of confusion due to that.

Thx to you too. :)
AndyK allready corrected me and the next time when upload is blocked, I'l save a bench of clicks. ;)
Most of the small arrows were allready explored, just this one must have been hidden by some magic.

Happy Easter (if you like so)
Michael

Scott Brown
Scott Brown
Joined: 9 Feb 05
Posts: 38
Credit: 215235
RAC: 0

RE: RE: @Wurgl It is very

Message 28073 in response to message 28070

Quote:
Quote:
@Wurgl
It is very rude to refer to anyone as "boy".
I am an old man with grandchildren. I got 2 words for you but I can't say them or I would be rude too! I only tried to offer an explaination for what occured!

Now that is very much a nationality thing. Here, it can be a term of endearment, "I like the boy!"

Although the same statement in the USoA seems to provoke a fight. I don't understand why and I don't want too.

In the USA, the "boy" as an insult is tied to racial issues historically...
but Steve Cressman appears to be Canadian...

Wurgl (speak^Wcrunching for Special: Off-Topic)
Wurgl (speak^Wc...
Joined: 11 Feb 05
Posts: 321
Credit: 140550008
RAC: 0

RE: In the USA, the "boy"

Message 28074 in response to message 28073

Quote:

In the USA, the "boy" as an insult is tied to racial issues historically...
but Steve Cressman appears to be Canadian...

Ich könnte natürlich auch auf Deutsch schreiben. Wenn ich meine Muttersprache verwende, dann ist mir jede mögliche zweite Bedeutung eines jeden Wortes bekannt. Dass mir diese Kenntnis in anderen Sprachen teilweise fehlt, mag man mir oder meinem Englischlehrer ankreiden.

Leider versteht mich dann ein grosser Teil der Mitleser nicht :-(

And have fun with the translation done by google, I think my English is still better than that of any machine.

Quote:


I could write naturally also on German. If I mean native language use, then me each possible second meaning of each word is well-known. That this knowledge in other languages is missing to me partly, one may hold against to me or my English teacher.

Unfortunately then a large part of the Mitleser does not understand me: - (

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.