#2650 closed error (fixed)

Read buffer error

Reported by: dsergeev Owned by: um_support
Component: UM Model Keywords: Nesting Suite, Dumping
Cc: Platform: Monsoon2
UM Version: 11.1

Description

Hi,

I am getting an error probably related to model dump output, but the error message is not very clear. This is the job.out output:

FILE_MANAGER:          : Unit :  15 (portio)
DUMPCTL: Opening new file  on unit  15
IO: Switching file mode to local because there is no IO server
IO: Opening unit  15 with collective(broadcast) semantics
IO: Checking consistency of unit open request...
IO: Valid request
c_io ( 15):Open: File=
c_io ( 15):c_io_unix: open: open call failed on file for unit 15
c_io ( 15):Open: File is new
IO: Open:  on unit  15

WRITING UNIFIED MODEL DUMP ON UNIT 15
#####################################

SET_DUMPFILE_ADDRESS: Dumpfile LOOKUP Address and Lengths Rewritten:
143332750 Words Stored as Data Length in FIXHD(161)
143332750 Words Used in Memory for Data 
71916375 Words Used on Disk for Data 
73038847 Words Used on Disk for Data after Rounding
73563136 Words Used on Disk in Total for the File (  588505088 Bytes)

????????????????????????????????????????????????????????????????????????????????
???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!
?  Error code: 1
?  Error from routine: c_io_rbuffering_change_mode
?  Error message: Failure to mode change in another layer means read buffer cannot be made consistent.
?  Error from processor: 0
?  Error number: 37
????????????????????????????????????????????????????????????????????????????????

============================= PBS epilogue =============================

As you can see, the error itself is in c_io_rbuffering_change_mode C-subroutine, and I don't understand what's causing it.

This error occurs at 6th time step of the regional forecast job of the Nesting Suite u-bb731. Logs are in /home/d03/deser/cylc-run/u-bb731/log.20181022T145415Z/job/20180904T0000Z/regn1_resn_1_RA1T_um_fcst_000/01

Cheers.
Denis

Change History (1)

comment:1 Changed 13 months ago by dsergeev

  • Resolution set to fixed
  • Status changed from new to closed

My bad, the reason of this error is that I accidentally switched off dumping in the um job. The error message is still pretty confusing though.

Note: See TracTickets for help on using tickets.