Date: Sat, 1 Oct 2022 12:55:18 -0700 From: Dan Mahoney <freebsd@gushi.org> To: George Mitchell <george+freebsd@m5p.com> Cc: ports@freebsd.org Subject: Re: Spamassassin fails to start Message-ID: <9B570513-E019-4C9B-933C-A8D82B8C86A1@gushi.org> In-Reply-To: <f3f18e21-2b46-571b-d0d7-21cb45fc6e9a@m5p.com> References: <25400.37159.88354.410989@jerusalem.litteratus.org> <f3f18e21-2b46-571b-d0d7-21cb45fc6e9a@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is either a disconnect between sa and the init script, or something = broken in spamassassin. Please post any relevant config snippets for spamassassin from your = rc.conf.local -- it was previously the case but may have been fixed that = the rc.d files would start it, but if you were running in debug mode, = the rc.d files could not stop it or status it. What does spamassassin --lint reveal? What do you get if you try to start spamd manually with the stock args = specified in /usr/local/etc/rc.d/sa-spamd -Dan > On Oct 1, 2022, at 12:43, George Mitchell <george+freebsd@m5p.com> = wrote: >=20 > On 10/1/22 15:12, Robert Huff wrote: >> Hello: >> On a system running: >> FreeBSD 14.0-CURRENT #0 main-dfddfe29d8: >> Thu Jul 28 11:36:59 EDT 2022 >> amd64 >> with all involved ports up to date, spamassassin fails to start >> and reports: >> Starting spamd. >> child process [90570] exited or timed out without signaling = production of a PID file: exit 255 at /usr/local/bin/spamd line 3034. >> /usr/local/etc/rc.d/sa-spamd: WARNING: failed to start spamd >> Way above my pay grade. Any idea what's going wrong? >> Respectfully, >> Robert Huff >> [...] >=20 > The first thing I'd recommend is looking in the log = (/var/log/messages) > to see if it mentions anything. If this was a fresh installation, = have > you run sa-update yet? -- George >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9B570513-E019-4C9B-933C-A8D82B8C86A1>