Panic Mode On (115) Server Problems?

Message boards : Number crunching : Panic Mode On (115) Server Problems?
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 . . . 31 · Next

AuthorMessage
Profile Wiggo
Avatar

Send message
Joined: 24 Jan 00
Posts: 27625
Credit: 261,360,520
RAC: 489
Australia
Message 1981177 - Posted: 19 Feb 2019, 22:38:24 UTC

All back to business as usual here now.

Cheers.
ID: 1981177 · Report as offensive
Profile Cactus Bob
Avatar

Send message
Joined: 19 May 99
Posts: 209
Credit: 10,924,287
RAC: 29
Canada
Message 1981181 - Posted: 19 Feb 2019, 23:17:28 UTC

Just checked the SSP and the RTS is at 69.
Creation rate is 53/s. not good

Luck for me a have a low RAC so will prob not run out before the servers catch up and stabilize.

Bob
Sometimes I wonder, what happened to all the people I gave directions to?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SETI@home classic workunits 4,321
SETI@home classic CPU time 22,169 hours
ID: 1981181 · Report as offensive
Profile Kissagogo27 Special Project $75 donor
Avatar

Send message
Joined: 6 Nov 99
Posts: 711
Credit: 8,032,827
RAC: 62
France
Message 1981253 - Posted: 20 Feb 2019, 9:06:44 UTC

Some DL errors this night ( here UTC+1 ) with fine UL


19-Feb-2019 22:22:50 [SETI@home] Requesting new tasks for CPU and AMD/ATI GPU
19-Feb-2019 22:22:53 [SETI@home] Scheduler request completed: got 5 new tasks
19-Feb-2019 22:22:55 [SETI@home] Started download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
19-Feb-2019 22:22:56 [SETI@home] Started download of ap_18fe19ab_B4_P0_00263_20190219_25671.wu
19-Feb-2019 22:22:56 [SETI@home] Started download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
19-Feb-2019 22:22:56 [SETI@home] Started download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu
19-Feb-2019 22:22:56 [SETI@home] Started download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
19-Feb-2019 22:23:02 [SETI@home] Temporarily failed download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu: transient HTTP error
19-Feb-2019 22:23:02 [SETI@home] Backing off 00:03:02 on download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
19-Feb-2019 22:23:02 [SETI@home] Temporarily failed download of ap_18fe19ab_B4_P0_00263_20190219_25671.wu: transient HTTP error
19-Feb-2019 22:23:02 [SETI@home] Backing off 00:02:39 on download of ap_18fe19ab_B4_P0_00263_20190219_25671.wu
19-Feb-2019 22:23:02 [SETI@home] Temporarily failed download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu: transient HTTP error
19-Feb-2019 22:23:02 [SETI@home] Backing off 00:02:37 on download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
19-Feb-2019 22:23:02 [SETI@home] Temporarily failed download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu: transient HTTP error
19-Feb-2019 22:23:02 [SETI@home] Backing off 00:02:54 on download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu
19-Feb-2019 22:23:02 [SETI@home] Temporarily failed download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu: transient HTTP error
19-Feb-2019 22:23:02 [SETI@home] Backing off 00:03:58 on download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
19-Feb-2019 22:23:05 [---] Project communication failed: attempting access to reference site
19-Feb-2019 22:23:07 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 22:39:37 [SETI@home] Computation for task 09no06aa.1395.42927.12.39.138_1 finished
19-Feb-2019 22:39:37 [SETI@home] Starting task 09no06aa.20081.44972.11.38.82_0
19-Feb-2019 22:39:39 [SETI@home] Started upload of 09no06aa.1395.42927.12.39.138_1_r1637062679_0
19-Feb-2019 22:39:44 [SETI@home] Finished upload of 09no06aa.1395.42927.12.39.138_1_r1637062679_0
19-Feb-2019 23:01:46 [SETI@home] Computation for task 09no06aa.20081.44972.11.38.82_0 finished
19-Feb-2019 23:01:46 [SETI@home] Starting task 09no06aa.9531.47835.14.41.154_0
19-Feb-2019 23:01:48 [SETI@home] Started upload of 09no06aa.20081.44972.11.38.82_0_r833943041_0
19-Feb-2019 23:01:52 [SETI@home] Finished upload of 09no06aa.20081.44972.11.38.82_0_r833943041_0
19-Feb-2019 23:05:56 [SETI@home] Started download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
19-Feb-2019 23:05:56 [SETI@home] Started download of ap_18fe19ab_B4_P0_00263_20190219_25671.wu
19-Feb-2019 23:05:56 [SETI@home] Started download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
19-Feb-2019 23:05:56 [SETI@home] Started download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu
19-Feb-2019 23:05:56 [SETI@home] Started download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
19-Feb-2019 23:05:57 [SETI@home] Sending scheduler request: To fetch work.
19-Feb-2019 23:05:57 [SETI@home] Reporting 2 completed tasks
19-Feb-2019 23:05:57 [SETI@home] Requesting new tasks for CPU and AMD/ATI GPU
19-Feb-2019 23:06:00 [SETI@home] Scheduler request completed: got 0 new tasks
19-Feb-2019 23:06:00 [SETI@home] No tasks sent
19-Feb-2019 23:06:00 [SETI@home] No tasks are available for AstroPulse v7
19-Feb-2019 23:06:00 [SETI@home] Tasks for NVIDIA GPU are available, but your preferences are set to not accept them
19-Feb-2019 23:06:00 [SETI@home] Tasks for Intel GPU are available, but your preferences are set to not accept them
19-Feb-2019 23:06:02 [SETI@home] Temporarily failed download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu: transient HTTP error
19-Feb-2019 23:06:02 [SETI@home] Backing off 00:07:01 on download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu
19-Feb-2019 23:06:02 [SETI@home] Temporarily failed download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu: transient HTTP error
19-Feb-2019 23:06:02 [SETI@home] Backing off 00:07:59 on download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
19-Feb-2019 23:06:05 [---] Project communication failed: attempting access to reference site
19-Feb-2019 23:06:07 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 23:06:08 [SETI@home] Temporarily failed download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu: transient HTTP error
19-Feb-2019 23:06:08 [SETI@home] Backing off 00:07:15 on download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
19-Feb-2019 23:06:11 [---] Project communication failed: attempting access to reference site
19-Feb-2019 23:06:12 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 23:07:41 [SETI@home] Finished download of ap_18fe19ab_B4_P0_00263_20190219_25671.wu
19-Feb-2019 23:07:54 [SETI@home] Temporarily failed download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu: transient HTTP error
19-Feb-2019 23:07:54 [SETI@home] Backing off 00:06:02 on download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
19-Feb-2019 23:07:57 [---] Project communication failed: attempting access to reference site
19-Feb-2019 23:07:58 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 23:13:04 [SETI@home] Started download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu
19-Feb-2019 23:13:23 [SETI@home] Started download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
19-Feb-2019 23:13:30 [SETI@home] Temporarily failed download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu: transient HTTP error
19-Feb-2019 23:13:30 [SETI@home] Backing off 00:13:27 on download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
19-Feb-2019 23:13:34 [---] Project communication failed: attempting access to reference site
19-Feb-2019 23:13:36 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 23:13:57 [SETI@home] Started download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
19-Feb-2019 23:14:02 [SETI@home] Started download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
19-Feb-2019 23:14:08 [SETI@home] Temporarily failed download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu: transient HTTP error
19-Feb-2019 23:14:08 [SETI@home] Backing off 00:13:59 on download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
19-Feb-2019 23:14:11 [---] Project communication failed: attempting access to reference site
19-Feb-2019 23:14:12 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 23:14:55 [SETI@home] Temporarily failed download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu: transient HTTP error
19-Feb-2019 23:14:55 [SETI@home] Backing off 00:12:36 on download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu
19-Feb-2019 23:14:58 [---] Project communication failed: attempting access to reference site
19-Feb-2019 23:14:59 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 23:15:52 [SETI@home] Temporarily failed download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu: transient HTTP error
19-Feb-2019 23:15:52 [SETI@home] Backing off 00:12:56 on download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
19-Feb-2019 23:15:55 [---] Project communication failed: attempting access to reference site
19-Feb-2019 23:15:56 [---] Internet access OK - project servers may be temporarily down.
19-Feb-2019 23:23:58 [SETI@home] Computation for task 09no06aa.9531.47835.14.41.154_0 finished
19-Feb-2019 23:23:58 [SETI@home] Starting task 09no06aa.16239.45381.10.37.232_0
19-Feb-2019 23:24:05 [SETI@home] Started upload of 09no06aa.9531.47835.14.41.154_0_r926042299_0
19-Feb-2019 23:24:08 [SETI@home] Finished upload of 09no06aa.9531.47835.14.41.154_0_r926042299_0
19-Feb-2019 23:24:25 [SETI@home] Computation for task 09no06aa.16239.45381.10.37.232_0 finished
19-Feb-2019 23:24:25 [SETI@home] Starting task 09no06aa.16239.45381.10.37.250_1
19-Feb-2019 23:24:28 [SETI@home] Started upload of 09no06aa.16239.45381.10.37.232_0_r1114372215_0
19-Feb-2019 23:24:32 [SETI@home] Finished upload of 09no06aa.16239.45381.10.37.232_0_r1114372215_0
19-Feb-2019 23:24:52 [SETI@home] Computation for task 09no06aa.16239.45381.10.37.250_1 finished
19-Feb-2019 23:24:52 [SETI@home] Starting task 28dc06ai.8866.24203.15.42.211_1
19-Feb-2019 23:24:59 [SETI@home] Started upload of 09no06aa.16239.45381.10.37.250_1_r564246745_0
19-Feb-2019 23:25:02 [SETI@home] Finished upload of 09no06aa.16239.45381.10.37.250_1_r564246745_0
19-Feb-2019 23:47:04 [SETI@home] Computation for task 28dc06ai.8866.24203.15.42.211_1 finished
19-Feb-2019 23:47:04 [SETI@home] Starting task blc31_2bit_guppi_58406_04592_HIP116971_0042.13574.409.21.44.14.vlar_0
19-Feb-2019 23:47:06 [SETI@home] Started upload of 28dc06ai.8866.24203.15.42.211_1_r1659993850_0
19-Feb-2019 23:47:10 [SETI@home] Finished upload of 28dc06ai.8866.24203.15.42.211_1_r1659993850_0
20-Feb-2019 00:14:43 [SETI@home] Started download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
20-Feb-2019 00:14:43 [SETI@home] Started download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
20-Feb-2019 00:14:43 [SETI@home] Started download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu
20-Feb-2019 00:14:43 [SETI@home] Started download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
20-Feb-2019 00:15:16 [SETI@home] Sending scheduler request: To fetch work.
20-Feb-2019 00:15:16 [SETI@home] Reporting 4 completed tasks
20-Feb-2019 00:15:16 [SETI@home] Requesting new tasks for CPU and AMD/ATI GPU
20-Feb-2019 00:15:18 [SETI@home] Scheduler request completed: got 0 new tasks
20-Feb-2019 00:15:18 [SETI@home] No tasks sent
20-Feb-2019 00:15:18 [SETI@home] No tasks are available for AstroPulse v7
20-Feb-2019 00:15:18 [SETI@home] Tasks for NVIDIA GPU are available, but your preferences are set to not accept them
20-Feb-2019 00:15:18 [SETI@home] Tasks for Intel GPU are available, but your preferences are set to not accept them
20-Feb-2019 00:15:22 [SETI@home] Finished download of ap_18fe19ab_B4_P1_00286_20190219_26132.wu
20-Feb-2019 00:15:24 [SETI@home] Finished download of ap_18fe19ab_B5_P0_00210_20190219_27119.wu
20-Feb-2019 00:15:44 [SETI@home] Finished download of ap_18fe19ab_B4_P0_00264_20190219_25671.wu
20-Feb-2019 00:15:44 [SETI@home] Finished download of ap_18fe19ab_B5_P0_00211_20190219_27119.wu

ID: 1981253 · Report as offensive
Profile Bill Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 30 Nov 05
Posts: 282
Credit: 6,916,194
RAC: 60
United States
Message 1981521 - Posted: 21 Feb 2019, 16:59:22 UTC

So I had a problem in the old Panic Mode On thread (message located here, where after the maintenance shutdown, I would have a full slug of CPU tasks, but I am only getting one GPU task at a time. Sometimes, no GPU tasks even come through and other projects with a resource share of 0 start crunching GPU tasks. At the time I had several AP7 GPU tasks that were stopping due to computation errors, but I haven't had that problem for a few weeks now. I don't see how the server could be restricting me because of that. Any thoughts?

I did see a line in the event log that made me curious. I searched for the line on the forums, but it was from nine years ago. I'm not sure if it is even valid anymore. I'm not in front of that computer but when I am I'll post what I discovered.
Seti@home classic: 1,456 results, 1.613 years CPU time
ID: 1981521 · Report as offensive
Profile Brent Norman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 1 Dec 99
Posts: 2786
Credit: 685,657,289
RAC: 835
Canada
Message 1981522 - Posted: 21 Feb 2019, 17:11:32 UTC - in response to Message 1981521.  

Which event log entry is of concern? Please post startup.
Which computer?

For one, I would try suspending all other projects for awhile so you are only requesting from seti and see if that changes anything.
ID: 1981522 · Report as offensive
Profile Bill Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 30 Nov 05
Posts: 282
Credit: 6,916,194
RAC: 60
United States
Message 1981529 - Posted: 21 Feb 2019, 17:46:53 UTC - in response to Message 1981522.  

Let me pull up the event log this evening when I have a moment. I'll post information then.

Computer this is happening to is here.
Seti@home classic: 1,456 results, 1.613 years CPU time
ID: 1981529 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 21035
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1981534 - Posted: 21 Feb 2019, 18:08:34 UTC

You appear to be using an unreleased version of BOINC on that computer - is that the one you were working with Richard to trace the crazy peak_flops problem on?
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1981534 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13158
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1981538 - Posted: 21 Feb 2019, 18:14:48 UTC - in response to Message 1981534.  

Likely is. I think he is running the beta client from appveyor that Richard had him test. If so, it is likely it is from the current 7.15.0 master branch and that branch has a serious problem with work fetch caused by a commit that was developed to resolve a bug I filed. Fixed my bug but broke work fetch badly. Anything is possible now with the current master branch with inability to get work for various situations.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1981538 · Report as offensive
Profile Bill Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 30 Nov 05
Posts: 282
Credit: 6,916,194
RAC: 60
United States
Message 1981543 - Posted: 21 Feb 2019, 18:28:42 UTC - in response to Message 1981538.  

Likely is. I think he is running the beta client from appveyor that Richard had him test. If so, it is likely it is from the current 7.15.0 master branch and that branch has a serious problem with work fetch caused by a commit that was developed to resolve a bug I filed. Fixed my bug but broke work fetch badly. Anything is possible now with the current master branch with inability to get work for various situations.
Yeah, good point, I'm running the unreleased version of BOINC. I suppose troubleshooting this might be wasting time. I'm still crunching, I just don't have the backlog that one would normally like.
Seti@home classic: 1,456 results, 1.613 years CPU time
ID: 1981543 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13158
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1981548 - Posted: 21 Feb 2019, 19:01:56 UTC - in response to Message 1981543.  

If you have any sort of max_concurrent statement on any project, that is what is likely interfering with work fetch. Or if you have a large REC debt to other projects. DA wrote the code to not request work if any project had an abundance of work onboard to complete. So you will likely not be able to maintain any sort of normal cache. The way the client now works is more of a just in time system.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1981548 · Report as offensive
Profile Bill Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 30 Nov 05
Posts: 282
Credit: 6,916,194
RAC: 60
United States
Message 1981588 - Posted: 21 Feb 2019, 22:50:13 UTC - in response to Message 1981548.  

If you have any sort of max_concurrent statement on any project, that is what is likely interfering with work fetch. Or if you have a large REC debt to other projects. DA wrote the code to not request work if any project had an abundance of work onboard to complete. So you will likely not be able to maintain any sort of normal cache. The way the client now works is more of a just in time system.
I do not have any max_concurrent, so we're good there. I did just realize I have resource share for seti beta set to 100, but I have that project suspended since I'm done testing for now. I have set the resource share to 0 just in case...but this problem was happening before I used the beta.

As for my event log, this is the typical verbiage I get when attempting to get more tasks:

2/21/2019 4:33:21 PM | SETI@home | Requesting new tasks for CPU
2/21/2019 4:33:22 PM | SETI@home | Scheduler request completed: got 0 new tasks
2/21/2019 4:33:22 PM | SETI@home | No tasks sent
2/21/2019 4:33:22 PM | SETI@home | No tasks are available for AstroPulse v7
2/21/2019 4:33:22 PM | SETI@home | No tasks are available for SETI@home v8
2/21/2019 4:33:22 PM | SETI@home | Tasks for Intel GPU are available, but your preferences are set to not accept them
2/21/2019 4:33:22 PM | SETI@home | This computer has reached a limit on tasks in progress


That is when it is looking for more CPU work. When a GPU tasks completes, this is all I get:

2/21/2019 4:28:14 PM | SETI@home | Reporting 1 completed tasks
2/21/2019 4:28:14 PM | SETI@home | Requesting new tasks for CPU and AMD/ATI GPU
2/21/2019 4:28:16 PM | SETI@home | Scheduler request completed: got 1 new tasks

Seti@home classic: 1,456 results, 1.613 years CPU time
ID: 1981588 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14511
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1981589 - Posted: 21 Feb 2019, 22:59:45 UTC - in response to Message 1981588.  

I suggest you add "sched_op_debug" to your Event Log options. It's relatively quiet, but it shows much more clearly what is being requested (or not) at each scheduler contact.
ID: 1981589 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13158
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1981590 - Posted: 21 Feb 2019, 23:16:30 UTC - in response to Message 1981589.  

I suggest you add "sched_op_debug" to your Event Log options. It's relatively quiet, but it shows much more clearly what is being requested (or not) at each scheduler contact.

+1
Always run that option myself for the log.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1981590 · Report as offensive
Profile Bill Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 30 Nov 05
Posts: 282
Credit: 6,916,194
RAC: 60
United States
Message 1981620 - Posted: 22 Feb 2019, 4:07:14 UTC - in response to Message 1981589.  

I suggest you add "sched_op_debug" to your Event Log options. It's relatively quiet, but it shows much more clearly what is being requested (or not) at each scheduler contact.

So before I retire for the evening, this is what has popped up so far:
2/21/2019 10:00:37 PM | SETI@home | [sched_op] CPU work request: 1615101.02 seconds; 0.00 devices
2/21/2019 10:00:37 PM | SETI@home | [sched_op] AMD/ATI GPU work request: 0.00 seconds; 0.00 devices
2/21/2019 10:00:38 PM | SETI@home | [sched_op] Server version 709
I will post more tomorrow.
Seti@home classic: 1,456 results, 1.613 years CPU time
ID: 1981620 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13158
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1981621 - Posted: 22 Feb 2019, 4:17:58 UTC - in response to Message 1981620.  

Yep, you aren't asking for gpu work. I never saw a notice about Eric updating the Seti servers with the updated software for the schedulers you tested at Beta.

But you now have an established APR for gpu work here at Main. That should prevent you from getting any more -197 errors because of an incorrectly calculated time to completion. So you could revert back to the stock 7.14.2 client and see if you can process gpu work now. You might want to run down your cache to only a dozen or so tasks for the experiment. That way you won't throw away a ton of tasks if the error is still present on the stock client now that you have a reasonable APR.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1981621 · Report as offensive
Profile Unixchick Project Donor
Avatar

Send message
Joined: 5 Mar 12
Posts: 815
Credit: 2,361,516
RAC: 22
United States
Message 1981624 - Posted: 22 Feb 2019, 5:36:38 UTC

status page isn't updating, so something might be going wrong. I hope by posting about it, it will magically fix itself. Maybe it is just a small hiccup. Is there a schedule of when hiccups happen?
ID: 1981624 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14511
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1981639 - Posted: 22 Feb 2019, 9:06:08 UTC - in response to Message 1981621.  
Last modified: 22 Feb 2019, 9:06:43 UTC

Yep, you aren't asking for gpu work. I never saw a notice about Eric updating the Seti servers with the updated software for the schedulers you tested at Beta.

But you now have an established APR for gpu work here at Main.
I haven't heard about any software update either, although we're working to get the patch into the official server release code (#3027).

Bill only has an established APR for MB work here - he's had that all along, before all this started. It was AP work that started the trouble, and that still needs the patch.
ID: 1981639 · Report as offensive
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1981661 - Posted: 22 Feb 2019, 15:47:49 UTC - in response to Message 1981624.  

Is there a schedule of when hiccups happen?


Of course there is :) I believe they input a random number table from a text book and have been invoking it systematically, at random and throwing those results as a seed into a random generator. This produces that highly reliable schedule of random events :)

Sorry, just fooling around. Its Friday!!!

Tom
A proud member of the OFA (Old Farts Association).
ID: 1981661 · Report as offensive
Profile Bill Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 30 Nov 05
Posts: 282
Credit: 6,916,194
RAC: 60
United States
Message 1981778 - Posted: 23 Feb 2019, 3:29:49 UTC

So I think most of today S@H was not requesting GPU work. I seem to keep getting info such as this:

2/22/2019 9:12:03 PM | SETI@home | [sched_op] CPU work request: 1619990.50 seconds; 0.00 devices
2/22/2019 9:12:03 PM | SETI@home | [sched_op] AMD/ATI GPU work request: 0.00 seconds; 0.00 devices
However, I did have E@H enabled as a 0 work load project, and it kept processing GPU tasks for that. I suspended E@H, and then got this:

2/22/2019 9:22:17 PM | SETI@home | [sched_op] CPU work request: 1621367.64 seconds; 0.00 devices
2/22/2019 9:22:17 PM | SETI@home | [sched_op] AMD/ATI GPU work request: 1.00 seconds; 1.00 devices
2/22/2019 9:22:19 PM | SETI@home | Scheduler request completed: got 1 new tasks
2/22/2019 9:22:19 PM | SETI@home | [sched_op] Server version 709
2/22/2019 9:22:19 PM | SETI@home | Project requested delay of 303 seconds
2/22/2019 9:22:19 PM | SETI@home | [sched_op] estimated total CPU task duration: 0 seconds
2/22/2019 9:22:19 PM | SETI@home | [sched_op] estimated total AMD/ATI GPU task duration: 1447 seconds

And I finally was able to download a single GPU task (amazing!). I'll let this run overnight like this and see what happens.
Seti@home classic: 1,456 results, 1.613 years CPU time
ID: 1981778 · Report as offensive
Stephen "Heretic" Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Sep 12
Posts: 5557
Credit: 192,787,363
RAC: 628
Australia
Message 1981786 - Posted: 23 Feb 2019, 6:07:56 UTC

. . I have a small issue someone might be able to help me with. During the kerfuffle when we lost the storage device, along with a great number of failed downloads and later failed validations due to missing files I had one other casualty. One task which had completed went through the upload process but failed to complete, yet apparently went far enough that the result files were removed from my drive and the transfer from my file transfer screeen, but remains in the Manager list as "uploading". I presume this simply means that the client didn't update the client_state.xml to remove the listing by marking it as reported. I could not abort the transfer because it had been removed. I cannot abort the task because it's state is "being uploaded". I tried the ghost recovery protocol but this achieved nothing (possibly because there were no actual ghosted tasks) and even tried the benchmarking option in the hope it would download the master file but none of these methods worked. I gave up and waited for it to be removed from the system hoping that might somehow trigger an accounting for the task but it is still there.

. . So does anyone have any ideas on how to get Boinc Manager to 'realise' that this task is no longer here? I am sick of seeing it sitting there taunting me ... :(

Stephen

:)
ID: 1981786 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 . . . 31 · Next

Message boards : Number crunching : Panic Mode On (115) Server Problems?


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