Errno 54 is a connection reset by peer error:
"Connection reset by peer", /* 54 - ECONNRESET */
Usually - we see these when the return network kills the connection.
Example of such - seen in updates:
We are making the call out to the downloads/updater just fine — even manifest is showing as such:
Wed Jan 21 22:54:54 2015 Info: case started downloading files
Wed Jan 21 22:54:54 2015 Info: case waiting on download lock
Wed Jan 21 22:54:54 2015 Info: case acquired download lock
Wed Jan 21 22:54:54 2015 Info: case beginning download of remote file "http://updates-static.ironport.com/case/1.0/case/default/1392316781285111"
Wed Jan 21 22:55:18 2015 Info: case released download lock
Wed Jan 21 22:55:18 2015 Warning: case update failed
Wed Jan 21 22:55:18 2015 Debug: application update failed: ('aplib.oserrors.pyx aplib.oserrors.map_exception (aplib/aplib.oserrors.c:463)|28', "<class 'aplib.oserrors.ECONNRESET'>", '[Errno 54] Connection reset by peer', '[updater/app_thread.py _run_update|643] [updater/app_thread.py run_update|672] [updater/app_thread.py _download_files|513] [updater/app_thread.py download_files|533] [updater/app_thread.py _download_file|445] [updater/app_thread.py download_file|501] [updater/stream_file.py download|82] [updater/stream_file.py __iter__|130] [updater/stream_file.py __iter__|46] [_coro.pyx coro._coro.sched.with_timeout (coro/_coro.c:11537)|1086] [python2.6_7_i386_nothr/socket.py read|353] [socket.pyx coro._coro.sock.recv (coro/_coro.c:19519)|501] [socket.pyx coro._coro.sock._wait_for_read (coro/_coro.c:22874)|1031] [poller.pyx coro._coro.kqueue_poller._wait_for_read (coro/_coro.c:14776)|301] [poller.pyx coro._coro.kqueue_poller._wait_for_with_eof (coro/_coro.c:14719)|296] [pyrex_helpers.pyx coro._coro.raise_oserror_with_errno (coro/_coro.c:2769)|15] [aplib.oserrors.pyx aplib.oserrors.map_exception (aplib/aplib.oserrors.c:463)|28]')
I had changed over to the updates-static server to make sure we weren’t getting issues going through Akamai … but in the above, the call to the downloads/updater, getting the manifest of “what is changed/what is available”… Once that communication is sent back – right after the download lock, the update fails – so, something on the return path is killing the delivery.
Outside of changing the log levels to debug, reviewing the connection... try running a packet capture to see what is shown from point-to-point at the time of the Errno 54 generated.
Outside of the above - here is breakdown:
Email Error Codes
There are 2 format Error codes come in, x.x.x and xxx. (Where x stands for a number). Many people get a failed email message and just know that the mail didn’t go through. This message is called a bounceback. What does that message really mean?
The failed email notice tells you what is wrong and why the email failed.
This way you can determine if it is your email or the one you are sending to.
Email Error Codes have 3 Digits
(The 1st digit indicates if the response was good, bad, or incomplete)
If the 1st digit is a…
1 The Command was accepted, but the action is pending confirmation of a reply
2 The action was completed successfully
3 The command was accepted, but the action is pending receipt of further information.
4 The command was not accepted and the requested action did not occur. These are usually because of a temporary error or condition and one should try resending the request again.
5 The command was not accepted and the requested action did not occur. This is a permanent failure message. Something needs to be fixed before the action will work.
If the 2nd digit is a….
0 Syntax-Usually refers to a syntax error occurring.
1 Information-Reply to a request for information.
2 Connections-Refers to the channel transmitting
3 or 4 These are undefined still
5 Indicate the status of the receiver’s mail system
x.x.x Email Error Codes
X.1.X CODES
* X.1.0 – Other address status
* X.1.1 – Bad destination mailbox address
* X.1.2 – Bad destination system address
* X.1.3 – Bad destination mailbox address syntax
* X.1.4 – Destination mailbox address ambiguous
* X.1.5 – Destination mailbox address valid
* X.1.6 – Mailbox has moved
* X.1.7 – Bad sender’s mailbox address syntax
* X.1.8 – Bad sender’s system address
X.2.X CODES
* X.2.0 – Other or undefined mailbox status
* X.2.1 – Mailbox disabled, not accepting messages
* X.2.2 – Mailbox full
* X.2.3 – Message length exceeds administrative limit
* X.2.4 – Mailing list expansion issue
X.3.X CODES
* X.3.0 – Other or undefined mail system status
* X.3.1 – Mail system full
* X.3.2 – System not accepting network messages
* X.3.3 – System not capable of selected features
* X.3.4 – Message too big for system
* X.3.5 – System incorrectly configured
X.4.X CODES
* X.4.0 – Other or undefined network or routing status
* X.4.1 – No answer from host
* X.4.2 – Bad connection
* X.4.3 – Routing server failure
* X.4.4 – Unable to routev
* X.4.5 – Network congestion
* X.4.6 – Routing loop detected
* X.4.7 – Delivery time expired
X.5.X CODES
* X.5.0 – Other or undefined protocol status
* X.5.1 – Invalid command
* X.5.2 – Syntax error
* X.5.3 – Too many recipients
* X.5.4 – Invalid command arguments
* X.5.5 – Wrong protocol version
X.6.X CODES
* X.6.0 – Other or undefined media error
* X.6.1 – Media not supported
* X.6.2 – Conversion required and prohibited
* X.6.3 – Conversion required but not supported
* X.6.4 – Conversion with loss performed
* X.6.5 – Conversion failed
X.7.X CODES
* X.7.0 – Other or undefined security status
* X.7.1 – Delivery not authorized, message refused
* X.7.2 – Mailing list expansion prohibited
* X.7.3 – Security conversion required but not possible
* X.7.4 – Security features not supported
* X.7.5 – Cryptographic failure
* X.7.6 – Cryptographic algorithm not supported
* X.7.7 – Message integrity failure
XXX EMAIL ERROR CODES
200 Codes
* 211 – System status / system help reply
* 214 – Help message
* 220 – Domain service ready
* 221 – Service closing transmission channel
* 250 – Requested mail action okay and completed
* 251 – will forward to forwardpath
* 252 – Pending messages for node started. Cannot Verify user, will take message for this user and attempt delivery
* 253 – pending messages for node started
300 Codes
* 354 – Start mail input; end with . server is ready to accept the message
* 355 – Octet-offset is the transaction offset
400 Codes
* 421 – Domain service not available, closing transmission channel
* 432 – Domain service not available, closing transmission channel
* 450 – Requested mail action not taken: mailbox unavailable. request refused
* 451 – Requested action aborted: local error in processing Request is unable to be processed, try again
* 452 – Requested action not taken: insufficient system storage
* 453 – No mail
* 454 – TLS not available due to temporary reason. Encryption required for requested authentication mechanism.
* 458 – Unable to queue messages for node
* 459 – node not allowed: reason
500 Codes
* 500 – server could not recognize the command due to a syntax error
* 501 – Syntax error, no parameters allowed
* 502 – Command not implemented
* 503 – Bad sequence of commands
* 504 – Command parameter not implemented
* 510 – Check the recipient address
* 512 – Host unknown. Domain can not be found.
* 515 – Destination mailbox address invalid
* 517 – Problem with senders mail attribute, check properties
* 521 – Machine does not accept mail
* 522 – Recipient has exceeded mailbox limit
* 523 – Server or connector limit exceeded. Message too large
* 530 – Must issue a STARTTLS command first. Encryption required for requested authentication mechanism
* 531 – Mail system Full
* 533 – Remote server has insufficient disk space to hold email
* 534 – Authentication mechanism is too weak. Message too big
* 535 – Multiple servers using same IP
* 538 – Encryption required for requested authentication mechanism.
* 540 – No DNS Server for email address
* 541 – No answer from host
* 542 – Bad Connection
* 543 – Routing server failure. No available route
* 546 – Email looping
* 547 – Delivery time-out.
* 550 – Requested action not taken: mailbox unavailable.
* 551 – User not local; please try forwardpath
* 552 – Requested mail action aborted: exceeded storage allocation
* 553 – Requested action not taken: mailbox name not allowed
* 554 – Transaction failed
