On Tue, Jan 12, 2021 at 10:02:19PM +0000, Sudip Mukherjee wrote: > On Tue, Jan 12, 2021 at 9:36 PM Michael Grant <mgrant@grant.org> wrote: > > > > I have made this change: > > > > > > > > [Service] > > > > Type=forking > > > > ExecStart=/usr/sbin/milter-greylist > > > > Restart=on-failure > > > > PrivateTmp=true > > > > > > > > And it’s still restarting every few minutes: > > > > > > > > Jan 12 16:09:43 strange milter-greylist[255358]: racl 277 greylist [delay 300] [aw 3888000] [maxpeek -1] default > > > > Jan 12 16:09:43 strange systemd[1]: Started Greylist Mail Filter Daemon. > > > > Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Main process exited, code=exited, status=71/OSERR > > > > Jan 12 16:30:43 strange systemd[1]: milter-greylist.service: Failed with result 'exit-code'. > > > > Jan 12 16:30:44 strange systemd[1]: milter-greylist.service: Scheduled restart job, restart counter is at 2. > > > > Jan 12 16:30:44 strange systemd[1]: Stopped Greylist Mail Filter Daemon. > > > > Jan 12 16:30:44 strange systemd[1]: Starting Greylist Mail Filter Daemon... > > > > > > > > I just noticed it says ‘Scheduled restart job’, is that because it exits? Or is that because some timer is killing it? > > I think its restarting because the service file has > "Restart=on-failure". and since the main process is exiting with error > systemd thinks the service has failed and so it restarts. > To reproduce the error, do I just run milter-greylist with a > greylist.conf and Sendmail/Postfix or do I need to have real mails to > see the issue? I could probably send you my config files. I do have a fairly large database of grey listed hosts. I probably don't want to post that in the bug tracking database! For me, it runs for a while in side sendmail as a milter, I get a few messages, then it restarts. The journalctl is huge, I will forward it to you after. It doesn't seem to have any extra info.
Attachment:
signature.asc
Description: PGP signature