![]() ![]() This is serious badness and things are severely screwed up if this ever occur.ĬURLE_OPERATION_TIMEDOUT (28) - Operation timeout. (This error code was formerly known as CURLE_FTP_COULDNT_STOR_FILE.)ĬURLE_READ_ERROR (26) - There was a problem reading a local file or an error returned by the read callback.ĬURLE_OUT_OF_MEMORY (27) - A memory allocation request failed. The error buffer usually contains the server's explanation to this. For FTP, the server typically denied the STOR command. (This error code was formerly known as CURLE_HTTP_NOT_FOUND.)ĬURLE_WRITE_ERROR (23) - An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback.ĬURLE_UPLOAD_FAILED (25) - Failed starting the upload. This happens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously given size.ĬURLE_FTP_COULDNT_RETR_FILE (19) - This was either a weird reply to a 'RETR' command or a zero byte transfer complete.ĬURLE_QUOTE_ERROR (21) - When sending custom "QUOTE" commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command.ĬURLE_HTTP_RETURNED_ERROR (22) - This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400. If libcurl fails to parse that line, this return code is passed back.ĬURLE_FTP_CANT_GET_HOST (15) - An internal failure to lookup the host used for the new connection.ĬURLE_FTP_COULDNT_SET_TYPE (17) - Received an error when trying to set the transfer mode to binary or ascii.ĬURLE_PARTIAL_FILE (18) - A file transfer was shorter or larger than expected. The server is flawed.ĬURLE_FTP_WEIRD_227_FORMAT (14) - FTP servers return a 227-line as a response to a PASV command. This error code indicates that an unexpected code was returned.ĬURLE_FTP_WEIRD_PASV_REPLY (13) - libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. ![]() For FTP, this occurs while trying to change to the remote directory.ĬURLE_FTP_WEIRD_PASS_REPLY (11) - After having sent the FTP password to the server, libcurl expects a proper reply. The given remote server is probably not an OK FTP server.ĬURLE_REMOTE_ACCESS_DENIED (9) - We were denied access to the resource given in the URL. This error code implies that it got a strange or bad reply. The given remote host was not resolved.ĬURLE_COULDNT_CONNECT (7) - Failed to connect() to host or proxy.ĬURLE_FTP_WEIRD_SERVER_REPLY (8) - After connecting to an FTP server, libcurl expects to get a certain reply back. The given proxy host could not be resolved.ĬURLE_COULDNT_RESOLVE_HOST (6) - Couldn't resolve host. This is likely to be an internal error or problem.ĬURLE_URL_MALFORMAT (3) - The URL was not properly formatted.ĬURLE_COULDNT_RESOLVE_PROXY (5) - Couldn't resolve proxy. The support might be a compile-time option that you didn't use, it can be a misspelled protocol string or just a protocol libcurl has no code for.ĬURLE_FAILED_INIT (2) - Very early initialization code failed. The error codes are listed below along with a text message explaining the problem that was encountered.ĬURLE_UNSUPPORTED_PROTOCOL (1) - The URL you passed to libcurl used a protocol that this libcurl does not support. This error code appears in parenthesis next to the "failed" message after the webserver log transfer is attempted, e.g. an invalid username/password, remote server unreachable, remote log unreadable, etc.), Urchin will log an error code in the runtime output, as viewable in the Task History for the Profile. However, if some error is encountered during the transfer (e.g. Under normal circumstances, the transfer will be successful and no errors appear in the runtime log. Exception is basically useless.Error code list for failed FTP and HTTP remote webserver log transfersĪn Urchin Log Source can be configured to collect a webserver log from a remote server via FTP or HTTP. I don't know what configuration he can't find. I haved tried to search for the CONFIGURATION_NOT_FOUND but I could not find it in the firebase docs. I tried to search the google but no success of any solution for this. ![]() I have followed the guides how to set up auth for google account. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |