ok this is the errorlevel curl, i will quote each line which can be used in aria2c
1 Unsupported protocol. This build of curl has no support for this protocol.
maybe ?
2 Failed to initialize.
3 URL malformat. The syntax was not correct.
maybe ?
5 Couldn't resolve proxy. The given proxy host could not be resolved.
6 Couldn't resolve host. The given remote host was not resolved.
7 Failed to connect to host.
an option which can be included in aria2c for a multithread aspect ;)
8 FTP weird server reply. The server sent data curl couldn't parse.
9 FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that doesn't exist on the server.
11 FTP weird PASS reply. Curl couldn't parse the reply sent to the PASS request.
13 FTP weird PASV reply, Curl couldn't parse the reply sent to the PASV request.
14 FTP weird 227 format. Curl couldn't parse the 227-line the server sent.
15 FTP can't get host. Couldn't resolve the host IP we got in the 227-line.
17 FTP couldn't set binary. Couldn't change transfer method to binary.
18 Partial file. Only a part of the file was transferred.
an option which can be included in aria2c ;)
19 FTP couldn't download/access the given file, the RETR (or similar) command failed.
21 FTP quote error. A quote command returned error from the server.
22 HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f/--fail is used.
23 Write error. Curl couldn't write data to a local filesystem or similar.
an option which can be included in aria2c for a multithread aspect ;)
25 FTP couldn't STOR file. The server denied the STOR operation, used for FTP uploading.
26 Read error. Various reading problems.
27 Out of memory. A memory allocation request failed.
28 Operation timeout. The specified time-out period was reached according to the conditions.
an option which can be included in aria2c for a multithread aspect ;)
30 FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT command, try doing a transfer using PASV instead!
31 FTP couldn't use REST. The REST command failed. This command is used for resumed FTP transfers.
33 HTTP range error. The range "command" didn't work.
34 HTTP post error. Internal post-request generation error.
35 SSL connect error. The SSL handshaking failed.
36 FTP bad download resume. Couldn't continue an earlier aborted download.
an option which can be included in aria2c for a multithread aspect ;) and for all protocols ;)
37 FILE couldn't read file. Failed to open the file. Permissions?
42 Aborted by callback. An application told curl to abort the operation.
43 Internal error. A function was called with a bad parameter.
45 Interface error. A specified outgoing interface could not be used.
47 Too many redirects. When following redirects, curl hit the maximum amount.
an option which can be included in aria2c for a multithread aspect ;)
51 The peer's SSL certificate or SSH MD5 fingerprint was not ok
52 The server didn't reply anything, which here is considered an error.
53 SSL crypto engine not found
54 Cannot set SSL crypto engine as default
55 Failed sending network data
an option which can be included in aria2c for a multithread aspect ;)
56 Failure in receiving network data
58 Problem with the local certificate
59 Couldn't use specified SSL cipher
60 Peer certificate cannot be authenticated with known CA certificates
61 Unrecognized transfer encoding
63 Maximum file size exceeded
64 Requested FTP SSL level failed
65 Sending the data requires a rewind that failed
66 Failed to initialise SSL Engine
67 User, password or similar was not accepted and curl failed to login
68 File not found on TFTP server
69 Permission problem on TFTP server
70 Out of disk space on TFTP server
71 Illegal TFTP operation
72 Unknown TFTP transfer ID
73 File already exists (TFTP)
74 No such user (TFTP)
75 Character conversion failed
76 Character conversion functions required
77 Problem with reading the SSL CA cert (path? access rights?)
78 The resource referenced in the URL does not exist
79 An unspecified error occurred during the SSH session
80 Failed to shut down the SSL connection
XX There will appear more error codes here in future releases. The existing ones are meant to never change.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now as detailed as curl, in svn trunk aria2 exits with last error code encountered in the session.
I've not documented the error code yet. There are 8 error codes defined:
0 ... all finished.
1 ... unknown error.
2 ... time out
3 ... resource not found (404 for HTTP, for example)
4 ... max file not found (see --max-file-not-found option..)
5 ... too slow download speed (see --lowest-speed-limit option)
6 ... network problem (something bad happened in the network connection...)
7 ... in progress(user pressed Ctrl-C and there are unfinished downloads, for example)
Because these are exit status, normally it is not printed in the console when aria2 exits.
If you are using typical unix shell, type $? to print the exit status of the previous command.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1450148
Originator: NO
Could you show me the example for "errorlevel"?
Logged In: NO
ok this is the errorlevel curl, i will quote each line which can be used in aria2c
1 Unsupported protocol. This build of curl has no support for this protocol.
2 Failed to initialize.
3 URL malformat. The syntax was not correct.
5 Couldn't resolve proxy. The given proxy host could not be resolved.
6 Couldn't resolve host. The given remote host was not resolved.
7 Failed to connect to host.
8 FTP weird server reply. The server sent data curl couldn't parse.
9 FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that doesn't exist on the server.
11 FTP weird PASS reply. Curl couldn't parse the reply sent to the PASS request.
13 FTP weird PASV reply, Curl couldn't parse the reply sent to the PASV request.
14 FTP weird 227 format. Curl couldn't parse the 227-line the server sent.
15 FTP can't get host. Couldn't resolve the host IP we got in the 227-line.
17 FTP couldn't set binary. Couldn't change transfer method to binary.
18 Partial file. Only a part of the file was transferred.
19 FTP couldn't download/access the given file, the RETR (or similar) command failed.
21 FTP quote error. A quote command returned error from the server.
22 HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f/--fail is used.
23 Write error. Curl couldn't write data to a local filesystem or similar.
25 FTP couldn't STOR file. The server denied the STOR operation, used for FTP uploading.
26 Read error. Various reading problems.
27 Out of memory. A memory allocation request failed.
28 Operation timeout. The specified time-out period was reached according to the conditions.
30 FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT command, try doing a transfer using PASV instead!
31 FTP couldn't use REST. The REST command failed. This command is used for resumed FTP transfers.
33 HTTP range error. The range "command" didn't work.
34 HTTP post error. Internal post-request generation error.
35 SSL connect error. The SSL handshaking failed.
36 FTP bad download resume. Couldn't continue an earlier aborted download.
37 FILE couldn't read file. Failed to open the file. Permissions?
42 Aborted by callback. An application told curl to abort the operation.
43 Internal error. A function was called with a bad parameter.
45 Interface error. A specified outgoing interface could not be used.
47 Too many redirects. When following redirects, curl hit the maximum amount.
51 The peer's SSL certificate or SSH MD5 fingerprint was not ok
52 The server didn't reply anything, which here is considered an error.
53 SSL crypto engine not found
54 Cannot set SSL crypto engine as default
55 Failed sending network data
56 Failure in receiving network data
58 Problem with the local certificate
59 Couldn't use specified SSL cipher
60 Peer certificate cannot be authenticated with known CA certificates
61 Unrecognized transfer encoding
63 Maximum file size exceeded
64 Requested FTP SSL level failed
65 Sending the data requires a rewind that failed
66 Failed to initialise SSL Engine
67 User, password or similar was not accepted and curl failed to login
68 File not found on TFTP server
69 Permission problem on TFTP server
70 Out of disk space on TFTP server
71 Illegal TFTP operation
72 Unknown TFTP transfer ID
73 File already exists (TFTP)
74 No such user (TFTP)
75 Character conversion failed
76 Character conversion functions required
77 Problem with reading the SSL CA cert (path? access rights?)
78 The resource referenced in the URL does not exist
79 An unspecified error occurred during the SSH session
80 Failed to shut down the SSL connection
XX There will appear more error codes here in future releases. The existing ones are meant to never change.
Now as detailed as curl, in svn trunk aria2 exits with last error code encountered in the session.
I've not documented the error code yet. There are 8 error codes defined:
0 ... all finished.
1 ... unknown error.
2 ... time out
3 ... resource not found (404 for HTTP, for example)
4 ... max file not found (see --max-file-not-found option..)
5 ... too slow download speed (see --lowest-speed-limit option)
6 ... network problem (something bad happened in the network connection...)
7 ... in progress(user pressed Ctrl-C and there are unfinished downloads, for example)
Because these are exit status, normally it is not printed in the console when aria2 exits.
If you are using typical unix shell, type $? to print the exit status of the previous command.