amavis.service failed with start-limit-hit

Discussion in 'Installation/Configuration' started by lonerunner, May 28, 2021.

  1. lonerunner

    lonerunner Member

    I am having an error all of a sudden with amavis.service starting and thus the emails are not sending from the server.
    This is a new server i setup about 2 weeks ago and everything seems to be working fine until yesterday when i noticed emails are piling up in the queue.
    When i took a look on the issue i get `connection refused to 127.0.0.1` in mail log file and i found out it's because amavis service failed to run.
    Upon checking on the service status i get the error like this:

    Code:
    amavis.service - LSB: Starts amavisd-new mailfilter
       Loaded: loaded (/etc/init.d/amavis; generated)
       Active: failed (Result: start-limit-hit) since Thu 2021-05-27 22:42:13 CEST; 14h ago
         Docs: man:systemd-sysv-generator(8)
      Process: 8972 ExecStart=/etc/init.d/amavis start (code=exited, status=0/SUCCESS)
      Process: 8997 ExecStop=/etc/init.d/amavis stop (code=exited, status=0/SUCCESS)
    
    May 27 22:42:14 ns3.domain.info systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter.
    May 27 22:42:14 ns3.domain.info systemd[1]: amavis.service: Start request repeated too quickly.
    May 27 22:42:14 ns3.domain.info systemd[1]: amavis.service: Failed with result 'start-limit-hit'.
    May 27 22:42:14 ns3.domain.info systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter.
    May 27 22:42:14 ns3.domain.info systemd[1]: amavis.service: Start request repeated too quickly.
    May 27 22:42:14 ns3.domain.info systemd[1]: amavis.service: Failed with result 'start-limit-hit'.
    May 27 22:42:14 ns3.domain.info systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter.
    May 27 22:42:14 ns3.domain.info systemd[1]: amavis.service: Start request repeated too quickly.
    May 27 22:42:14 ns3.domain.info systemd[1]: amavis.service: Failed with result 'start-limit-hit'.
    May 27 22:42:14 ns3.domain.info systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter.
    
    I resolve the issues by restarting amavis service but i can't figure out why this has happened.
     
  2. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Log messages from amavis will be in mail.log, you will probably find the reason there.
     
    Last edited: May 28, 2021
  3. lonerunner

    lonerunner Member

    In a whole log file, the only thing i found related to amavis or mentioning amavis is this


    Code:
    May 27 18:26:02 ns3 amavis[23621]: starting. /usr/sbin/amavisd-new at ns3.domain.info amavisd-new-2.11.0 (20160426), Unicode aware, LC_ALL="C", LANG="en_US.UTF-8"
    May 27 18:26:02 ns3 amavis[23628]: Net::Server: Group Not Defined.  Defaulting to EGID '122 122'
    May 27 18:26:02 ns3 amavis[23628]: Net::Server: User Not Defined.  Defaulting to EUID '114'
    May 27 18:26:02 ns3 amavis[23628]: No ext program for   .lz4, tried: lz4c -d
    May 27 18:26:02 ns3 amavis[23628]: No ext program for   .rpm, tried: rpm2cpio.pl, rpm2cpio
    May 27 18:26:02 ns3 amavis[23628]: No ext program for   .rar, tried: unrar-free
    May 27 18:26:02 ns3 amavis[23628]: No ext program for   .zoo, tried: zoo
    May 27 18:26:02 ns3 amavis[23628]: No ext program for   .doc, tried: ripole
    May 27 18:26:02 ns3 amavis[23628]: No decoder for       .F   
    May 27 18:26:02 ns3 amavis[23628]: No decoder for       .doc
    May 27 18:26:02 ns3 amavis[23628]: No decoder for       .lz4
    May 27 18:26:02 ns3 amavis[23628]: No decoder for       .zoo
    May 27 18:26:02 ns3 amavis[23628]: Using primary internal av scanner code for ClamAV-clamd
    May 27 18:26:02 ns3 amavis[23628]: Found secondary av scanner ClamAV-clamscan at /usr/bin/clamscan
    
     
  4. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    Those are the logs when it started, maybe previous logs are in the rotated log file (mail.log.1)? You might check your amavis logging level as well, I see log messages for every message amavis processes.
     
  5. lonerunner

    lonerunner Member

    I checked the log files from 3 days ago, from before amavis failed and i don't see anything else in log files so i checked amavis/conf.d/50-user file and log level was set to 0, I changed it now to 5 so this should log all debugging as documentation states. Will see if I set it correctly to log more details.
     

Share This Page