Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

env_case.xml error

Hi all

I have created a new case of CESM1.2.0 (res: f45_g37 compset: BRCP85CN) on a userdefined (unsupported, OS=Linux) machine. I have created the required fpftdyn input file for clm (which is not available from the svn repository and is not in the default build-namelist database), using the provided clm tools. I have also modified the file $CCSMROOT/models/lnd/clm/bld/namelist_files/namelist_defaults_clm4_0.xml to include an xml entry that points to the newly created file. The case compiled successfully.

Then, when I submitted a run, it failed immediately, giving the following error:

>"LockedFiles/env_case.xml.locked has been modified and is different than the LockedFiles version
Cannot change env_case.xml, please recover the original copy from LockedFiles"

I have not knowingly modified the file env_case.xml.The command:

>diff env_case.xml LockedFiles/env_case.xml.locked

in the $CASEROOT directory shows nothing. The error message does not make any sense to me: it appears to be saying that LockedFiles/env_case.xml.locked is different to itself. Could someone please explain to me what the intended meaning of the message is? I have tried to copy LockedFiles/env_case.xml.locked into the $CASEROOT directory and overwrite the existing env_case.xml file. This did not work. I then tried to run ./cesm_setup -clean, followed by ./cesm_setup and ./${CASEROOT}.clean_build. When I then try to rebuild, I get the same error, as when I initially tried to run the model.

Any help/explanation would be greatly appreciated.

Thanks in advance
 

jedwards

CSEG and Liaisons
Staff member
Hi Stefaan,Is it possible that your case directory cannot be read from the compute nodes?   Try something like ssh to the compute node and see if you can read the directory.   
 
Top