Paul Lemmons:
> I am getting the following message in my syslog exactly every 30
> seconds. Everything is working but words like "Fatal" and "Input/output
> error" cause me an inordinate amount of angst.
>
> postfix/postqueue[<procid>]: fatal: output write error: Input/output error
Wietse:
> A write(2) operation to the standard output stream failed,
> and the last system error code was EIO (I/O error).
> ...
> What was the output from postqueue being written to?
Paul Lemmons:
> These messages are being seen in in the /var/log/mail.log on a 30
> second period. Nothing is being done (by me) outside of the normal
> processing of messages by postfix that would be causing these. No
> external process is piping anything to another program. This is a
> very vanilla setup.
The postqueue command is run for a reason. This behavior is not
built into Postfix. It scans tghe queue every 30s, and it probably
uses more CPU and disk than Postfix would otherwise use.
Historically, UNIX systems had process accounting and it was easy
to find out who ran what, when, and where.
$ lastcomm postqueue
postqueue - wietse #C:0:0x80 0.007 secs Fri Mar 1 14:42
postqueue - wietse #C:0:0x80 0.008 secs Fri Mar 1 14:41
postqueue - wietse #C:0:0x80 0.007 secs Fri Mar 1 14:41
postqueue - root __ 0.017 secs Fri Mar 1 03:01
postqueue - root __ 0.015 secs Fri Mar 1 03:01
postqueue - root __ 0.014 secs Fri Mar 1 03:01
postqueue - root __ 0.014 secs Fri Mar 1 03:01
The three lines at 14:01 are me while responding to your email.
The four lines at 03:01 are a nightly cron job.
If you don't have that, then run pstree, and wait util you get lucky.
Wietse
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
