BIG Problem Postfix issue

Discussion in 'Installation/Configuration' started by admins, Oct 4, 2009.

  1. admins

    admins Member HowtoForge Supporter

    Hi all

    I've the following in the log:
    Code:
    Oct 4 17:33:22 websrv1 postfix/smtpd[24341]: warning: problem talking to service rewrite: Success
    Oct 4 17:33:22 websrv1 postfix/smtpd[24346]: warning: problem talking to service rewrite: Success
    Oct 4 17:33:22 websrv1 postfix/master[21531]: warning: process /usr/lib/postfix/trivial-rewrite pid 25847 exit status 1
    Oct 4 17:33:22 websrv1 postfix/master[21531]: warning: process /usr/lib/postfix/trivial-rewrite pid 25848 exit status 1
    Oct 4 17:34:17 websrv1 amavis[21591]: (21591-01) (!)rw_loop: leaving rw loop, no progress
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26416]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26416]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26417]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26417]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26418]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26418]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26419]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26419]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26420]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26420]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26421]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26421]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26422]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26422]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26423]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26423]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26424]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26424]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26425]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26425]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26426]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26426]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26427]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26427]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
    Oct 4 17:34:22 websrv1 postfix/trivial-rewrite[26428]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
    Where could I fix this problem?

    thanks
    admins
     
  2. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Please cjeck if you are able to login to the mysql database with the mysql login details that can be found in the /etc/postfix/mysql* files.
     
  3. Ovidiu

    Ovidiu Active Member

    got the same problem but just from time to time so the credentials are fine. could be mysql is overloaded?
    already upped the max connections, any other advice?
     
  4. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Please make sure that you set also the max user connections to a higher value and not just the max connactions as all services connect with the same username.
     
  5. Ovidiu

    Ovidiu Active Member

    hmmmm I upped the max connections. should be good now.
    the max_user_connections is on default=0 meaning unlimited...

    well, I guess there is not much more I can do...
     
  6. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Anything in the mysql or mail error logs?
     
  7. Ovidiu

    Ovidiu Active Member

    todays mysql logs are empty.

    mail.err shows this:

    Code:
    h1550830:/var/log# tail -f /var/log/mail.err
    Nov 11 15:44:50 h1550830 amavis[24189]: (24189-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154450-24189: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:50 h1550830 amavis[24191]: (24191-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154450-24191: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:51 h1550830 amavis[24192]: (24192-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154451-24192: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:52 h1550830 amavis[24193]: (24193-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154452-24193: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:52 h1550830 amavis[24196]: (24196-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154452-24196: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:53 h1550830 amavis[24198]: (24198-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154453-24198: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:55 h1550830 amavis[24199]: (24199-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154455-24199: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:56 h1550830 amavis[24200]: (24200-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154456-24200: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:56 h1550830 amavis[24202]: (24202-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154456-24202: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    Nov 11 15:44:56 h1550830 amavis[24203]: (24203-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091111T154456-24203: Too many links at /usr/sbin/amavisd-new line 5081, <GEN33> line 4.
    
    
    otherwise nothing remotely interesting...

    if I chekc the mailqueue I see some messages with this error:

    Code:
    delivery temporarily suspended: lost connection with 127.0.0.1[127.0.0.1] while sending RCPT TO
    Code:
    delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
     
  8. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

  9. Ovidiu

    Ovidiu Active Member

  10. Ovidiu

    Ovidiu Active Member

    I have used this command to count hte number of files:

    it was 110.000 then I used this command to delete everything older than 3 days:

    because 3 days ago I moved a client with a fairly huge newsletter with lots of dead recipients. We are currently in the process of cleaning it up via the bounces.

    Anything else I can do in the meantime?
    Oh, btw. the tmp fodler seems to be fully cluttered with te,porary spamassassin files...
     
    Last edited: Nov 12, 2009
  11. Ovidiu

    Ovidiu Active Member

    it seems the temporary fodler was needed only for the FuzzyOCR spamassassin extension. disabling that seems to have fixed the amavis errors...
     
  12. Ovidiu

    Ovidiu Active Member

    not really :-(

    getting these now:

    Code:
    Nov 13 09:56:18 h1550830 amavis[21700]: (21700-01) (!)Requesting process rundown after fatal error
    Nov 13 09:56:19 h1550830 amavis[21715]: (21715-01) (!!)TROUBLE in process_request: Can't create directory /var/lib/amavis/tmp/amavis-20091113T095619-21715: Too many links at /usr/sbin/amavisd-new line 5081, line 4.
     

Share This Page