amavisd does not start email stalled

Discussion in 'Installation/Configuration' started by korbynn, Dec 19, 2014.

  1. korbynn

    korbynn Member

    new install
    CentOS 7
    lastest version of ISPconfig

    Followed Perfect Server CentOS 7
    clamd is clamd@.service - does not start

    amavisd results in:

    [[email protected] amavisd]# service amavisd status -l
    Redirecting to /bin/systemctl status -l amavisd.service
    amavisd.service - Amavisd-new is an interface between MTA and content checkers.
    Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled)
    Active: failed (Result: start-limit) since Thu 2014-12-18 17:31:04 PST; 6min ago
    Docs: http://www.ijs.si/software/amavisd/#doc
    Process: 12897 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=227/NO_NEW_PRIVILEGES)

    Dec 18 17:31:04 server. ... systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
    Dec 18 17:31:04 server. ... systemd[1]: Unit amavisd.service entered failed state.
    Dec 18 17:31:04 server. ... systemd[1]: amavisd.service holdoff time over, scheduling restart.
    Dec 18 17:31:04 server. ... systemd[1]: Stopping Amavisd-new is an interface between MTA and content checkers....
    Dec 18 17:31:04 server. ... systemd[1]: Starting Amavisd-new is an interface between MTA and content checkers....
    Dec 18 17:31:04 server. ... systemd[1]: amavisd.service start request repeated too quickly, refusing to start.
    Dec 18 17:31:04 server. ... systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
    Dec 18 17:31:04 server. ... systemd[1]: Unit amavisd.service entered failed state.

    Can someone point me in the right direction?
    Cheers
    korbynn
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    any errors in mail log?
     
  3. korbynn

    korbynn Member

    There are no errors in maillog showing last 20 lines:

    Dec 18 13:52:38 server dovecot: imap-login: Login: user=<webmaster@ ...>, method=PLAIN, rip=::1, lip=::1, mpid=30246, secured, session=<7F6XGIIK0QAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:52:38 server dovecot: imap(webmaster@ ...): Disconnected: Logged out in=50 out=475
    Dec 18 13:53:38 server dovecot: imap-login: Login: user=<webmaster@ ...>, method=PLAIN, rip=::1, lip=::1, mpid=30267, secured, session=<KuwqHIIKEAAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:53:38 server dovecot: imap(webmaster@ ...): Disconnected: Logged out in=50 out=475
    Dec 18 13:54:38 server dovecot: imap-login: Login: user=<webmaster@ ...>, method=PLAIN, rip=::1, lip=::1, mpid=30286, secured, session=<i2u+H4IKuAAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:54:38 server dovecot: imap(webmaster@ ...): Disconnected: Logged out in=50 out=475
    Dec 18 13:55:02 server dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured, session=<BdwxIYIKLwAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:55:02 server dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=::1, lip=::1, secured, session=<FecxIYIKUQAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:55:02 server postfix/smtpd[30330]: connect from localhost[::1]
    Dec 18 13:55:02 server postfix/smtpd[30330]: lost connection after CONNECT from localhost[::1]
    Dec 18 13:55:02 server postfix/smtpd[30330]: disconnect from localhost[::1]
    Dec 18 13:55:38 server dovecot: imap-login: Login: user=<webmaster@ ...>, method=PLAIN, rip=::1, lip=::1, mpid=30359, secured, session=<bVpSI4IKogAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:55:38 server dovecot: imap(webmaster@ ...): Disconnected: Logged out in=50 out=475
    Dec 18 13:56:38 server dovecot: imap-login: Login: user=<webmaster@ ...>, method=PLAIN, rip=::1, lip=::1, mpid=30384, secured, session=<tUzrJoIK2AAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:56:38 server dovecot: imap(webmaster@ ...): Disconnected: Logged out in=50 out=475
    Dec 18 13:57:38 server dovecot: imap-login: Login: user=<webmaster@ ...>, method=PLAIN, rip=::1, lip=::1, mpid=30416, secured, session=<z7F6KoIKeAAAAAAAAAAAAAAAAAAAAAAB>
    Dec 18 13:57:38 server dovecot: imap(webmaster@ ...): Disconnected: Logged out in=50 out=475
    Dec 18 13:58:15 server dovecot: master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
    Dec 18 13:58:15 server dovecot: anvil: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
    Dec 18 13:58:15 server dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)



    Contents of journalctl -xn

    -- Logs begin at Thu 2014-12-18 12:12:12 PST, end at Fri 2014-12-19 08:51:01 PST. --
    Dec 19 08:50:55 server. ... systemd[1]: Unit amavisd.service entered failed state.
    Dec 19 08:50:55 server. ... systemd[1]: amavisd.service holdoff time over, scheduling restart.
    Dec 19 08:50:55 server. ... systemd[1]: Stopping Amavisd-new is an interface between MTA and content check
    -- Subject: Unit amavisd.service has begun shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit amavisd.service has begun shutting down.
    Dec 19 08:50:55 server. ... systemd[1]: Starting Amavisd-new is an interface between MTA and content check
    -- Subject: Unit amavisd.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit amavisd.service has begun starting up.
    Dec 19 08:50:55 server. ... systemd[1]: amavisd.service start request repeated too quickly, refusing to st
    Dec 19 08:50:55 server. ... systemd[1]: Failed to start Amavisd-new is an interface between MTA and conten
    -- Subject: Unit amavisd.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit amavisd.service has failed.
    --
    -- The result is failed.
    Dec 19 08:50:55 server. ... systemd[1]: Unit amavisd.service entered failed state.
    Dec 19 08:51:01 server. ... systemd[1]: Starting Session 2073132 of user root.
    -- Subject: Unit session-2073132.scope has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-2073132.scope has begun starting up.
    Dec 19 08:51:01 server. ... systemd[1]: Started Session 2073132 of user root.
    -- Subject: Unit session-2073132.scope has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit session-2073132.scope has finished starting up.
    --
    -- The start-up result is done.
    Dec 19 08:51:01 server. ... CROND[913]: (root) CMD (/usr/local/ispconfig/server/server.sh &> /dev/null)


    My other server is CentOS 6.5 and installed without a issue.
    I like the new stuff in CentOS 7 which I do not need to install like php 5.4 mariadb etc.
    I have not redirected the domain to this server until it is set up.
    I guess that from these logs that amavisd and clamd behave differently in CentOS 7.

    Cheers korbynn
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    The general problem with systemd is that you dont get useful error messages anymore, so its not easy to debug whats wrong when a service fails. there are no general issues with the setup on centos 7 as it is used already on many servers. Maybe its a problem with the hstname as amavis refuses to start when it does not get a fqdn hostname.
     
    jossmalo and cassola-enterprises like this.
  5. korbynn

    korbynn Member

    Just to follow up on this thread.
    On reboot my vps server is unreachable.
    I have to leave firewalld enabled but I have to stop it on a reboot/start up.
    i have ssh on 31337. having ssh on port 22 results in a lot of breakin attempts.
    then I have to service firewalld stop to open the ports.

    For some reason amavisd is running but the config is not correct.
    I kill -9 x3 amavisd processes, then amavisd -c /etc/amavisd/amavisd.conf
    this then gets the mail moving.

    now I have mailman issue which I will start another thread.
     
  6. Thank you for your best guess till!
    I edited nano /etc/hosts and used the syntax suggested instead of the one you describe in the tutorial.
    That was exactly the reason why amavisd didn't start.
    Thanks!
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    The syntax in the tutorial is fine as well, just ensure that you have no typos.
     

Share This Page