Loading ...
Sorry, an error occurred while loading the content.
 

Re: New document: STRESS_README

Expand Messages
  • Andreas Grimm
    Hello (sorry, i resend it to the list), these are the last signs of live from anvil: Nov 1 10:13:03 mx-01 postfix/anvil[14283]: statistics: max connection
    Message 1 of 38 , Nov 1 4:29 AM
      Hello (sorry, i resend it to the list),

      these are the last signs of live from anvil:
      Nov  1 10:13:03 mx-01 postfix/anvil[14283]: statistics: max connection rate 200/60s for (smtp:80.253.80.28) at Nov  1 10:04:11
      Nov  1 10:13:03 mx-01 postfix/anvil[14283]: statistics: max connection count 37 for (smtp:80.253.80.28) at Nov  1 10:04:17
      Nov  1 10:13:03 mx-01 postfix/anvil[14283]: statistics: max cache size 2003 at Nov  1 10:07:43
      Nov  1 10:14:52 mx-01 postfix/anvil[14283]: statistics: max connection rate 12/60s for (smtp:66.56.131.32) at Nov  1 10:14:25
      Nov  1 10:14:56 mx-01 postfix/anvil[14283]: statistics: max connection count 13 for (smtp:220.224.9.191) at Nov  1 10:13:49
      Nov  1 10:14:57 mx-01 postfix/anvil[14283]: statistics: max cache size 1974 at Nov  1 10:14:15

      Then:
      Nov  1 10:14:59 mx-01 postfix/smtpd[4192]: warning: connect to private/anvil: Resource temporarily unavailable
      Nov  1 10:14:59 mx-01 postfix/smtpd[3611]: warning: connect to private/anvil: Resource temporarily unavailable

      Prior to my kernel modification i got "Too many open files". Now the error-log contains nothing about that incedent.

      ----- Original Message ----
      From: Wietse Venema <wietse@...>
      To: Andreas Grimm <grimm.andreas@...>
      Cc: postfix-users@...
      Sent: Thursday, November 1, 2007 12:06:50 PM
      Subject: Re: New document: STRESS_README

      Andreas Grimm:
      write(5, "\3137\0\0\34\0\0\0\1\0\0\0", 12) = -1 ECONNRESET (Connection reset by peer)
      time(NULL)                              = 1193908492
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      send(7, "<22>Nov  1 10:14:52 postfthoseix/anvi"..., 123, MSG_NOSIGNAL) = 123
      time(NULL)                              = 1193908496
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      send(7, "<22>Nov  1 10:14:56 postfix/anvi"..., 121, MSG_NOSIGNAL) = 121
      time(NULL)                              = 1193908497
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
      send(7, "<22>Nov  1 10:14:57 postfix/anvi"..., 92, MSG_NOSIGNAL) = 92
      exit_group(0)                          = ?

      What error message is postfix/anvil logging at Nov  1 10:14:52,
      Nov  1 10:14:56, and Nov  1 10:14:57?

          Wietse


      __________________________________________________
      Do You Yahoo!?
      Tired of spam? Yahoo! Mail has the best spam protection around
      http://mail.yahoo.com

      __________________________________________________
      Do You Yahoo!?
      Tired of spam? Yahoo! Mail has the best spam protection around
      http://mail..yahoo.com
    • Victor Duchovni
      ... Why not just a single mail log file? How does mail.info differ from mail ? I am guessing you are writing each info (majority) log message to disk
      Message 38 of 38 , Nov 1 10:27 AM
        On Thu, Nov 01, 2007 at 10:10:30AM -0700, Andreas Grimm wrote:

        > Hello,
        >
        > no, destinations are local files:
        > destination mailinfo { file("/var/log/mail.info"); };
        > destination mailwarn { file("/var/log/mail.warn"); };
        > destination mailerr { file("/var/log/mail.err" fsync(yes)); };
        > destination mail { file("/var/log/mail"); };

        Why not just a single mail log file? How does "mail.info" differ from
        "mail"? I am guessing you are writing each "info" (majority) log message
        to disk twice. This is wasteful.

        > Messages in the fifo should be dropped, thats right. Maybe the release
        > comes from the simple restart of syslog-ng (cleaning up garbage?). It's
        > confusing.

        Either the log socket was actually unix-stream, or the sync flags were
        wrong, or syslog-ng was unwell after running a long time, but that should
        not happen.

        Perhaps there were other settings in syslog-ng.conf that had not yet
        taken effect? Also, you will lose some messages when you rotate
        log files by renaming, and send SIGHUP to the log server. It rebinds
        the /dev/log unix-domain socket, and messages are lost (briefly)
        while the socket is rebuilt.

        I avoid this, by not using fixed file names, and not sending SIGHUP.

        destination mail {
        file("/d/d1/log/raw/mail/$YEAR/$MONTH/$DAY/$HOUR"
        template("$ISODATE $HOST $MSG\n") template_escape(no)
        owner("root") group("log") perm(0640)
        dir_owner("root") dir_group("log") dir_perm(02750)
        create_dirs(yes));
        };

        These log files don't require external rotation, it is enough to just
        delete sufficiently old ones periodically. We compress them first
        (writing compressed data to a parallel directory tree) and move
        sync the compressed files to a log aggregation server.

        --
        Viktor.

        Disclaimer: off-list followups get on-list replies or get ignored.
        Please do not ignore the "Reply-To" header.

        To unsubscribe from the postfix-users list, visit
        http://www.postfix.org/lists.html or click the link below:
        <mailto:majordomo@...?body=unsubscribe%20postfix-users>

        If my response solves your problem, the best way to thank me is to not
        send an "it worked, thanks" follow-up. If you must respond, please put
        "It worked, thanks" in the "Subject" so I can delete these quickly.
      Your message has been successfully submitted and would be delivered to recipients shortly.