mailscanner does not start after installation

Vito Arh vitoarh at yahoo.com
Fri Nov 8 10:08:41 UTC 2019


Hi all,

I tried to install mailscanner to my LXC container. Installation completed successfully. After installation I wanted to start service with command:
# service mailscanner start
Job for mailscanner.service failed because of unavailable resources or another system error.See "systemctl status mailscanner.service" and "journalctl -xe" for details.
I posted logs below. I think the problem is in "mailscanner.service: Failed to set invocation ID on control group /system.slice/mailscanner.service, ignoring: Operation not permitted"
How can I avoid that? I googled without success. Probabbly this is because LXC containter?

Thank you for your help.

Some details and logs:

# uname -a
Linux boba 4.15.18-15-pve #1 SMP PVE 4.15.18-40 (Tue, 21 May 2019 17:43:20 +0200) x86_64 GNU/Linux


# systemctl status mailscanner.service

● mailscanner.service - LSB: MailScanner daemon
   Loaded: loaded (/usr/lib/MailScanner/init/ms-init; enabled; vendor preset: enabled)
   Active: failed (Result: resources) since Fri 2019-11-08 10:55:59 CET; 3min 9s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 17588 ExecStart=/usr/lib/MailScanner/init/ms-init start (code=exited, status=0/SUCCESS)

nov 08 10:55:59 boba systemd[1]: Starting LSB: MailScanner daemon...
nov 08 10:55:59 boba ms-init[17588]:     Edit the file /etc/MailScanner/MailScanner.conf according to
nov 08 10:55:59 boba ms-init[17588]:     your needs. When complete, edit /etc/MailScanner/defaults and set
nov 08 10:55:59 boba ms-init[17588]:     the variable to enable MailScanner to run:
nov 08 10:55:59 boba ms-init[17588]:     run_mailscanner=1
nov 08 10:55:59 boba systemd[1]: mailscanner.service: PID file /var/run/MailScanner.pid not readable (yet?) after start: No such file or directory
nov 08 10:55:59 boba systemd[1]: Failed to start LSB: MailScanner daemon.
nov 08 10:55:59 boba systemd[1]: mailscanner.service: Unit entered failed state.
nov 08 10:55:59 boba systemd[1]: mailscanner.service: Failed with result 'resources'.


#journalctl -xe

nov 08 11:02:45 boba systemd[1]: mailscanner.service: Failed to reset devices.list: Operation not permittednov 08 11:02:45 boba systemd[1]: mailscanner.service: Failed to set invocation ID on control group /system.slice/mailscanner.service, ignoring: Operation not permitted
nov 08 11:02:45 boba systemd[1]: Starting LSB: MailScanner daemon...
-- Subject: Unit mailscanner.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mailscanner.service has begun starting up.
nov 08 11:02:45 boba ms-init[18374]:     Edit the file /etc/MailScanner/MailScanner.conf according to
nov 08 11:02:45 boba ms-init[18374]:     your needs. When complete, edit /etc/MailScanner/defaults and set
nov 08 11:02:45 boba ms-init[18374]:     the variable to enable MailScanner to run:
nov 08 11:02:45 boba ms-init[18374]:     run_mailscanner=1
nov 08 11:02:45 boba systemd[1]: mailscanner.service: PID file /var/run/MailScanner.pid not readable (yet?) after start: No such file or directory
nov 08 11:02:45 boba systemd[1]: Failed to start LSB: MailScanner daemon.
-- Subject: Unit mailscanner.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mailscanner.service has failed.
--
-- The result is failed.
nov 08 11:02:45 boba systemd[1]: mailscanner.service: Unit entered failed state.
nov 08 11:02:45 boba systemd[1]: mailscanner.service: Failed with result 'resources'.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20191108/3fa5b698/attachment.html>


More information about the MailScanner mailing list