Re: FATAL ERROR: Unable to access config file ubq_ws_eq.log

From: Jim Phillips (jim_at_ks.uiuc.edu)
Date: Thu Nov 12 2015 - 22:45:32 CST

According to this line:

[1]+ Aborted (core dumped) ./namd2 ubq_ws_eq.conf ubq_ws_eq.log

it appears you actually ran something like this:

./namd2 ubq_ws_eq.conf ubq_ws_eq.log > ubq_ws_eq.log &

so NAMD is trying to read the .log file as its second input file.

Jim

On Thu, 12 Nov 2015, Hugo Siles wrote:

> Hello,
> I have installed NAMD_2.9_Linux-x86 under fedora 22, I run the tutor 1-2-sphere and after some prossesing I get a FATAL ERROR, I don't know if this is a specific error of the tutor,
> I run the command:
> namd2 ubq_ws_eq.conf > ubq_ws_eq.log &
> The file ubq_ws_eq.log has been created , it is in the correspondig folder
> These are the last lines :
>
>
>

WRITING VELOCITIES TO RESTART FILE AT STEP 2500
> FINISHED WRITING RESTART VELOCITIES
> The last velocity output (seq=2500) takes 0.001 seconds, 20.898 MB of mem
> ory in use
> PRESSURE: 2600 0 0 0 0 0 0 0 0 0
> GPRESSURE: 2600 0 0 0 0 0 0 0 0 0
> PRESSAVG: 2600 0 0 0 0 0 0 0 0 0
> GPRESSAVG: 2600 0 0 0 0 0 0 0 0 0
> ENERGY: 2600 227.8945 701.6813 303.3303 40.56
> 57 -22755.2308 1585.8306 2.6538 0.0000
> 4387.0055 -15506.2691 316.1452 -19893.2746 -15486.769
> 7 314.1489
>
> Info: Configuration file is ubq_ws_eq.log
> FATAL ERROR: Unable to access config file ubq_ws_eq.log
> ------------- Processor 0 Exiting: Called CmiAbort ------------
> Reason: FATAL ERROR: Unable to access config file ubq_ws_eq.log
>
> [0] Stack Traceback:
> [0:0] main+0x38 [0x81b0220]
> [0:1] __libc_start_main+0xf7 [0xb73936c7]
> Charm++ fatal error:
> FATAL ERROR: Unable to access config file ubq_ws_eq.log
>
> [0] Stack Traceback:
> [0:0] _Z8NAMD_diePKc+0x4a [0x81ac556]
> [0:1] main+0x38 [0x81b0220]
> [0:2] __libc_start_main+0xf7 [0xb73936c7]
> ^C
> [1]+ Aborted (core dumped) ./namd2 ubq_ws_eq.conf ubq_ws
> _eq.log
>
>

I will appreciate any help
>
> Hugo
>

This archive was generated by hypermail 2.1.6 : Tue Dec 27 2016 - 23:21:32 CST