Hello,
I have an issue with a PES scan along a coordinate using CASSCF (aka MULTI). The input is attached.
The job simply runs without problems for some time but is eventually interrupted with a BAD TERMINATION (exit code 134, terminated by abort signal i.e. 6). The error is reported on stdout and stderr (see below) but not in the output file.
I ran this job twice and the error appeared during iteration #47 both times.
Does anybody know or see what is wrong here?
Best regards,
Alexandre Voute
command:
molpro test_scan_casscf-11e12o_cc-pvdz_220121-122419.inp -o test_scan_casscf-11e12o_cc-pvdz_220121-122419.out --no-xml-output -m 1024 -n 16 &
stdout:
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 439449 RUNNING AT lac24-27
= EXIT CODE: 134
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Aborted (signal 6)
This typically refers to a problem with your application.
stderr:
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfilerOe78m
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfileFVmVkd
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfileaZeKmh
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfilebIEv37
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfileCNZeC4
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfile7OiM2S
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfilebEjZDY
terminate called after throwing an instance of 'std::runtime_error'
what(): Cannot open cache file tmpfile8rjtuN