Now I am getting errors both while uploading and reporting...
Quote:
01/09/2010 8.29.55 Einstein@Home Started upload of h1_0863.00_S5R4__181_S5GC1a_1_0
01/09/2010 8.29.56 Einstein@Home [error] Error reported by file upload server: can't parse config file
01/09/2010 8.29.56 Einstein@Home [error] Error reported by file upload server: can't parse config file
01/09/2010 8.29.56 Einstein@Home Temporarily failed upload of h1_0863.00_S5R4__182_S5GC1a_1_0: transient upload error
01/09/2010 8.29.56 Einstein@Home Backing off 1 min 10 sec on upload of h1_0863.00_S5R4__182_S5GC1a_1_0
01/09/2010 8.29.56 Einstein@Home Temporarily failed upload of h1_0863.00_S5R4__181_S5GC1a_1_0: transient upload error
01/09/2010 8.29.56 Einstein@Home Backing off 1 min 0 sec on upload of h1_0863.00_S5R4__181_S5GC1a_1_0
01/09/2010 8.30.02 Einstein@Home update requested by user
01/09/2010 8.30.05 Einstein@Home Sending scheduler request: Requested by user.
01/09/2010 8.30.05 Einstein@Home Reporting 49 completed tasks, requesting new tasks
01/09/2010 8.30.28 Project communication failed: attempting access to reference site
01/09/2010 8.30.28 Einstein@Home Scheduler request failed: Failure when receiving data from the peer
01/09/2010 8.30.29 Internet access OK - project servers may be temporarily down.
The "can't parse config file" was a configuration error that lasted for about 4h yesterday and is fixed by now.
The machine that serves ABP work (the tasks starting with e.g. "p2030_53925_52612") was overloaded, partly because of the new participants we got since the discovery press release.
Yesterday we set up a new server for downloading ABP workunits to take that load from the old one that is now just used for upload.
This should have solved the (server side) issues with uploading.
To get back on topic, I guess no one have an idea what was wrong?
Not sure. The key is the "invalid signature" message, which could mean one of two things: a misconfiguration of the server (wrong upload keys), or a problem when uploading the file, basically a checksum error on the uploaded files resulting in a somewhat misleading error message. I haven't got any similar reports from other participants pointing to a configuration problem at that time, so I suspect the latter.
Since monday I started getting again errors while reporting.
23/11/2010 10.08.35 Einstein@Home Sending scheduler request: To report completed tasks.
23/11/2010 10.08.35 Einstein@Home Reporting 20 completed tasks, not requesting new tasks
23/11/2010 10.08.59 Project communication failed: attempting access to reference site
23/11/2010 10.08.59 Einstein@Home Scheduler request failed: Failure when receiving data from the peer
23/11/2010 10.09.00 Internet access OK - project servers may be temporarily down.
I can upload the results, but I cannot report them, and the list is growing...
Since monday I started getting again errors while reporting.
23/11/2010 10.08.35 Einstein@Home Sending scheduler request: To report completed tasks.
23/11/2010 10.08.35 Einstein@Home Reporting 20 completed tasks, not requesting new tasks
23/11/2010 10.08.59 Project communication failed: attempting access to reference site
23/11/2010 10.08.59 Einstein@Home Scheduler request failed: Failure when receiving data from the peer
23/11/2010 10.09.00 Internet access OK - project servers may be temporarily down.
I can upload the results, but I cannot report them, and the list is growing...
Exit and then restart Boinc, if that doesn't work restart the whole pc. It sounds like you have an IP problem connecting to Einstein.
A transient upload error is a
)
A transient upload error is a server problem. Nothing much you can do about that, that'll have to be done at the (mirror) site.
BOINC will try and retry all on its own to do the upload. There is nothing you have to do.
Right -- figured as much --
)
Right -- figured as much -- so the next move will be for the admins to figure out.
I see it on all my systems (XP, Vista, Win 7) at the moment. Given time of day, I'll look in on things tomorrow morning.
Now I am getting errors both
)
Now I am getting errors both while uploading and reporting...
The upload has
)
The upload has restarted.
Now it only wants to report 57 units...
What's happening?
The "can't parse config file"
)
The "can't parse config file" was a configuration error that lasted for about 4h yesterday and is fixed by now.
The machine that serves ABP work (the tasks starting with e.g. "p2030_53925_52612") was overloaded, partly because of the new participants we got since the discovery press release.
Yesterday we set up a new server for downloading ABP workunits to take that load from the old one that is now just used for upload.
This should have solved the (server side) issues with uploading.
BM
BM
RE: I've been getting this
)
To get back on topic, I guess no one have an idea what was wrong?
I have 10 WUs with the validate error, on 2 diff PCs, and I think all had the permanent upload error.
RE: To get back on topic, I
)
Not sure. The key is the "invalid signature" message, which could mean one of two things: a misconfiguration of the server (wrong upload keys), or a problem when uploading the file, basically a checksum error on the uploaded files resulting in a somewhat misleading error message. I haven't got any similar reports from other participants pointing to a configuration problem at that time, so I suspect the latter.
BM
BM
Since monday I started
)
Since monday I started getting again errors while reporting.
I can upload the results, but I cannot report them, and the list is growing...
RE: Since monday I started
)
Exit and then restart Boinc, if that doesn't work restart the whole pc. It sounds like you have an IP problem connecting to Einstein.
RE: RE: I can upload the
)
Already estarted the whole PC a couple times before posting, without success...
What is annoying is that the upload process works, but not the reporting process...