Re: Error in NONMEM (78)
hi Xinting,
this error indicates that the nonmem process was terminated. Did you kill
the run perhaps by accident? Was the server you are running on rebooted? If
you are using a job scheduler (SGE / Torque / Condor / SLURM etc) it may be
that your process ran over the allotted time window (24hrs is a common
cap), and was therefore killed.
Ron
Quoted reply history
On Mon, Mar 31, 2014 at 11:15 PM, Xinting Wang <[email protected]>wrote:
> Dear all,
>
> I came across below problem using NONMEM:
>
> forrtl: error (78): process killed (SIGTERM)
> Image PC Routine Line
> Source
> nonmem 0000000000410458 Unknown Unknown Unknown
> nonmem 000000000040888B Unknown Unknown Unknown
> nonmem 00000000004AA3AA Unknown Unknown Unknown
> nonmem 0000000000541BFD Unknown Unknown Unknown
> nonmem 00000000005BACF8 Unknown Unknown Unknown
> nonmem 00000000004BCB42 Unknown Unknown Unknown
> nonmem 000000000053B396 Unknown Unknown Unknown
> nonmem 0000000000470625 Unknown Unknown Unknown
> nonmem 000000000043C744 Unknown Unknown Unknown
> nonmem 00000000004002EC Unknown Unknown Unknown
> nonmem 00000000006DC350 Unknown Unknown Unknown
> nonmem 00000000004001B9 Unknown Unknown Unknown
>
> However, the same control file and code was run successfully a few months
> ago. I tried to google this problem but little evidence could be found. It
> seems that this was caused by the Fortran language (
> http://denali.princeton.edu/intel_fc_docs/f_ug1/ug1l_rt_errors.htm)
>
> error (78): Process killed (SIGTERM)
>
> FOR$IOS_SIGTERM. The process received the signal SIGTERM. Determine source
> of this software termination signal (described in signal(3) ).
>
> Does anybody has ever come across this problem before? Thanks a lot.
>
> Best Regards
>
> --
> Xinting
>