Got server request to delete file '(file-name)'

From Unofficial BOINC Wiki

Jump to: navigation, search

Contents

[edit] General

Message Type: Information Message

This Message means that the Server no longer needs the file listed. Once the BOINC Client Software on your Host no longer needs this file it will be deleted.

[edit] Version Information

  • None.

[edit] Example Log(s)

[edit] No Work Sent - Removing File To Free Up Disk Space 

2005-07-05 10:32:43 [Einstein@Home] Sending scheduler request to
                                    http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2005-07-05 10:32:43 [Einstein@Home] Requesting 57743 seconds of work, returning 0 results
2005-07-05 10:32:44 [Einstein@Home] Scheduler request to
                                    http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2005-07-05 10:32:44 [Einstein@Home] Message from server: No work sent
2005-07-05 10:32:44 [Einstein@Home] Message from server: (there was work but you don't have enough
                                    disk space allocated)
2005-07-05 10:32:44 [Einstein@Home] Message from server: Removing file l1_0103.5 to free up
                                    disk space
2005-07-05 10:32:44 [Einstein@Home] Got server request to delete file l1_0103.5
2005-07-05 10:32:44 [Einstein@Home] No work from project
2005-07-05 10:32:45 [Einstein@Home] Deferring communication with project for 3 hours,
                                    59 minutes, and 58 seconds

Line-By-Line Explanation

This message indicates that the BOINC Client Software is making the attempt to connect to the Project's Scheduling Server.
Within the Scheduler Request Message we are asking for work to the tune of 57,743 seconds, and also returning no Results to the Project.
This message tells you that the communication session completed without error.
But, no work was sent...
The reason for no work is that you don't have enough free disk space.
The Scheduling Server is going to attempt to free space by removing a file.
  • Got server request to delete file '(file-name)'
The BOINC Daemon is going to remove the file.
However, this still results in no work from the Project.
Because of the communications failure, we will use Exponential Back-Off to prevent our Host from "flooding" the Server with communication requests. I mean, if it is busy, maybe we should give it a break.

[edit] Einstein@Home Multiple Results From One Work Unit Data File

Einstein@Home Work Unit "H1_0526.0
Einstein@Home Work Unit "H1_0526.0

One of the BOINC Powered Projects, Einstein@Home has the need for a fairly large Work Unit Data File. This file is fairly large, taking about 14 Mega-Bytes of space.

Because of this, the Project uses a method where the Participant's Computer will download the file once, and then will process multiple Results from that same Work Unit Data File until all the work that can be accomplished is finished. This allows the Participants that use Dial-Up Connections to avoid massive downloads for only one Result.

Example log courtesy of Mary Jo Kelleher 


2005-06-10 16:39:06 [Einstein@Home] Sending scheduler request to
                                    http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2005-06-10 16:39:06 [Einstein@Home] Requesting 5 seconds of work, returning 0 results
2005-06-10 16:39:07 [Einstein@Home] Scheduler request to
                                    http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2005-06-10 16:39:07 [Einstein@Home] Got server request to delete file H1_0358.5
2005-06-10 16:39:08 [Einstein@Home] Started download of H1_1167.5
2005-06-10 16:39:29 [Einstein@Home] Temporarily failed download of H1_1167.5: -106
2005-06-10 16:39:31 [Einstein@Home] Started download of H1_1167.5
2005-06-10 16:40:29 [Einstein@Home] Finished download of H1_1167.5
2005-06-10 16:40:29 [Einstein@Home] Throughput 256557 bytes/sec
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
2005-06-11 01:43:28 [Einstein@Home] Starting result H1_1167.5__1167.9_0.1_T10_Fin1_5 using
                                    einstein version 4.79
2005-06-12 01:53:32 [Einstein@Home] Computation for result H1_1167.5__1167.9_0.1_T10_Fin1_5
                                    finished
2005-06-12 01:53:32 [Einstein@Home] Starting result H1_1167.5__1167.8_0.1_T16_Fin1_0 using
                                    einstein version 4.79
2005-06-12 21:23:24 [Einstein@Home] Computation for result H1_1167.5__1167.8_0.1_T16_Fin1_0
                                    finished
2005-06-12 21:23:24 [Einstein@Home] Starting result H1_1167.5__1167.5_0.1_T17_Fin1_2 using
                                    einstein version 4.79
2005-06-13 12:23:27 [Einstein@Home] Computation for result H1_1167.5__1167.5_0.1_T17_Fin1_2
                                    finished
2005-06-13 12:23:27 [Einstein@Home] Starting result H1_1167.5__1167.7_0.1_T17_Fin1_3 using
                                    einstein version 4.79
2005-06-14 04:31:44 [Einstein@Home] Computation for result H1_1167.5__1167.7_0.1_T17_Fin1_3
                                    finished
2005-06-14 08:41:15 [Einstein@Home] Starting result H1_1167.5__1167.7_0.1_T18_Fin1_2 using
                                    einstein version 4.79
2005-06-15 06:42:59 [Einstein@Home] Computation for result H1_1167.5__1167.7_0.1_T18_Fin1_2
                                    finished
2005-06-15 08:11:19 [Einstein@Home] Starting result H1_1167.5__1167.6_0.1_T19_Fin1_0 using
                                    einstein version 4.79
2005-06-16 09:33:58 [Einstein@Home] Computation for result H1_1167.5__1167.6_0.1_T19_Fin1_0
                                    finished
2005-06-16 09:33:58 [Einstein@Home] Starting result H1_1167.5__1167.9_0.1_T19_Fin1_2 using
                                    einstein version 4.79
2005-06-17 10:19:45 [Einstein@Home] Computation for result H1_1167.5__1167.9_0.1_T19_Fin1_2
                                    finished
2005-06-17 10:19:45 [Einstein@Home] Starting result H1_1167.5__1167.5_0.1_T21_Fin1_3 using
                                    einstein version 4.79
2005-06-18 12:12:15 [Einstein@Home] Computation for result H1_1167.5__1167.5_0.1_T21_Fin1_3
                                    finished
2005-06-18 13:00:42 [Einstein@Home] Starting result H1_1167.5__1167.6_0.1_T22_Fin1_3 using
                                    einstein version 4.79
2005-06-19 15:14:13 [Einstein@Home] Computation for result H1_1167.5__1167.6_0.1_T22_Fin1_3
                                    finished
2005-06-19 15:14:13 [Einstein@Home] Starting result H1_1167.5__1167.6_0.1_T23_Fin1_2 using
                                    einstein version 4.79
2005-06-20 17:13:42 [Einstein@Home] Computation for result H1_1167.5__1167.6_0.1_T23_Fin1_2
                                    finished
2005-06-20 18:13:52 [Einstein@Home] Starting result H1_1167.5__1167.8_0.1_T25_Fin1_1 using
                                    einstein version 4.79
2005-06-21 22:58:09 [Einstein@Home] Computation for result H1_1167.5__1167.8_0.1_T25_Fin1_1
                                    finished
2005-06-21 22:58:09 [Einstein@Home] Starting result H1_1167.5__1167.5_0.1_T27_Fin1_1 using
                                    einstein version 4.79
2005-06-23 01:42:59 [Einstein@Home] Computation for result H1_1167.5__1167.5_0.1_T27_Fin1_1
                                    finished
2005-06-23 02:43:08 [Einstein@Home] Starting result H1_1167.5__1167.9_0.1_T27_Fin1_2 using
                                    einstein version 4.79
2005-06-24 07:00:57 [Einstein@Home] Computation for result H1_1167.5__1167.9_0.1_T27_Fin1_2
                                    finished
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
2005-06-24 00:11:11 [Einstein@Home] Sending scheduler request to
                                    http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2005-06-24 00:11:11 [Einstein@Home] Requesting 2 seconds of work, returning 0 results
2005-06-24 00:11:12 [Einstein@Home] Scheduler request to
                                    http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
2005-06-24 00:11:12 [Einstein@Home] Got server request to delete file H1_1167.5
2005-06-24 00:11:13 [Einstein@Home] Started download of H1_0152.0
2005-06-24 00:11:39 [Einstein@Home] Finished download of H1_0152.0
2005-06-24 00:11:39 [Einstein@Home] Throughput 585778 bytes/sec

Explanation

A new Work Unit, H1_1167.5 is downloaded, and the old Work Unit Data File (H1_0358.5) is deleted. A short time later the processing of Results from the Work Unit Data File H1_1167.5 begins.

As each Result is processed, it is uploaded (upload messages of the Result Data Files were not included) and another Result is started. In this case, there were over 10 Results obtained through the processing of this Work Unit Data File by this Participant.

When all the possible work has been "squeezed" out of this Work Unit Data File, it is deleted and another new one is downloaded. This process extended over a 10 day period. Pretty good return on one Work Unit Data File download.

Note:
The message "Got server request to delete file '(file-name)'" doesn't mean that a file is immediately deleted. If there are one or more Results that are still using the file, these Results will run to a normal finish and upload before the actual file-deletion takes place.

[edit] Also See

Retrieved from "http://www.boinc-wiki.info/Got_server_request_to_delete_file_%27%28file-name%29%27"
Personal tools