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

CESM2.1.4 case_run error: without any hist output nc files

wilma wang

Wilma Wang
New Member
Dear all,
I recently ported CESM2.1.4 to our computer cluster, which has no internet connection. I tried running the F2000climo compset for the test.
The case_create/case_setup/case_build/case_submit steps were finished successfully.
However, I encountered an error during the case_run step: the model run had already been finished, there are some rest ncfiles in the cesm_run directory but not any output nc_file. And the PBS work was still running until it was killed due to a walltime limitation.
1752821703564.png
Attached are the run_cesm.sh file, the cesm.log file(tar file), and the three porting XML files.
Any comments are welcome!
Thanks all!
Wilma W.
 

Attachments

  • run_cesm214.sh.txt
    686 bytes · Views: 1
  • cesm_run.log.tar
    780 KB · Views: 7
  • config_batch.xml.txt
    28.9 KB · Views: 0
  • config_compilers.xml.txt
    47 KB · Views: 0
  • config_machines.xml.txt
    1.9 KB · Views: 0

rrbuchholz

Rebecca Buchholz
CSEG and Liaisons
Staff member
It looks like the error from the cesm.log file that the model tries to write to an atmosphere restart file
Opened file F2000climo_f09_f09_mg17.cam.r.0001-01-06-00000.nc to write
2818048
But comes up with the errors:
NetCDF: Variable not found
NetCDF: Invalid dimension ID or name
WARNING: Rearr optional argument is a pio2 feature, ignored in pio1
and then fails.
Stack trace terminated abnormally.
[mpiexec@node-0-16.local] HYDU_sock_write (utils/sock/sock.c:286): write error (Bad file descriptor)
[mpiexec@node-0-16.local] HYD_pmcd_pmiserv_send_signal (pm/pmiserv/pmiserv_cb.c:169): unable to write data to proxy
[mpiexec@node-0-16.local] ui_cmd_cb (pm/pmiserv/pmiserv_pmci.c:79): unable to send signal downstream
[mpiexec@node-0-16.local] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status
[mpiexec@node-0-16.local] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:198): error waiting for event
[mpiexec@node-0-16.local] main (ui/mpich/mpiexec.c:344): process manager error waiting for completion

There doesn't seem to be any help in the atm.log file.

I'm sorry, I'm not sure what might be going on. I think this would be a question for software engineers.
 
Vote Upvote 0 Downvote
Top