Note: There are a few cases of duplicates in user autocompletion which are being worked on.
Last Comment Bug 1077137 - twistd logs not being sent because "Message size exceeds fixed limit"
: twistd logs not being sent because "Message size exceeds fixed limit"
Product: Release Engineering
Classification: Other
Component: Buildduty (show other bugs)
: unspecified
: All All
P2 normal (vote)
: ---
Assigned To: Nick Thomas [:nthomas]
: Justin Wood (:Callek)
: Chris AtLee [:catlee]
Depends on:
  Show dependency treegraph
Reported: 2014-10-02 14:54 PDT by Ben Hearsum (:bhearsum)
Modified: 2014-10-09 16:43 PDT (History)
2 users (show)
See Also:
Crash Signature:
Machine State: ---
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Ben Hearsum (:bhearsum) 2014-10-02 14:54:45 PDT
Traceback (most recent call last):
  File "/builds/buildbot/build1/tools/buildfarm/maintenance/", line 247, in <module>
    hostname, exceptions,
  File "/builds/buildbot/build1/tools/buildfarm/maintenance/", line 117, in send_msg
    s.sendmail(fromaddr, [addr], m.as_string())
  File "/tools/python27/lib/python2.7/", line 722, in sendmail
    raise SMTPSenderRefused(code, resp, from_addr)
smtplib.SMTPSenderRefused: (552, '5.3.4 Message size exceeds fixed limit', '')

There's probably two issues to deal with here:
1) Why are the messages so big?
2) Split the mail if the messages are too big.
Comment 1 User image Nick Thomas [:nthomas] 2014-10-02 18:53:44 PDT
The db reboot yesterday gave us a metric crapton of tracebacks in the logs, bug 1076623 to handle that a little more gracefully. To fix this up we need to go around and touch the marker file, which tells the script which timestamp to start at.
Comment 2 User image Nick Thomas [:nthomas] 2014-10-02 18:55:47 PDT
Actually, it looks like the files (eg bm11:~cltbld/.bm111-tests1-windows-last-time.txt) have an epoch timestamp instead.
Comment 3 User image Nick Thomas [:nthomas] 2014-10-02 19:07:59 PDT
Shoved 1412298000 (Thu Oct 2 18:00:00 2014 Pacific) into the stale files just prior to the 7pm cron job.
Comment 4 User image Nick Thomas [:nthomas] 2014-10-09 16:43:03 PDT
And again today for bm81, 82, 84, 85, 86, 105. A gap as big as 7am to 4pm Pacific.

Note You need to log in before you can comment on or make changes to this bug.