FATAL ERROR: Unable to access config file temp14.conf

From: Charles Hoying (choying_at_usc.edu)
Date: Thu Aug 16 2018 - 20:44:17 CDT

Hi NAMD users,

I am working on submitting a NAMD job remotely on a computing network. I
have submitted the job no problem from one directory, but am unable to
submit in a neighboring directory.

My process creates a .conf file using VMD, and then inputs it to NAMD.
Specifically the error messages I get:

----------------------(everything is fine until here)

Info) Exiting normally.
[hpc-login2:10135] mca: base: component_find: unable to open
/usr/usc/openmpi/1.8.4/lib/openmpi/mca_plm_tm: libtorque.so.2: cannot open
shared object file: No such file or directory (ignored)
[hpc-login2:10135] mca: base: component_find: unable to open
/usr/usc/openmpi/1.8.4/lib/openmpi/mca_ras_tm: libtorque.so.2: cannot open
shared object file: No such file or directory (ignored)
[hpc-login2:10135] 58 more processes have sent help message
help-mpi-btl-base.txt / btl:no-nics
[hpc-login2:10135] Set MCA parameter "orte_base_help_aggregate" to 0 to see
all help / error messages
[hpc-login2:10135] 17 more processes have sent help message
help-mpi-btl-base.txt / btl:no-nics
[hpc-login2:10135] 11 more processes have sent help message
help-mpi-btl-base.txt / btl:no-nics
[hpc-login2:10135] 15 more processes have sent help message
help-mpi-btl-base.txt / btl:no-nics
[hpc-login2:10135] 18 more processes have sent help message
help-mpi-btl-base.txt / btl:no-nics
------------- Processor 0 Exiting: Called CmiAbort ------------
Reason: FATAL ERROR: Unable to access config file temp14.conf

[hpc-login2:10135] 98 more processes have sent help message
help-mpi-api.txt / mpi-abort
submit pulling 14-th, pid=

---------------------(end error message)

There are a lot of mpi errors, none of which I got from the other
directory, but I get them every time here for some reason, even though I am
sourcing the same mpi installation.

I checked the file permissions, and they are identical to the temp14.conf
file from the adjacent directory, so I have no idea why the program would
be unable to access it. I read the file as well, and it doesn't seem to be
corrupted.

Any ideas?

Thanks,
Charlie Hoying

This archive was generated by hypermail 2.1.6 : Wed Dec 04 2019 - 23:20:09 CST