Univention Bugzilla – Bug 46101
Postgrey and amavis are shown as stopped in UMC system service module
Last modified: 2018-03-15 08:25:21 CET
The services postgrey and amavis are shown as stopped in UMC system service module. This is wrong since they are running: root@master421:~# ps -ef | grep -i postgrey postgrey 1339 1 0 08:29 ? 00:00:00 postgrey --pidfile=/var/run/postgrey.pid --daemonize --inet=10023 --delay=300 --max-age=35 --retry-window=48h --auto-whitelist-clients=5 --lookup-by-host --privacy --whitelist-clients=/etc/postgrey/whitelist_clients --whitelist-recipients=/etc/postgrey/whitelist_recipients root 3990 3215 0 08:36 pts/0 00:00:00 grep -i postgrey root@master421:~# ps -ef | grep -i amavisd amavis 2358 1 0 08:29 ? 00:00:02 /usr/sbin/amavisd-new (master) amavis 2762 2358 0 08:29 ? 00:00:00 /usr/sbin/amavisd-new (ch4-avail) amavis 2763 2358 0 08:29 ? 00:00:00 /usr/sbin/amavisd-new (ch3-avail) root 3992 3215 0 08:36 pts/0 00:00:00 grep -i amavisd root@master421:~# systemctl status amavis ● amavis.service - LSB: Starts amavisd-new mailfilter Loaded: loaded (/etc/init.d/amavis) Active: active (running) since Mo 2018-01-22 08:29:28 CET; 7min ago CGroup: /system.slice/amavis.service ├─2358 /usr/sbin/amavisd-new (master) ├─2762 /usr/sbin/amavisd-new (ch4-avail) └─2763 /usr/sbin/amavisd-new (ch3-avail) Jan 22 08:29:29 master421 amavis[2358]: Using primary internal av scanner code for Clam Antivirus-clamd Jan 22 08:29:29 master421 amavis[2358]: Deleting db files __db.002,__db.001,__db.003,snmp.db,nanny.db in /var/lib/amavis/db Jan 22 08:29:29 master421 amavis[2358]: Creating db in /var/lib/amavis/db/; BerkeleyDB 0.54, libdb 5.3 Jan 22 08:32:16 master421 amavis[2763]: (02763-01) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <nagios@deadlock42.intranet> -> <root@localhost>, Message-ID: <20180122072949.97F56105C41@master4...1EB1, 142993 ms Jan 22 08:32:16 master421 amavis[2762]: (02762-01) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <nagios@deadlock42.intranet> -> <root@localhost>, Message-ID: <20180122073149.907A0105C23@master4...01EB1, 26329 ms Jan 22 08:32:18 master421 amavis[2763]: (02763-02) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <root@master421.deadlock42.intranet> -> <root@master421.deadlock42.intranet>, Message-ID: <201801...101EB1, 1718 ms Jan 22 08:32:50 master421 amavis[2762]: (02762-02) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <nagios@deadlock42.intranet> -> <root@localhost>, Message-ID: <20180122073249.4CF02101EB1@master4...D101E1F, 746 ms Jan 22 08:33:49 master421 amavis[2762]: (02762-03) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <nagios@deadlock42.intranet> -> <root@localhost>, Message-ID: <20180122073349.15680101F29@master4...01011EA, 369 ms Jan 22 08:33:49 master421 amavis[2763]: (02763-03) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <nagios@deadlock42.intranet> -> <root@localhost>, Message-ID: <20180122073349.0C243101E1F@master4...01011EA, 760 ms Jan 22 08:36:09 master421 amavis[2762]: (02762-04) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <nagios@deadlock42.intranet> -> <root@localhost>, Message-ID: <20180122073609.2CFC2101EB1@master4...11011EA, 317 ms Hint: Some lines were ellipsized, use -l to show in full. root@master421:~# systemctl status postgrey ● postgrey.service - LSB: Start/stop the postgrey daemon Loaded: loaded (/etc/init.d/postgrey) Active: active (running) since Mo 2018-01-22 08:29:02 CET; 8min ago Main PID: 1339 (postgrey --pidf) CGroup: /system.slice/postgrey.service └─1339 postgrey --pidfile=/var/run/postgrey.pid --daemonize --inet=10023 --delay=300 --max-age=35 --retry-window=48h --auto-whitelist-clients=5 --lookup-by-host --privacy --whitelist-clients=/etc/p... Jan 22 08:29:02 master421 postgrey[743]: Starting postfix greylisting daemon: postgrey. Jan 22 08:29:02 master421 systemd[1]: Started LSB: Start/stop the postgrey daemon. Jan 22 08:29:02 master421 postgrey[1339]: Resolved [localhost]:10023 to [::1]:10023, IPv6 Jan 22 08:29:02 master421 postgrey[1339]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 Jan 22 08:29:02 master421 postgrey[1339]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 Jan 22 08:29:02 master421 postgrey[1339]: Duplicate configuration (TCP) on [127.0.0.1]:10023 with IPv4) - skipping Jan 22 08:29:02 master421 postgrey[1339]: Binding to TCP port 10023 on host ::1 with IPv6 Jan 22 08:29:02 master421 postgrey[1339]: Binding to TCP port 10023 on host 127.0.0.1 with IPv4 Jan 22 08:29:02 master421 postgrey[1339]: Setting gid to "137 137" Jan 22 08:29:02 master421 postgrey[1339]: Setting uid to "128" root@master421:~#
The same issue with spamassassin.
*** This bug has been marked as a duplicate of bug 43555 ***
I didn't check the resolved issues.
Nothing to release.