Because aria2 can handle multiple downloads at once, it encounters
lots of errors in a session. aria2 returns the following exit status
based on the last error encountered.
- If all downloads were successful.
- If an unknown error occurred.
- If time out occurred.
- If a resource was not found.
- If aria2 saw the specified number of "resource not found" error.
- If a download aborted because download speed was too slow.
- If network problem occurred.
- If there were unfinished downloads. This error is only reported if
all finished downloads were successful and there were unfinished
downloads in a queue when aria2 exited by pressing Ctrl-C by an user
or sending TERM or INT signal.
- If remote server did not support resume when resume was required to
- If there was not enough disk space available.
- If piece length was different from one in .aria2 control file. See
- If aria2 was downloading same file at that moment.
- If aria2 was downloading same info hash torrent at that moment.
- If file already existed. See
- If renaming file failed. See
- If aria2 could not open existing file.
- If aria2 could not create new file or truncate existing file.
- If file I/O error occurred.
- If aria2 could not create directory.
- If name resolution failed.
- If aria2 could not parse Metalink document.
- If FTP command failed.
- If HTTP response header was bad or unexpected.
- If too many redirects occurred.
- If HTTP authorization failed.
- If aria2 could not parse bencoded file (usually ".torrent" file).
- If ".torrent" file was corrupted or missing information that aria2 needed.
- If Magnet URI was bad.
- If bad/unrecognized option was given or unexpected option argument
- If the remote server was unable to handle the request due to a
temporary overloading or maintenance.
- If aria2 could not parse JSON-RPC request.
- Reserved. Not used.
- If checksum validation failed.
An error occurred in a finished download will not be reported
as exit status.