|Posted on Friday, January 18, 2013 - 3:32 pm: |
I've come across a problem similar to, but not identical to one mentioned a few times on the boards. runall works fine for all the test jobs, and individual jobs also complete successfully from the command line of the webmo users account, but when submitting a job through WebMO we get the following. Any help appreciated.
Distributed Data Interface kickoff program.
Initiating 1 compute processes on 1 nodes to run the following command:
ERROR OPENING NEW FILE PUNCH,
ASSIGNED TO EXPLICIT FILE NAME `pwd`/$JOB.dat,
PLEASE CHECK THE -SETENV- FILE ASSIGNMENTS IN YOUR -RUNGMS- SCRIPT.
EXECUTION OF GAMESS TERMINATED -ABNORMALLY- AT Fri Jan 18 14:34:32 2013
STEP CPU TIME = 0.00 TOTAL CPU TIME = 0.0 ( 0.0 MIN)
TOTAL WALL CLOCK TIME= 0.0 SECONDS, CPU UTILIZATION IS 100.00%
DDI Process 0: error code 911
ddikick.x: application process 0 quit unexpectedly.
ddikick.x: Fatal error detected.
The error is most likely to be in the application, so check for
input errors, disk space, memory needs, application bugs, etc.
ddikick.x will now clean up all processes, and exit...
ddikick.x: Sending kill signal to DDI processes.
ddikick.x: Execution terminated due to error(s).
Post Number: 326
|Posted on Friday, January 18, 2013 - 3:35 pm: |
Make sure you are using the most recent version of WebMO, and the most recent version of GAMESS. GAMESS has made some substantial changes over the years, which requires corresponding updates in WebMO.
|Posted on Friday, January 18, 2013 - 4:45 pm: |
Thanks JR, the new GAMESS did do the trick. I was hoping to avoid the GAMESS switch, but I guess it was unavoidable.