Message boards : Number crunching : Upload Errors
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4

AuthorMessage
Bob Giel

Send message
Joined: 4 Sep 05
Posts: 4
Credit: 392,992
RAC: 0
Message 25994 - Posted: 23 Oct 2013, 19:25:50 UTC

LHC@home 1.0 10/23/2013 2:13:52 PM Started upload of sd_sixt43_350_2.3_4D_e2.62__1__s__62.31_60.32__10_12__6__65_1_sixvf_boinc81_0_0
LHC@home 1.0 10/23/2013 2:13:52 PM Started upload of sd_sixt43_350_2.3_4D_e2.62__1__s__62.31_60.32__10_12__6__65_1_sixvf_boinc81_0_6
LHC@home 1.0 10/23/2013 2:13:54 PM [error] Error reported by file upload server: can't open log file '../log_boinc05/file_upload_handler.log' (errno: 9)
LHC@home 1.0 10/23/2013 2:13:54 PM [error] Error reported by file upload server: can't open log file '../log_boinc05/file_upload_handler.log' (errno: 9)
LHC@home 1.0 10/23/2013 2:13:54 PM Temporarily failed upload of sd_sixt43_350_2.3_4D_e2.62__1__s__62.31_60.32__10_12__6__65_1_sixvf_boinc81_0_0: transient upload error
LHC@home 1.0 10/23/2013 2:13:54 PM Backing off 3 hr 12 min 44 sec on upload of sd_sixt43_350_2.3_4D_e2.62__1__s__62.31_60.32__10_12__6__65_1_sixvf_boinc81_0_0

Unless my trifocals need replacing, wouldn't the above indicated error mean that the "log file" the upload server is trying to write to is either missing or the application trying to write to it doesn't have enough "permission" to do so?
ID: 25994 · Report as offensive     Reply Quote
Richard Haselgrove

Send message
Joined: 27 Oct 07
Posts: 185
Credit: 3,297,428
RAC: 0
Message 25996 - Posted: 23 Oct 2013, 19:56:18 UTC - in response to Message 25966.  

Please everybody, READ before posting.

Oh Bob, Bob, Bob - two copies in two separate threads? Why not plaster it all over the front page as well?

Oh, sorry - the admins have done that already, haven't they?
ID: 25996 · Report as offensive     Reply Quote
Profile dr_mabuse
Avatar

Send message
Joined: 30 Dec 05
Posts: 57
Credit: 816,219
RAC: 1
Message 26004 - Posted: 24 Oct 2013, 0:28:48 UTC

I have upload errors since 3 days. more than a year before I had also upload errors for 7 of my BOINC applications- the only one to work was the World Community grid. I posted the problem on the discussion fora of 5 projects but no one had a solution. The problem disappeared finally after installing the current BOINC version.
This here seems to be another problem. I use to create a report file and will publish a part of it here, hoping that it may help:
23.10.2013 23:17:46 | LHC@home 1.0 | [fxd] starting upload, upload_offset -1
23.10.2013 23:17:46 | LHC@home 1.0 | [http] HTTP_OP::libcurl_exec(): ca-bundle 'C:\Program Files\BOINC\ca-bundle.crt'
23.10.2013 23:17:46 | LHC@home 1.0 | [http] HTTP_OP::libcurl_exec(): ca-bundle set
23.10.2013 23:17:46 | LHC@home 1.0 | Started upload of sd_sixt15_640_1.3_4D__1__s__62.31_60.32__10_12__6__30_1_sixvf_boinc74_0_0
23.10.2013 23:17:46 | LHC@home 1.0 | [file_xfer] URL: http://lhcathomeclassic.cern.ch/sixtrack_cgi/file_upload_handler
23.10.2013 23:17:46 | LHC@home 1.0 | [fxd] starting upload, upload_offset -1
23.10.2013 23:17:46 | LHC@home 1.0 | [http] HTTP_OP::libcurl_exec(): ca-bundle 'C:\Program Files\BOINC\ca-bundle.crt'
23.10.2013 23:17:46 | LHC@home 1.0 | [http] HTTP_OP::libcurl_exec(): ca-bundle set
23.10.2013 23:17:46 | LHC@home 1.0 | Started upload of sd_sixt15_640_1.3_4D__1__s__62.31_60.32__6_8__6__25_1_sixvf_boinc39_1_6
23.10.2013 23:17:46 | LHC@home 1.0 | [file_xfer] URL: http://lhcathomeclassic.cern.ch/sixtrack_cgi/file_upload_handler
23.10.2013 23:17:46 | LHC@home 1.0 | [http] [ID#533] Info: About to connect() to lhcathomeclassic.cern.ch port 80 (#0)
23.10.2013 23:17:46 | LHC@home 1.0 | [http] [ID#533] Info: Trying 128.142.138.22...
23.10.2013 23:17:46 | LHC@home 1.0 | [http] [ID#534] Info: About to connect() to lhcathomeclassic.cern.ch port 80 (#1)
23.10.2013 23:17:46 | LHC@home 1.0 | [http] [ID#534] Info: Trying 128.142.138.22...
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Info: Connected to lhcathomeclassic.cern.ch (128.142.138.22) port 80 (#0)
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Info: Connected to lhcathomeclassic.cern.ch (128.142.138.22) port 80 (#0)
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server: POST /sixtrack_cgi/file_upload_handler HTTP/1.1
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.0.64)
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server: Host: lhcathomeclassic.cern.ch
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server: Accept: */*
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server: Accept-Encoding: deflate, gzip
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server: Content-Type: application/x-www-form-urlencoded
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server: Content-Length: 326
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#533] Sent header to server:
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Info: Connected to lhcathomeclassic.cern.ch (128.142.138.22) port 80 (#1)
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Info: Connected to lhcathomeclassic.cern.ch (128.142.138.22) port 80 (#1)
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server: POST /sixtrack_cgi/file_upload_handler HTTP/1.1
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.0.64)
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server: Host: lhcathomeclassic.cern.ch
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server: Accept: */*
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server: Accept-Encoding: deflate, gzip
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server: Content-Type: application/x-www-form-urlencoded
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server: Content-Length: 324
23.10.2013 23:17:47 | LHC@home 1.0 | [http] [ID#534] Sent header to server:
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Received header from server: HTTP/1.1 200 OK
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Received header from server: Date: Wed, 23 Oct 2013 21:17:51 GMT
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Received header from server: Server: Apache
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Received header from server: Content-Length: 159
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Received header from server: Connection: close
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Received header from server: Content-Type: text/plain; charset=UTF-8
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Received header from server:
23.10.2013 23:17:51 | LHC@home 1.0 | [http] [ID#533] Info: Closing connection #0
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Received header from server: HTTP/1.1 200 OK
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Received header from server: Date: Wed, 23 Oct 2013 21:17:51 GMT
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Received header from server: Server: Apache
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Received header from server: Content-Length: 159
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Received header from server: Connection: close
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Received header from server: Content-Type: text/plain; charset=UTF-8
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Received header from server:
23.10.2013 23:17:52 | LHC@home 1.0 | [http] [ID#534] Info: Closing connection #1
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] http op done; retval 0 (Success)
23.10.2013 23:17:52 | LHC@home 1.0 | [error] Error reported by file upload server: can't open log file '../log_boinc05/file_upload_handler.log' (errno: 9)
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] parsing upload response: <data_server_reply> <status>1</status> <message>can't open log file '../log_boinc05/file_upload_handler.log' (errno: 9)</message></data_server_reply>
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] parsing status: -127
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] http op done; retval 0 (Success)
23.10.2013 23:17:52 | LHC@home 1.0 | [error] Error reported by file upload server: can't open log file '../log_boinc05/file_upload_handler.log' (errno: 9)
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] parsing upload response: <data_server_reply> <status>1</status> <message>can't open log file '../log_boinc05/file_upload_handler.log' (errno: 9)</message></data_server_reply>
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] parsing status: -127
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] file transfer status -127 (transient upload error)
23.10.2013 23:17:52 | LHC@home 1.0 | Temporarily failed upload of sd_sixt15_640_1.3_4D__1__s__62.31_60.32__10_12__6__30_1_sixvf_boinc74_0_0: transient upload error
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] project-wide xfer delay for 11366.596881 sec
23.10.2013 23:17:52 | LHC@home 1.0 | Backing off 4 hr 49 min 47 sec on upload of sd_sixt15_640_1.3_4D__1__s__62.31_60.32__10_12__6__30_1_sixvf_boinc74_0_0
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] file transfer status -127 (transient upload error)
23.10.2013 23:17:52 | LHC@home 1.0 | Temporarily failed upload of sd_sixt15_640_1.3_4D__1__s__62.31_60.32__6_8__6__25_1_sixvf_boinc39_1_6: transient upload error
23.10.2013 23:17:52 | LHC@home 1.0 | [file_xfer] project-wide xfer delay for 14519.534898 sec
23.10.2013 23:17:52 | LHC@home 1.0 | Backing off 3 hr 46 min 47 sec on upload of sd_sixt15_640_1.3_4D__1__s__62.31_60.32__6_8__6__25_1_sixvf_boinc39_1_6
23.10.2013 23:21:31 | | Suspending computation - CPU is busy
23.10.2013 23:21:41 | | Resuming computation
23.10.2013 23:55:59 | LHC@home 1.0 | Sending scheduler request: Requested by project.
23.10.2013 23:55:59 | LHC@home 1.0 | Not requesting tasks: some task is suspended via Manager
23.10.2013 23:55:59 | LHC@home 1.0 | [http] HTTP_OP::init_post(): http://lhcathomeclassic.cern.ch/sixtrack_cgi/cgi
23.10.2013 23:55:59 | LHC@home 1.0 | [http] HTTP_OP::libcurl_exec(): ca-bundle set
23.10.2013 23:55:59 | LHC@home 1.0 | [http] [ID#1] Info: About to connect() to lhcathomeclassic.cern.ch port 80 (#0)
23.10.2013 23:55:59 | LHC@home 1.0 | [http] [ID#1] Info: Trying 128.142.138.22...
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Info: Connected to lhcathomeclassic.cern.ch (128.142.138.22) port 80 (#0)
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Info: Connected to lhcathomeclassic.cern.ch (128.142.138.22) port 80 (#0)
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: POST /sixtrack_cgi/cgi HTTP/1.1
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.0.64)
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: Host: lhcathomeclassic.cern.ch
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: Accept: */*
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: Content-Length: 17685
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server: Expect: 100-continue
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Sent header to server:
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server: HTTP/1.1 100 Continue
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server: HTTP/1.1 200 OK
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server: Date: Wed, 23 Oct 2013 21:55:59 GMT
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server: Server: Apache
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server: Connection: close
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server: Transfer-Encoding: chunked
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server: Content-Type: text/xml
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Received header from server:
23.10.2013 23:56:00 | LHC@home 1.0 | [http] [ID#1] Info: Closing connection #0
23.10.2013 23:56:01 | LHC@home 1.0 | Scheduler request completed

Thanks for any advice. I stopped the 4 last WUs in my input queue, running out at 29th.oct.13
Greetings from Germany
Dr.Mabuse
ID: 26004 · Report as offensive     Reply Quote
Profile Roger Parsons
Avatar

Send message
Joined: 18 Dec 11
Posts: 17
Credit: 928,185
RAC: 0
Message 26014 - Posted: 24 Oct 2013, 8:01:00 UTC - in response to Message 25980.  

This MUST help. Thanks a lot. Eric.



Eric - all running again normally - uploads and downloads - so the fix seems to have worked. Thanks to you and all those who sorted it out. R.
"Any fool can appreciate mountain scenery. It takes a man of discernment to appreciate the Fens."
[Harry Godwin - pollen analyst - circa 1932]
ID: 26014 · Report as offensive     Reply Quote
Yacob

Send message
Joined: 1 Dec 12
Posts: 11
Credit: 5,844,526
RAC: 0
Message 26026 - Posted: 24 Oct 2013, 13:21:53 UTC - in response to Message 26014.  

Thanks to Eric and to whoever who fixed it!!
ID: 26026 · Report as offensive     Reply Quote
Neal Watkins
Avatar

Send message
Joined: 14 Nov 05
Posts: 31
Credit: 678,725
RAC: 59
Message 26031 - Posted: 24 Oct 2013, 20:40:05 UTC

As an ex unix sysadmin, I found that 50% of all unix problems turn out to be permission problems...
ID: 26031 · Report as offensive     Reply Quote
henry

Send message
Joined: 15 Sep 13
Posts: 73
Credit: 5,763
RAC: 0
Message 26033 - Posted: 25 Oct 2013, 5:27:56 UTC - in response to Message 26031.  

...not a Unix sysadmin here but as a seasoned Linux user I know you're right. Now a question for you. How does a good sysadmin prevent a permission problem from becoming a bigger problem? Does one accomplish that by changing the system then disappearing for several days? Or does one stick around and monitor the system in case one goofed a permission while making said changes?
ID: 26033 · Report as offensive     Reply Quote
Richard Haselgrove

Send message
Joined: 27 Oct 07
Posts: 185
Credit: 3,297,428
RAC: 0
Message 26034 - Posted: 25 Oct 2013, 17:12:32 UTC - in response to Message 26031.  

As an ex unix sysadmin, I found that 50% of all unix problems turn out to be permission problems...

Interesting. Another BOINC project couldn't be contacted for scheduler reports and work fetches for several hours overnight. The working day has just started in their part of the globe, and they managed to fix it quickly once on site. I just got this reply from their server guy:

Thanks for the heads up Richard!

It turned out to be a permissions change on a directory due to auto-update of mod_fcgi.

If an operating system can't auto-update its own modules without breaking permissions...
ID: 26034 · Report as offensive     Reply Quote
henry

Send message
Joined: 15 Sep 13
Posts: 73
Credit: 5,763
RAC: 0
Message 26035 - Posted: 25 Oct 2013, 18:03:16 UTC - in response to Message 26034.  

As an ex unix sysadmin, I found that 50% of all unix problems turn out to be permission problems...

Interesting. Another BOINC project couldn't be contacted for scheduler reports and work fetches for several hours overnight. The working day has just started in their part of the globe, and they managed to fix it quickly once on site. I just got this reply from their server guy:

Thanks for the heads up Richard!

It turned out to be a permissions change on a directory due to auto-update of mod_fcgi.

If an operating system can't auto-update its own modules without breaking permissions...


That's not necessarily the fault of the operating system. It's more likely the fault of the software updater application, perhaps even params passed to the updater by the incoming package. And I'm not sure fault is even the right word to use as it implies a mistake was made when in fact changing the permissions might have been a necessity or the lesser of 2 evils. There are many factors to consider.

The incident you report is an example of why I don't allow my hosts to auto-update, not ever. I auto-download updates but I choose when to install the modules and I do so only when I have time to watch the system for a while and do at least some minimal checks to verify that important stuff wasn't broken. Anything less is shoddy administration IMHO, especially on a system such as a BOINC server where one wants more than the average measure of reliability. Call me paranoid, pedantic, whatever, I just like things to run smoothly.

6 bangers are for wussies.
ID: 26035 · Report as offensive     Reply Quote
FruehwF

Send message
Joined: 21 Aug 12
Posts: 9
Credit: 2,941,516
RAC: 0
Message 26143 - Posted: 22 Jan 2014, 14:58:25 UTC



22.01.2014 13:43:04 UT
22.01.2014 14:43:04 | LHC@home 1.0 | Server can't open log file (../log_boinc05/scheduler.log)


Eric please contact your Admin.
ID: 26143 · Report as offensive     Reply Quote
Helix Von Smelix

Send message
Joined: 28 Sep 04
Posts: 4
Credit: 27,104,553
RAC: 0
Message 26145 - Posted: 22 Jan 2014, 16:39:10 UTC - in response to Message 26143.  



22.01.2014 13:43:04 UT
22.01.2014 14:43:04 | LHC@home 1.0 | Server can't open log file (../log_boinc05/scheduler.log)


Eric please contact your Admin.

Same for me. :-(
ID: 26145 · Report as offensive     Reply Quote
Sunny129
Avatar

Send message
Joined: 12 Dec 05
Posts: 31
Credit: 9,709,398
RAC: 0
Message 26147 - Posted: 22 Jan 2014, 16:53:08 UTC

1/22/2014 11:51:26 AM | LHC@home 1.0 | Project is temporarily shut down for maintenance


seems like standard maintenance to me...wonder why others are getting the "Server can't open log file (../log_boinc05/scheduler.log)" message instead...
ID: 26147 · Report as offensive     Reply Quote
henry

Send message
Joined: 15 Sep 13
Posts: 73
Credit: 5,763
RAC: 0
Message 26150 - Posted: 22 Jan 2014, 18:28:18 UTC - in response to Message 26147.  

The "can't open log file" is usually the first indication that the upload server's disk is full. The "project temporarily shutdown for maintenance" message is the indication that someone finally wised up and is making some room on the disk.

Due to inattention and/or lack of understanding of how a BOINC server works on the part of the admins, this situation repeats itself regularly at this project. It doesn't happen this frequently at any other project I crunch just this one. And now, as if that's not enough, they want to compound the problem by increasing the number of big files the server has to store by a factor of at least 5 I would estimate, with their looney tunes "multistage tasks" or "mega- tasks" or whatever name one wants to apply to the disaster in the making. Yep, shooting themselves in the foot over and over and over. Pathetic.


6 bangers are for wussies.
ID: 26150 · Report as offensive     Reply Quote
Profile Viking69
Avatar

Send message
Joined: 24 Jul 05
Posts: 56
Credit: 5,496,750
RAC: 123
Message 26558 - Posted: 25 May 2014, 23:24:50 UTC - in response to Message 25909.  

I'm glad the project is continuing, but I still do not see my avatar from Gravatar.com. I have confirmed that the web site has my image, and it is working on other BOINC projects.

Me too. I have about 50 WU's to upload.

Oh, And I am not seeing personal avatars show up. At least I 'm not seeming mine from gravitar.com


Let's crunch for our future.
ID: 26558 · Report as offensive     Reply Quote
Eric Mcintosh
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 12 Jul 11
Posts: 857
Credit: 1,619,050
RAC: 0
Message 26561 - Posted: 26 May 2014, 5:56:30 UTC - in response to Message 26150.  

Yes Henry; just saw this message. We are volunteers too (some of us) and
we have no budget or authority. Disk space is incredibly cheap these
days but we can't get it for admin reasons. No excuse though for the
sloppy management of what we have.

My reputation has been built on RFP (reliability, functionality,
performance) and I am shamed. Eric.
ID: 26561 · Report as offensive     Reply Quote
Eric Mcintosh
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 12 Jul 11
Posts: 857
Credit: 1,619,050
RAC: 0
Message 26562 - Posted: 26 May 2014, 5:58:08 UTC - in response to Message 26558.  

Well this is a new one too me. I am looking at a black
open top sports car shown with your message. Eric.
ID: 26562 · Report as offensive     Reply Quote
Profile Grubix

Send message
Joined: 3 Jul 08
Posts: 20
Credit: 8,281,604
RAC: 0
Message 26569 - Posted: 27 May 2014, 12:17:41 UTC

I have a lot of download errors:

Di 27 Mai 2014 14:10:41 CEST | LHC@home 1.0 | Scheduler request completed: got 1 new tasks
Di 27 Mai 2014 14:10:43 CEST | LHC@home 1.0 | [http] HTTP_OP::init_get(): http://lhcathomeclassic.cern.ch/sixtrack/download/2db/sd_LHC6.525_300_250_1.8_6D_blev__1__s__64.31_59.32__2_4__6__55_1_sixvf_boinc28.zip
Di 27 Mai 2014 14:10:43 CEST | LHC@home 1.0 | Started download of sd_LHC6.525_300_250_1.8_6D_blev__1__s__64.31_59.32__2_4__6__55_1_sixvf_boinc28.zip
Di 27 Mai 2014 14:10:43 CEST | LHC@home 1.0 | [file_xfer] URL: http://lhcathomeclassic.cern.ch/sixtrack/download/2db/sd_LHC6.525_300_250_1.8_6D_blev__1__s__64.31_59.32__2_4__6__55_1_sixvf_boinc28.zip
Di 27 Mai 2014 14:10:43 CEST | LHC@home 1.0 | [http] [ID#9] Info:  About to connect() to lhcathomeclassic.cern.ch port 80 (#0)
Di 27 Mai 2014 14:10:43 CEST | LHC@home 1.0 | [http] [ID#9] Info:    Trying 128.142.138.22...
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Info:  Connected to lhcathomeclassic.cern.ch (128.142.138.22) port 80 (#0)
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Sent header to server: GET /sixtrack/download/2db/sd_LHC6.525_300_250_1.8_6D_blev__1__s__64.31_59.32__2_4__6__55_1_sixvf_boinc28.zip HTTP/1.1
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Sent header to server: User-Agent: BOINC client (i686-pc-linux-gnu 7.0.27)
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Sent header to server: Host: lhcathomeclassic.cern.ch
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Sent header to server: Accept: */*
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Sent header to server: Accept-Encoding: deflate, gzip
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Sent header to server: Content-Type: application/x-www-form-urlencoded
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Sent header to server:
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: HTTP/1.1 404 Not Found
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Date: Tue, 27 May 2014 12:10:44 GMT
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Server: Apache
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Vary: accept-language,accept-charset
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Accept-Ranges: bytes
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Connection: close
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Transfer-Encoding: chunked
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Content-Type: text/html; charset=iso-8859-1
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server: Content-Language: en
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Received header from server:
Di 27 Mai 2014 14:10:44 CEST |  | [http_xfer] [ID#9] HTTP: wrote 305 bytes
Di 27 Mai 2014 14:10:44 CEST |  | [http_xfer] [ID#9] HTTP: wrote 57 bytes
Di 27 Mai 2014 14:10:44 CEST |  | [http_xfer] [ID#9] HTTP: wrote 87 bytes
Di 27 Mai 2014 14:10:44 CEST |  | [http_xfer] [ID#9] HTTP: wrote 2 bytes
Di 27 Mai 2014 14:10:44 CEST |  | [http_xfer] [ID#9] HTTP: wrote 206 bytes
Di 27 Mai 2014 14:10:44 CEST |  | [http_xfer] [ID#9] HTTP: wrote 1 bytes
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [http] [ID#9] Info:  Closing connection #0
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [file_xfer] http op done; retval -224 (permanent HTTP error)
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | [file_xfer] file transfer status -224 (permanent HTTP error)
Di 27 Mai 2014 14:10:44 CEST | LHC@home 1.0 | Giving up on download of sd_LHC6.525_300_250_1.8_6D_blev__1__s__64.31_59.32__2_4__6__55_1_sixvf_boinc28.zip: permanent HTTP error


The line with "HTTP/1.1 404 Not Found" is probably the most important.

Bye, Grubix.
ID: 26569 · Report as offensive     Reply Quote
Profile Viking69
Avatar

Send message
Joined: 24 Jul 05
Posts: 56
Credit: 5,496,750
RAC: 123
Message 26592 - Posted: 7 Jun 2014, 21:39:35 UTC - in response to Message 26562.  

Well this is a new one too me. I am looking at a black
open top sports car shown with your message. Eric.



Yes, that is my avatar. A modified AC Cobra. It's funny that I can see other avatars here, but not mine. Oh well. technology mystery.
Let's crunch for our future.
ID: 26592 · Report as offensive     Reply Quote
Profile Viking69
Avatar

Send message
Joined: 24 Jul 05
Posts: 56
Credit: 5,496,750
RAC: 123
Message 26593 - Posted: 8 Jun 2014, 8:55:57 UTC - in response to Message 26592.  

Well this is a new one too me. I am looking at a black
open top sports car shown with your message. Eric.



Yes, that is my avatar. A modified AC Cobra. It's funny that I can see other avatars here, but not mine. Oh well. technology mystery.


I've tried to look at this from another of my computers, and I see the avatar here. Same OS and Browser version as my primary PC.
ID: 26593 · Report as offensive     Reply Quote
Previous · 1 · 2 · 3 · 4

Message boards : Number crunching : Upload Errors


©2022 CERN