[molpro-user] BAD TERMINATION RETURENED BY MOLPRO
grant.hill at sheffield.ac.uk
Mon Apr 25 11:41:55 CEST 2016
This is a rather generic error message, but I’ve seen similar when a node runs out of memory. It might be worth double checking how much memory you are asking for (remember that Molpro works with words rather than bytes, and that the memory requested is per-process), and if other memory hungry jobs were running on the node at the same time.
> On 23 Apr 2016, at 15:22, Tanjin He <hetanjin at 163.com> wrote:
> Deal All,
> Recently something weird happened on my MOLPRO computation. When my job was almost completed, a bad termination was returned to the cluster management system. And the output file of MOLPRO didn't show any clues of possible error, but just stopped refreshing. It seemed that the MOLPRO process was killed, but I haven't done anything to disrupt the computation.
> I am sure my input file was correct because very similar cases have been calculated successfully before. So I want to ask if any of you have met with similar situation before? And how to solve this problem? Thank you very much!
> The error code from the management system is attached below.
> = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
> = PID 20083 RUNNING AT cn10238
> = EXIT CODE: 9
> = CLEANING UP REMAINING PROCESSES
> = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
> YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
> This typically refers to a problem with your application.
> Please see the FAQ page for debugging suggestions
> Best regards!
> Tanjin He
> Department of Automotive Engineering & Center for Combustion Energy
> Tsinghua University
> Email: hetanjin at 163.com
> Molpro-user mailing list
> Molpro-user at molpro.net
More information about the Molpro-user