Andy Mell <amell@???> writes:
> I am getting errors from exim every now and again which
> cause perfectly valid
> messages to be frozen. The error is:
>
> appendfile transport process returned a non-zero status
> (0x000b)
>
> Any ideas?
and John Horne <J.Horne@???> writes, inter alia:
> All started okay and exim delivered the messages really fast! However, two
> things then happened. 1) Messages started to freeze with the error "smtp
> transport process returned a non-zero status (0x008b)", [...]
>
> So, first of all any ideas what the 008b status from the stmp transport is?
Isn't it self-evident that these two-byte status codes are those returned
by wait(2) and relatives for a completed process; i.e. one byte of exit()
code and one byte of flags + signal number? [Well, obviously it isn't...]
These processes were terminated by signal 11, i.e. SIGSEGV on all systems
known to me.
Of course, this doesn't get one much further without more diagnosis of the
failing processes. At least in John Horne's example it seems to have made
a "core" file somewhere (indicated by the 0x0080 bit).
Chris Thompson Cambridge University Computing Service,
Email: cet1@??? New Museums Site, Cambridge CB2 3QG,
Phone: +44 1223 334715 United Kingdom.
--
* This is sent by the exim-users mailing list. To unsubscribe send a
mail with subject "unsubscribe" to exim-users-request@???
* Exim information can be found at http://www.exim.org/
