On Mon, Jan 03, 2022 at 03:14:32PM +1100, raf <post...@raf.org> wrote:
> On Sun, Jan 02, 2022 at 11:03:08PM -0500, Ken Wright <daddywarl...@gmail.com> > wrote: > > > On Mon, 2022-01-03 at 14:50 +1100, raf wrote: > > > On Sun, Jan 02, 2022 at 09:32:53PM -0500, Ken Wright > > > <daddywarl...@gmail.com> wrote: > > > > > > > Just checked my mail logs. Do any of these help anyone? > > > > > > > > kwright:~$ tail /var/log/mail.log > > > > [...] > > > > kwright:~$ tail /var/log/mail.err > > > > Jan 2 21:15:34 grace master[79805]: fatal: master_spawn: exec > > > > /usr/lib/postfix/sbin/0: No such file or directory > > > > [...] > > > > > > Yes! I think the reference to /usr/lib/postfix/sbin/0 > > > indicates an error in /etc/postfix/master.cf. The "0" > > > comes from the executable name in column 8. You > > > probably have a line with an extra word/column before > > > column 8, so that what should be column 7 (usually a - > > > or a number like 0 or 1) is now column 8, and it is > > > being interpreted as the name of the executable that > > > performs the service. Check for that. > > > > Right at the bottom of the file, there was a line with an extra column > > and "spawn" as the executable. I removed the superfluous - and > > restarted Postfix. The only things that have changed in the logs are > > the timestamps. > > > > Ken > > Oh well, I guess it's unrelated, then. > But whatever needed to be spawned wasn't > working either, and now that might work. > So it's still an improvement. :-) Actually, if you are still getting "/usr/lib/postfix/sbin/0: No such file or directory" messages (with new timestamps), that must mean that you didn't reload postfix after fixing master.cf. You need to do that. Reload Postfix and see if those messages stop appearing in the logs. cheers, raf
