OpenVZ Forum


Home » General » Support » Problem amavis ( Startup problem of Amavis-new service on OpenVZ)
Problem amavis [message #52116] Tue, 07 July 2015 08:59 Go to next message
Kolab is currently offline  Kolab
Messages: 1
Registered: July 2015
Junior Member
From: *fbx.proxad.net
Hello,

I just installed Kolab 3.4 on a VM OpenVZ (CentOS 7.1.1503).
Everything works fine apart from the amavisd service.
It can not start.
Result, emails are blocked in the postfix queue.
If I disable the use of amavis-new in postfix, emails can circulate.

The error code when running the service:
code = exited, status = 227 / NO_NEW_PRIVILEGES

Ok, and what can I do to fix this ?

Thank you for your help! Smile
Best Regards
Martin



[root@kolab ~]# service amavisd status
Redirecting to /bin/systemctl status 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 Mon 2015-07-06 09:23:36 EDT; 45min ago
Docs:
Process: 465 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=227/NO_NEW_PRIVILEGES)

Jul 02 05:46:43 kolab.qi.fr systemd[4235]: Failed at step NO_NEW_PRIVILEGES spawning /usr/sbin/amavisd: Invalid argument
Jul 02 05:46:43 kolab.qi.fr systemd[1]: amavisd.service: control process exited, code=exited status=227
Jul 02 05:46:43 kolab.qi.fr systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
Jul 02 05:46:43 kolab.qi.fr systemd[1]: Unit amavisd.service entered failed state.
Jul 02 05:46:43 kolab.qi.fr systemd[1]: amavisd.service holdoff time over, scheduling restart.
Jul 02 05:46:43 kolab.qi.fr systemd[1]: Stopping Amavisd-new is an interface between MTA and content checkers....
Jul 02 05:46:43 kolab.qi.fr systemd[1]: Starting Amavisd-new is an interface between MTA and content checkers....
Jul 02 05:46:43 kolab.qi.fr systemd[1]: amavisd.service start request repeated too quickly, refusing to start.
Jul 02 05:46:43 kolab.qi.fr systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
Jul 02 05:46:43 kolab.qi.fr systemd[1]: Unit amavisd.service entered failed state.
[root@kolab ~]#




[root@kolab ~]# postqueue -p
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
DD866188A082 365 Wed Jul 1 11:57:28 toto.martin@qi.fr
(connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
toto.martin@qi.fr

-- 1 Kbytes in 1 Request.
You have mail in /var/spool/mail/root
[root@kolab ~]# /etc/init.d/clamd stop



LOG
Jul 1 13:28:03 kolab clamd[3741]: SelfCheck: Database status OK.
Jul 1 13:34:48 kolab postfix/qmgr[11624]: DD866188A082: from=<toto.martin@qi.fr>, size=365, nrcpt=1 (queue active)
Jul 1 13:34:48 kolab postfix/smtp[20438]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Jul 1 13:34:48 kolab postfix/smtp[20438]: DD866188A082: to=<toto.martin@qi.fr>, relay=none, delay=5840, delays=5840/0.01/0/0, dsn=4.4.1, status=deferred (co$
Jul 1 13:38:03 kolab clamd[3741]: SelfCheck: Database status OK.
Re: Problem amavis [message #52136 is a reply to message #52116] Mon, 10 August 2015 19:51 Go to previous message
mallerton is currently offline  mallerton
Messages: 1
Registered: August 2015
Junior Member
From: *as13285.net
did you resolve this? I think you might be able to do so by removing the line NoNewPrivileges=true from /usr/lib/systemd/system/amavisd.service
Previous Topic: Installation according to wiki fails
Next Topic: Coud not start conteners form openvz 2.4.42 Centos6.1 to virtuozzo 3.10 CentOS 7.1
Goto Forum:
  


Current Time: Sun Dec 15 16:23:21 GMT 2019