Difference between revisions of "Error codes: Other BOINC errors"
(Adding FAQ 84) |
(adding table) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | 404: return "HTTP file not found"; | + | '''404: return "HTTP file not found";''' |
The 404 or Not Found error message is an HTTP standard response code indicating that the client was able to communicate with the server, but the server either could not find what was requested, or it was configured not to fulfill the request and not reveal the reason why. | The 404 or Not Found error message is an HTTP standard response code indicating that the client was able to communicate with the server, but the server either could not find what was requested, or it was configured not to fulfill the request and not reveal the reason why. | ||
| − | 407: return "HTTP proxy authentication failure"; | + | |
| + | '''407: return "HTTP proxy authentication failure";''' | ||
The server thinks that the HTTP data stream sent from the BOINC client was correct, but access to the URL resource requires the prior use of a proxy server that needs some authentication which has not been provided. This typically means you must log in (enter user ID and password) with the proxy server first. | The server thinks that the HTTP data stream sent from the BOINC client was correct, but access to the URL resource requires the prior use of a proxy server that needs some authentication which has not been provided. This typically means you must log in (enter user ID and password) with the proxy server first. | ||
| − | 416: return "HTTP range request error"; | + | |
| + | '''416: return "HTTP range request error";''' | ||
The server thinks that the HTTP data stream sent from the BOINC client contains a 'Range' request which specifies a range of bytes which can not be satisfied - because the resource being accessed does not cover this byte range. For example if the resource - an image file for example - has 1000 bytes and the Range requested is 500-1500, then it can not be satisfied. | The server thinks that the HTTP data stream sent from the BOINC client contains a 'Range' request which specifies a range of bytes which can not be satisfied - because the resource being accessed does not cover this byte range. For example if the resource - an image file for example - has 1000 bytes and the Range requested is 500-1500, then it can not be satisfied. | ||
| − | 500: return "HTTP internal server error"; | + | |
| + | '''500: return "HTTP internal server error";''' | ||
This is NOT a problem with your PC or internet connection! | This is NOT a problem with your PC or internet connection! | ||
| Line 19: | Line 22: | ||
This is a 'catch-all' error generated by BOINC. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the server site to locate and analyse these logs. | This is a 'catch-all' error generated by BOINC. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the server site to locate and analyse these logs. | ||
| − | 501: return "HTTP not implemented"; | + | |
| + | '''501: return "HTTP not implemented";''' | ||
The server does not support the HTTP method it finds in the HTTP data stream sent to it by the BOINC client. Or the method may be valid but not actually supported by the server. | The server does not support the HTTP method it finds in the HTTP data stream sent to it by the BOINC client. Or the method may be valid but not actually supported by the server. | ||
| − | 502: return "HTTP bad gateway"; | + | |
| + | '''502: return "HTTP bad gateway";''' | ||
A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request. | A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request. | ||
| Line 29: | Line 34: | ||
This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed. | This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed. | ||
| − | 503: return "HTTP service unavailable"; | + | |
| + | '''503: return "HTTP service unavailable";''' | ||
The server is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out. | The server is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out. | ||
| Line 36: | Line 42: | ||
2007-01-03 23:07:17 Message from server: The server is overloaded . You will be able to connect once the load level gets lower. | 2007-01-03 23:07:17 Message from server: The server is overloaded . You will be able to connect once the load level gets lower. | ||
| − | 504: return "HTTP gateway timeout"; | + | |
| + | '''504: return "HTTP gateway timeout";''' | ||
A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request. | A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request. | ||
| Line 46: | Line 53: | ||
This error means that the BOINC client couldn't connect to the IP address that the DNS server gave to BOINC. | This error means that the BOINC client couldn't connect to the IP address that the DNS server gave to BOINC. | ||
| − | See ERR_CONNECT -107 | + | |
| + | '''See ERR_CONNECT -107''' | ||
Error on file upload: socket read incomplete: asked for 12922, got 7422: No such file or directory | Error on file upload: socket read incomplete: asked for 12922, got 7422: No such file or directory | ||
| Line 54: | Line 62: | ||
Your copy of BOINC is telling the project servers to expect a file of size 12922 bytes, but the file it's actually sending is only 7422 bytes. Basically, BOINC is trying to send the wrong file, or a file of the wrong size. See error -127 for more information. | Your copy of BOINC is telling the project servers to expect a file of size 12922 bytes, but the file it's actually sending is only 7422 bytes. Basically, BOINC is trying to send the wrong file, or a file of the wrong size. See error -127 for more information. | ||
| + | |||
| + | |||
| + | {| class="wikitable" style="text-align: center;" | ||
| + | ! Original writer | ||
| + | ! Original FAQ | ||
| + | ! Date | ||
| + | |- | ||
| Jorden | | Jorden | ||
| − | | | + | | [http://boincfaq.mundayweb.com/index.php?language=1&view=84 84] |
| − | + | | 26-01-2007 | |
| − | | | + | |- |
| − | + | |} | |
| − | |||
| − | | | ||
| − | |||
| − | |||
| − | | | ||
Latest revision as of 14:53, 29 August 2016
404: return "HTTP file not found";
The 404 or Not Found error message is an HTTP standard response code indicating that the client was able to communicate with the server, but the server either could not find what was requested, or it was configured not to fulfill the request and not reveal the reason why.
407: return "HTTP proxy authentication failure";
The server thinks that the HTTP data stream sent from the BOINC client was correct, but access to the URL resource requires the prior use of a proxy server that needs some authentication which has not been provided. This typically means you must log in (enter user ID and password) with the proxy server first.
416: return "HTTP range request error";
The server thinks that the HTTP data stream sent from the BOINC client contains a 'Range' request which specifies a range of bytes which can not be satisfied - because the resource being accessed does not cover this byte range. For example if the resource - an image file for example - has 1000 bytes and the Range requested is 500-1500, then it can not be satisfied.
500: return "HTTP internal server error";
This is NOT a problem with your PC or internet connection!
The server encountered an unexpected condition that prevented it from fulfilling the request by the BOINC client for access to the requested URL.
This is a 'catch-all' error generated by BOINC. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the server site to locate and analyse these logs.
501: return "HTTP not implemented";
The server does not support the HTTP method it finds in the HTTP data stream sent to it by the BOINC client. Or the method may be valid but not actually supported by the server.
502: return "HTTP bad gateway";
A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request.
This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed.
503: return "HTTP service unavailable";
The server is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.
Some projects have their own error message for this. For example Primegrid: 2007-01-03 23:07:17 Message from server: The server is overloaded . You will be able to connect once the load level gets lower.
504: return "HTTP gateway timeout";
A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request.
This usually means that the upstream server is down (no response to the gateway/proxy), rather than that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.
system connect
This error means that the BOINC client couldn't connect to the IP address that the DNS server gave to BOINC.
See ERR_CONNECT -107
Error on file upload: socket read incomplete: asked for 12922, got 7422: No such file or directory together with Error on file upload: socket read incomplete: asked for 12922, got 7422: Transport endpoint is not connected
Your copy of BOINC is telling the project servers to expect a file of size 12922 bytes, but the file it's actually sending is only 7422 bytes. Basically, BOINC is trying to send the wrong file, or a file of the wrong size. See error -127 for more information.
| Original writer | Original FAQ | Date |
|---|---|---|
| Jorden | 84 | 26-01-2007 |
