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

Re: Weird throttling since midnight

Expand Messages
  • Wietse Venema
    ... Has your Berkeley DB library been updated? Perhaps you can revert the update. Apparently, their set_cachesize() function now returns an error when Postfix
    Message 1 of 13 , May 26, 2013
    • 0 Attachment
      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:

      if ((errno = db->set_cachesize(db, 0, dict_db_cache_size, 0)) != 0)
      msg_fatal("set DB cache size %d: %m", dict_db_cache_size);

      131072 (128 kbyte) is the Postfix default read buffer size:

      berkeley_db_read_buffer_size = 131072

      There is a similar parameter for writing, used in postmap.

      None of this has changed since Postfix 2.0.

      Wietse
    • The Doctor
      ... I have not updated the BDB in some time 5.3.25 for over a year. I suspect this to be the openssl . I was using openssl 1.0.2-dev . Reverting to openssl
      Message 2 of 13 , May 26, 2013
      • 0 Attachment
        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:
        >
        > if ((errno = db->set_cachesize(db, 0, dict_db_cache_size, 0)) != 0)
        > msg_fatal("set DB cache size %d: %m", dict_db_cache_size);
        >
        > 131072 (128 kbyte) is the Postfix default read buffer size:
        >
        > berkeley_db_read_buffer_size = 131072
        >
        > There is a similar parameter for writing, used in postmap.


        I have not updated the BDB in some time 5.3.25 for over a year.

        I suspect this to be the openssl .

        I was using openssl 1.0.2-dev . Reverting to openssl 1.0.1 branch.

        >
        > None of this has changed since Postfix 2.0.
        >
        > Wietse

        --
        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
        ... I take it back. Also the BDB is 5.3.21 which is the latest. Here are the logs from the latest backfire postfix start && tail -f /var/log/maillog postsuper:
        Message 3 of 13 , May 26, 2013
        • 0 Attachment
          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:
          > >
          > > if ((errno = db->set_cachesize(db, 0, dict_db_cache_size, 0)) != 0)
          > > msg_fatal("set DB cache size %d: %m", dict_db_cache_size);
          > >
          > > 131072 (128 kbyte) is the Postfix default read buffer size:
          > >
          > > berkeley_db_read_buffer_size = 131072
          > >
          > > There is a similar parameter for writing, used in postmap.
          >
          >
          > I have not updated the BDB in some time 5.3.25 for over a year.
          >
          > I suspect this to be the openssl .
          >
          > I was using openssl 1.0.2-dev . Reverting to openssl 1.0.1 branch.

          I take it back.

          Also the BDB is 5.3.21 which is the latest.

          Here are the logs from the latest backfire

          postfix start && tail -f /var/log/maillog
          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
          May 26 07:23:51 doctor postfix/postfix-script[14274]: starting the Postfix mail system
          May 26 07:23:52 doctor postfix/master[14276]: daemon started -- version 2.10.0, configuration /etc/postfix
          May 26 07:23:52 doctor postfix/qmgr[14278]: name_mask: ipv4
          May 26 07:23:52 doctor postfix/qmgr[14278]: inet_addr_local: configured 363 IPv4 addresses
          May 26 07:23:52 doctor postfix/qmgr[14278]: process generation: 2 (2)
          May 26 07:23:52 doctor postfix/qmgr[14278]: running: PATH=/bin:/usr/bin:/usr/contrib/bin:/usr/X11R6/bin? (ktrace -p 14278 2>&1 | logger -p mail.info) & sleep 5
          May 26 07:23:52 doctor postfix/qmgr[14278]: match_string: fast_flush_domains ~? debug_peer_list
          May 26 07:23:52 doctor postfix/qmgr[14278]: match_string: fast_flush_domains ~? fast_flush_domains
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: start move queue active -> incoming
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: end move queue active -> incoming
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: qmgr_scan_start: start incoming queue scan
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: qmgr_scan_start: start deferred queue scan
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: done incoming queue scan
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: done deferred queue scan
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: mail_flow_put: 100 100
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: trigger_server_accept_fifo: trigger arrived
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: master_notify: status 0
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: request: 87 (W)
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: qmgr_scan_start: start incoming queue scan
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: master_notify: status 1
          May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: done incoming queue scan
          May 26 07:23:52 doctor postfix/cleanup[14280]: name_mask: ipv4
          May 26 07:23:52 doctor postfix/cleanup[14280]: inet_addr_local: configured 363 IPv4 addresses
          May 26 07:23:52 doctor postfix/cleanup[14280]: process generation: 3 (3)
          May 26 07:23:52 doctor postfix/cleanup[14280]: running: PATH=/bin:/usr/bin:/usr/contrib/bin:/usr/X11R6/bin? (ktrace -p 14280 2>&1 | logger -p mail.info) & sleep 5
          May 26 07:23:52 doctor postfix/cleanup[14280]: Compiled against Berkeley DB: 5.3.21?
          May 26 07:23:52 doctor postfix/cleanup[14280]: Run-time linked against Berkeley DB: 5.3.21?
          May 26 07:23:52 doctor postfix/cleanup[14280]: fatal: set DB cache size 131072: Invalid argument
          May 26 07:23:54 doctor postfix/master[14276]: warning: process /usr/libexec/postfix/cleanup pid 14280 exit status 1
          May 26 07:23:54 doctor postfix/master[14276]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
          May 26 07:23:55 doctor postfix/postscreen[14352]: inet_addr_local: configured 363 IPv4 addresses
          May 26 07:23:55 doctor postfix/postscreen[14352]: process generation: 4 (4)
          May 26 07:23:55 doctor postfix/postscreen[14352]: running: PATH=/bin:/usr/bin:/usr/contrib/bin:/usr/X11R6/bin? (ktrace -p 14352 2>&1 | logger -p mail.info) & sleep 5
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? debug_peer_list
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? fast_flush_domains
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? mynetworks
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? permit_mx_backup_networks
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? qmqpd_authorized_clients
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? relay_domains
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? smtpd_access_maps
          May 26 07:23:55 doctor postfix/postscreen[14352]: match_list_match: postscreen_access_list: no match
          May 26 07:23:55 doctor postfix/postscreen[14352]: set_eugid: euid 31 egid 31
          May 26 07:23:55 doctor postfix/postscreen[14352]: Compiled against Berkeley DB: 5.3.21?
          May 26 07:23:55 doctor postfix/postscreen[14352]: Run-time linked against Berkeley DB: 5.3.21?
          May 26 07:23:55 doctor postfix/postscreen[14352]: fatal: set DB cache size 131072: Invalid argument
          May 26 07:23:57 doctor postfix/master[14276]: warning: process /usr/libexec/postfix/postscreen pid 14352 exit status 1
          May 26 07:23:57 doctor postfix/master[14276]: warning: /usr/libexec/postfix/postscreen: bad command startup -- throttling

          >
          > >
          > > None of this has changed since Postfix 2.0.
          > >
          > > Wietse
          >
          > --
          > 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

          --
          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
          ... FYI /* * __db_set_cachesize -- * Set underlying cache size. */ static int __db_set_cachesize(dbp, cache_gbytes, cache_bytes, ncache) DB *dbp;
          Message 4 of 13 , May 26, 2013
          • 0 Attachment
            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:
            > >
            > > if ((errno = db->set_cachesize(db, 0, dict_db_cache_size, 0)) != 0)
            > > msg_fatal("set DB cache size %d: %m", dict_db_cache_size);
            > >
            > > 131072 (128 kbyte) is the Postfix default read buffer size:
            > >
            > > berkeley_db_read_buffer_size = 131072
            > >
            > > There is a similar parameter for writing, used in postmap.
            >
            >
            > I have not updated the BDB in some time 5.3.25 for over a year.
            >
            > I suspect this to be the openssl .
            >
            > I was using openssl 1.0.2-dev . Reverting to openssl 1.0.1 branch.
            >
            > >
            > > None of this has changed since Postfix 2.0.
            > >
            > > Wietse


            FYI

            /*
            * __db_set_cachesize --
            * Set underlying cache size.
            */
            static int
            __db_set_cachesize(dbp, cache_gbytes, cache_bytes, ncache)
            DB *dbp;
            u_int32_t cache_gbytes, cache_bytes;
            int ncache;
            {
            DB_ILLEGAL_IN_ENV(dbp, "DB->set_cachesize");
            DB_ILLEGAL_AFTER_OPEN(dbp, "DB->set_cachesize");

            return (__memp_set_cachesize(
            dbp->dbenv, cache_gbytes, cache_bytes, ncache));
            }


            I am trying to find any more information that might be of help to you.

            >
            > --
            > 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

            --
            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
            ... Wietse would you like a copy of DB 5.3.21? ... -- Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca God,Queen and
            Message 5 of 13 , May 26, 2013
            • 0 Attachment
              On Sun, May 26, 2013 at 07:29:03AM -0600, The Doctor wrote:
              > 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:
              > > >
              > > > if ((errno = db->set_cachesize(db, 0, dict_db_cache_size, 0)) != 0)
              > > > msg_fatal("set DB cache size %d: %m", dict_db_cache_size);
              > > >
              > > > 131072 (128 kbyte) is the Postfix default read buffer size:
              > > >
              > > > berkeley_db_read_buffer_size = 131072
              > > >
              > > > There is a similar parameter for writing, used in postmap.
              > >
              > >
              > > I have not updated the BDB in some time 5.3.25 for over a year.
              > >
              > > I suspect this to be the openssl .
              > >
              > > I was using openssl 1.0.2-dev . Reverting to openssl 1.0.1 branch.
              >
              > I take it back.
              >
              > Also the BDB is 5.3.21 which is the latest.
              >
              > Here are the logs from the latest backfire
              >
              > postfix start && tail -f /var/log/maillog
              > 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
              > May 26 07:23:51 doctor postfix/postfix-script[14274]: starting the Postfix mail system
              > May 26 07:23:52 doctor postfix/master[14276]: daemon started -- version 2.10.0, configuration /etc/postfix
              > May 26 07:23:52 doctor postfix/qmgr[14278]: name_mask: ipv4
              > May 26 07:23:52 doctor postfix/qmgr[14278]: inet_addr_local: configured 363 IPv4 addresses
              > May 26 07:23:52 doctor postfix/qmgr[14278]: process generation: 2 (2)
              > May 26 07:23:52 doctor postfix/qmgr[14278]: running: PATH=/bin:/usr/bin:/usr/contrib/bin:/usr/X11R6/bin? (ktrace -p 14278 2>&1 | logger -p mail.info) & sleep 5
              > May 26 07:23:52 doctor postfix/qmgr[14278]: match_string: fast_flush_domains ~? debug_peer_list
              > May 26 07:23:52 doctor postfix/qmgr[14278]: match_string: fast_flush_domains ~? fast_flush_domains
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: start move queue active -> incoming
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: end move queue active -> incoming
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: qmgr_scan_start: start incoming queue scan
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: qmgr_scan_start: start deferred queue scan
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: done incoming queue scan
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: done deferred queue scan
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: mail_flow_put: 100 100
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: trigger_server_accept_fifo: trigger arrived
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: master_notify: status 0
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: request: 87 (W)
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: qmgr_scan_start: start incoming queue scan
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: master_notify: status 1
              > May 26 07:23:52 doctor doctor[31]: postfix/qmgr[14278]: done incoming queue scan
              > May 26 07:23:52 doctor postfix/cleanup[14280]: name_mask: ipv4
              > May 26 07:23:52 doctor postfix/cleanup[14280]: inet_addr_local: configured 363 IPv4 addresses
              > May 26 07:23:52 doctor postfix/cleanup[14280]: process generation: 3 (3)
              > May 26 07:23:52 doctor postfix/cleanup[14280]: running: PATH=/bin:/usr/bin:/usr/contrib/bin:/usr/X11R6/bin? (ktrace -p 14280 2>&1 | logger -p mail.info) & sleep 5
              > May 26 07:23:52 doctor postfix/cleanup[14280]: Compiled against Berkeley DB: 5.3.21?
              > May 26 07:23:52 doctor postfix/cleanup[14280]: Run-time linked against Berkeley DB: 5.3.21?
              > May 26 07:23:52 doctor postfix/cleanup[14280]: fatal: set DB cache size 131072: Invalid argument
              > May 26 07:23:54 doctor postfix/master[14276]: warning: process /usr/libexec/postfix/cleanup pid 14280 exit status 1
              > May 26 07:23:54 doctor postfix/master[14276]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
              > May 26 07:23:55 doctor postfix/postscreen[14352]: inet_addr_local: configured 363 IPv4 addresses
              > May 26 07:23:55 doctor postfix/postscreen[14352]: process generation: 4 (4)
              > May 26 07:23:55 doctor postfix/postscreen[14352]: running: PATH=/bin:/usr/bin:/usr/contrib/bin:/usr/X11R6/bin? (ktrace -p 14352 2>&1 | logger -p mail.info) & sleep 5
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? debug_peer_list
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? fast_flush_domains
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? mynetworks
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? permit_mx_backup_networks
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? qmqpd_authorized_clients
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? relay_domains
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_string: postscreen_access_list ~? smtpd_access_maps
              > May 26 07:23:55 doctor postfix/postscreen[14352]: match_list_match: postscreen_access_list: no match
              > May 26 07:23:55 doctor postfix/postscreen[14352]: set_eugid: euid 31 egid 31
              > May 26 07:23:55 doctor postfix/postscreen[14352]: Compiled against Berkeley DB: 5.3.21?
              > May 26 07:23:55 doctor postfix/postscreen[14352]: Run-time linked against Berkeley DB: 5.3.21?
              > May 26 07:23:55 doctor postfix/postscreen[14352]: fatal: set DB cache size 131072: Invalid argument
              > May 26 07:23:57 doctor postfix/master[14276]: warning: process /usr/libexec/postfix/postscreen pid 14352 exit status 1
              > May 26 07:23:57 doctor postfix/master[14276]: warning: /usr/libexec/postfix/postscreen: bad command startup -- throttling
              >

              Wietse would you like a copy of DB 5.3.21?

              > >
              > > >
              > > > None of this has changed since Postfix 2.0.
              > > >
              > > > Wietse
              > >
              > > --
              > > 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
              >
              > --
              > 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

              --
              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
            • Wietse Venema
              ... That is the same Berkeley DB error. You can stop posting these now. You may make more progress if you can back out the improved Berkeley DB library. You
              Message 6 of 13 , May 26, 2013
              • 0 Attachment
                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.
                >
                > Here are the logs from the latest backfire

                That is the same Berkeley DB error. You can stop posting these now.
                You may make more progress if you can back out the "improved"
                Berkeley DB library.

                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.

                http://docs.oracle.com/cd/E17076_02/html/api_reference/C/dbset_cachesize.html

                Wietse
              • The Doctor
                ... Correct about the word improved . I might have a 4.7 or 4.8 lying around let me check. In the mean time ... What tweak is needed in the main.cf to make
                Message 7 of 13 , May 26, 2013
                • 0 Attachment
                  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.
                  > >
                  > > Here are the logs from the latest backfire
                  >
                  > That is the same Berkeley DB error. You can stop posting these now.
                  > You may make more progress if you can back out the "improved"
                  > Berkeley DB library.

                  Correct about the word "improved". I might have a 4.7 or 4.8
                  lying around let me check.

                  In the mean time

                  >
                  > 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
                  >
                  > Wietse

                  --
                  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
                • Wietse Venema
                  ... # postconf berkeley_db_read_buffer_size=262144 # postfix reload (or start)
                  Message 8 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 9 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 10 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 11 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 12 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.