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

Re: Weird throttling since midnight

Expand Messages
  • Wietse Venema
    ... # postconf berkeley_db_read_buffer_size=262144 # postfix reload (or start)
    Message 1 of 13 , May 26, 2013
    • 0 Attachment
      The Doctor:
      > > You may also play with berkeley_db_read_buffer_size. The Berkeley
      > > DB documentation promises that they accept buffer sizes of 20kB or
      > > more, and their default is 256kB. If someone has screwed up Berkeley
      > > DB, then perhaps it helps to specify berkeley_db_read_buffer_size
      > > of 262144 (262144 = 256*1024). Hopefully they still accept that.
      >
      > What tweak is needed in the main.cf to make such a change?
      >
      > >
      > > http://docs.oracle.com/cd/E17076_02/html/api_reference/C/dbset_cachesize.html

      # postconf berkeley_db_read_buffer_size=262144
      # postfix reload (or start)
    • Jerry
      On Sun, 26 May 2013 07:55:25 -0600 ... I have that version installed on a FreeBSD-8.3 system and it is working fine. OpenSSL 1.0.1e is also installed if that
      Message 2 of 13 , May 26, 2013
      • 0 Attachment
        On Sun, 26 May 2013 07:55:25 -0600
        The Doctor articulated:

        > On Sun, May 26, 2013 at 09:51:41AM -0400, Wietse Venema wrote:
        > > The Doctor:
        > > > On Sun, May 26, 2013 at 06:37:17AM -0600, The Doctor wrote:
        > > > > On Sun, May 26, 2013 at 08:04:47AM -0400, Wietse Venema wrote:
        > > > > > The Doctor:
        > > > > > > All right, I have been getting a lot of irregular throttling
        > > > > > > since Saturday midnight.
        > > > > > >
        > > > > > > May 25 08:05:53 doctor postfix/postscreen[29851]: fatal:
        > > > > > > set DB cache size 131072: Invalid argument
        > > > > >
        > > > > > Has your Berkeley DB library been updated? Perhaps you can
        > > > > > revert the update.
        > > > > >
        > > > > > Apparently, their set_cachesize() function now returns an
        > > > > > error when Postfix sets the cache size.
        > > > > >
        > > > > > This code has not changed since Postfix 2.0, more than 10
        > > > > > years ago:
        > > >
        > > > I take it back.
        > > >
        > > > Also the BDB is 5.3.21 which is the latest.

        I have that version installed on a FreeBSD-8.3 system and it is working
        fine. OpenSSL 1.0.1e is also installed if that makes any difference. It
        is working with Postfix (2.11-20130405). All are from the FreeBSD ports
        tree.

        --
        Jerry ✌
        postfix-user@...
        _____________________________________________________________________
        TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail
        TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html
      • The Doctor
        ... Still throttled. Will try DB 4.7.25 later today -- Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca God,Queen and
        Message 3 of 13 , May 26, 2013
        • 0 Attachment
          On Sun, May 26, 2013 at 09:58:31AM -0400, Wietse Venema wrote:
          > The Doctor:
          > > > You may also play with berkeley_db_read_buffer_size. The Berkeley
          > > > DB documentation promises that they accept buffer sizes of 20kB or
          > > > more, and their default is 256kB. If someone has screwed up Berkeley
          > > > DB, then perhaps it helps to specify berkeley_db_read_buffer_size
          > > > of 262144 (262144 = 256*1024). Hopefully they still accept that.
          > >
          > > What tweak is needed in the main.cf to make such a change?
          > >
          > > >
          > > > http://docs.oracle.com/cd/E17076_02/html/api_reference/C/dbset_cachesize.html
          >
          > # postconf berkeley_db_read_buffer_size=262144
          > # postfix reload (or start)

          Still throttled.

          Will try DB 4.7.25 later today
          --
          Member - Liberal International This is doctor@... Ici doctor@...
          God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
          http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
          The false churches will conform themselves to this world's demands, seeing as they do not fear and thus do not obey God. - anon
        • The Doctor
          ... Similar here except the OS is BSD/OS 4.3.1 ... -- Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca God,Queen and
          Message 4 of 13 , May 26, 2013
          • 0 Attachment
            On Sun, May 26, 2013 at 10:37:26AM -0400, Jerry wrote:
            > On Sun, 26 May 2013 07:55:25 -0600
            > The Doctor articulated:
            >
            > > On Sun, May 26, 2013 at 09:51:41AM -0400, Wietse Venema wrote:
            > > > The Doctor:
            > > > > On Sun, May 26, 2013 at 06:37:17AM -0600, The Doctor wrote:
            > > > > > On Sun, May 26, 2013 at 08:04:47AM -0400, Wietse Venema wrote:
            > > > > > > The Doctor:
            > > > > > > > All right, I have been getting a lot of irregular throttling
            > > > > > > > since Saturday midnight.
            > > > > > > >
            > > > > > > > May 25 08:05:53 doctor postfix/postscreen[29851]: fatal:
            > > > > > > > set DB cache size 131072: Invalid argument
            > > > > > >
            > > > > > > Has your Berkeley DB library been updated? Perhaps you can
            > > > > > > revert the update.
            > > > > > >
            > > > > > > Apparently, their set_cachesize() function now returns an
            > > > > > > error when Postfix sets the cache size.
            > > > > > >
            > > > > > > This code has not changed since Postfix 2.0, more than 10
            > > > > > > years ago:
            > > > >
            > > > > I take it back.
            > > > >
            > > > > Also the BDB is 5.3.21 which is the latest.
            >
            > I have that version installed on a FreeBSD-8.3 system and it is working
            > fine. OpenSSL 1.0.1e is also installed if that makes any difference. It
            > is working with Postfix (2.11-20130405). All are from the FreeBSD ports
            > tree.
            >

            Similar here except the OS is BSD/OS 4.3.1

            > --
            > Jerry ???
            > postfix-user@...
            > _____________________________________________________________________
            > TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail
            > TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html
            >
            >

            --
            Member - Liberal International This is doctor@... Ici doctor@...
            God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
            http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
            The false churches will conform themselves to this world's demands, seeing as they do not fear and thus do not obey God. - anon
          • Bill Cole
            ... Do you have a Postfix queue named ? Why does your Postfix config think that you do, and that it needs hashing? I m not 100% sure that s your problem,
            Message 5 of 13 , May 26, 2013
            • 0 Attachment
              On 25 May 2013, at 21:24, The Doctor wrote:

              > hash_queue_names = " " defer deferred

              Do you have a Postfix queue named " "? Why does your Postfix config
              think that you do, and that it needs hashing?

              I'm not 100% sure that's your problem, but it seems worth fixing *AND*
              figuring out how such an oddity made it into your config. If correcting
              that is not a fix, you should recreate (i.e.postmap) all of the hash and
              btree maps mentioned in your postconf output, after making sure that
              postmap and all the other parts of Postfix are linked with the same
              version of BDB

              Also:

              On 26 May 2013, at 9:44, The Doctor wrote:

              > postsuper: warning: bogus file name: defer/2/gmon.out
              > postsuper: warning: bogus file name: defer/gmon.out
              > postfix/postfix-script: warning: damaged message: corrupt/gmon.out
              > postfix/postfix-script: starting the Postfix mail system
              > May 26 07:23:51 doctor doctor[31]: postfix/postsuper[14232]: warning:
              > bogus file name: defer/2/gmon.out
              > May 26 07:23:51 doctor doctor[31]: postfix/postsuper[14232]: warning:
              > bogus file name: defer/gmon.out
              > May 26 07:23:51 doctor postfix/postfix-script[14272]: warning: damaged
              > message: corrupt/gmon.out

              Whatever on that machine created random "gmon.out" files in queue
              directories should be removed.
            Your message has been successfully submitted and would be delivered to recipients shortly.