> On Fri, 23 Jan 1998, Jon Morby wrote:
>
> > 1998-01-23 15:59:44 queue run: process 20549 crashed with signal 139
> > while delivering 0xvj2w-0003Bj-00
> >
> > Any ideas?
>
> No. There have been a trickle of these reports in the last couple of
> weeks but no solid data. (1) Is there a core file? (2) Can you try running
>
> exim -d9 -M 0xvj2w-0003Bj-00
Yes ...
root@???:/# exim -d9 -M 0xvj2w-0003Bj-00
Exim version 1.82 jpm debug level set to 9
probably ndbm
set_process_info: 3880 1.82 jpm delivering specified messages
delivering message 0xvj2w-0003Bj-00
set_process_info: 3880 1.82 jpm delivering 0xvj2w-0003Bj-00
LOG: 0 MAIN
Spool file 0xvj2w-0003Bj-00-D not found
>
> to see whether the debugging information gives any clues as to where it
> is crashing? Can you take a copy of the offending message's -H file for
> analysis?
I have a core ... and the binary. It appears the message was
subsequently delivered however.
The 1.82 jpm refers to a couple of mods made after yesterdays
exchanges. Nothing drastic however. (yet :)
Having spoken to Dom subsequently he confessed to having rebooted the
NFS filer about 10 minutes earlier because it had run out of NFS locks.
(something somewhere had apparently grabbed over 8,000 locks on a file).
I haven't yet been able to get to the NFS server while it's in that
sort of a state to find what's causing it however :(
>
> --
> Philip Hazel University Computing Service,
> ph10@??? New Museums Site, Cambridge CB2 3QG,
> P.Hazel@??? England. Phone: +44 1223 334714
>
>
--
Jon Morby DDI: 0181 371 1286
Project Manager, Fax: 0181 371 1167
Demon Internet Ltd. The Internet for a tenner a month
--
*** Exim information can be found at
http://www.exim.org/ ***
