homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ngie
Recipients lukas.lalinsky, ngie, vinay.sajip
Date 2014年06月07日.03:34:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402112099.01.0.516461004984.issue11907@psf.upfronthosting.co.za>
In-reply-to
Content
The code doesn't appear to be conforming to RFC-3164 or RFC-5424:
(From RFC-3164):
4.1 syslog Message Parts
 The full format of a syslog message seen on the wire has three
 discernable parts. The first part is called the PRI, the second part
 is the HEADER, and the third part is the MSG. The total length of
 the packet MUST be 1024 bytes or less. There is no minimum length of
 the syslog message although sending a syslog packet with no contents
 is worthless and SHOULD NOT be transmitted.
(From RFC-5424)
 The reason syslog transport receivers need only support receiving up
 to and including 480 octets has, among other things, to do with
 difficult delivery problems in a broken network. Syslog messages may
 use a UDP transport mapping with this 480 octet restriction to avoid
 session overhead and message fragmentation. In a network with
 problems, the likelihood of getting one single-packet message
 delivered successfully is higher than getting two message fragments
 delivered successfully. Therefore, using a larger size may prevent
 the operator from getting some critical information about the
 problem, whereas using small messages might get that information to
 the operator. It is recommended that messages intended for
 troubleshooting purposes should not be larger than 480 octets. To
 further strengthen this point, it has also been observed that some
 UDP implementations generally do not support message sizes of more
 than 480 octets. This behavior is very rare and may no longer be an
 issue.
...
 It must be noted that the IPv6 MTU is about 2.5 times 480. An
 implementation targeted towards an IPv6-only environment might thus
 assume this as a larger minimum size.
With MTUs being what they are by default with ethernet, using an MTU <1500 with UDP when jumbo frames aren't available seems like a foolhardy thing to do.
I believe part of the problem is that the socket send buffer size is not being set in the SysLogHandler via socket.setsockopt and it's trying to jam as much information as it can down the pipe and failing, but I need to do more digging...
History
Date User Action Args
2014年06月07日 03:34:59ngiesetrecipients: + ngie, vinay.sajip, lukas.lalinsky
2014年06月07日 03:34:59ngiesetmessageid: <1402112099.01.0.516461004984.issue11907@psf.upfronthosting.co.za>
2014年06月07日 03:34:58ngielinkissue11907 messages
2014年06月07日 03:34:57ngiecreate

AltStyle によって変換されたページ (->オリジナル) /