Restarting on 30th March

[anton-seaice]

I attempted to restart from the 30th of March, and got this error on every MOM PE:

FATAL from PE   233: diag_time_inc: Invalid date. Date=1900-04-31 00:00:00

Image              PC                Routine            Line        Source             
access-om3-MOM6-C  0000000002E3B0B4  mpp_mod_mp_mpp_er          72  mpp_util_mpi.inc
access-om3-MOM6-C  0000000002C50ED5  fms_mod_mp_fms_er         536  fms.F90
access-om3-MOM6-C  0000000002BDE466  diag_util_mod_mp_        1336  diag_util.F90
access-om3-MOM6-C  0000000002BD9A82  diag_util_mod_mp_        1256  diag_util.F90
access-om3-MOM6-C  0000000002B9A28E  diag_manager_mod_         575  diag_manager.F90
access-om3-MOM6-C  00000000026F2275  mom_diag_manager_         213  MOM_diag_manager_infra.F90
access-om3-MOM6-C  0000000001E00E81  mom_diag_mediator        2524  MOM_diag_mediator.F90
access-om3-MOM6-C  0000000001E00372  mom_diag_mediator        2378  MOM_diag_mediator.F90
access-om3-MOM6-C  0000000001DFE8DA  mom_diag_mediator        2120  MOM_diag_mediator.F90
access-om3-MOM6-C  0000000001DFE315  mom_diag_mediator         947  MOM_diag_mediator.F90
access-om3-MOM6-C  0000000001C3FB81  mom_mp_initialize        2979  MOM.F90
access-om3-MOM6-C  0000000001BB8AE2  mom_ocean_model_n         284  mom_ocean_model_nuopc.F90
access-om3-MOM6-C  0000000001B8F29C  mom_cap_mod_mp_in         695  mom_cap.F90
access-om3-MOM6-C  00000000009F0FB2  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F4B0F  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000B4B39A  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000B37EE5  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F23EA  Unknown               Unknown  Unknown
access-om3-MOM6-C  000000000050CACA  Unknown               Unknown  Unknown
access-om3-MOM6-C  000000000075B321  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000983860  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009AAF81  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F0FB2  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F4B0F  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000B4B39A  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000B37EE5  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F23EA  Unknown               Unknown  Unknown
access-om3-MOM6-C  000000000050CACA  Unknown               Unknown  Unknown
access-om3-MOM6-C  000000000075B321  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000983860  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009AAE6B  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009B46CB  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F0FB2  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F4B0F  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000B4B39A  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000B37EE5  Unknown               Unknown  Unknown
access-om3-MOM6-C  00000000009F23EA  Unknown               Unknown  Unknown
access-om3-MOM6-C  000000000050CACA  Unknown               Unknown  Unknown
access-om3-MOM6-C  000000000075B321  Unknown               Unknown  Unknown
access-om3-MOM6-C  0000000000431CE8  MAIN__                    128  esmApp.F90
access-om3-MOM6-C  00000000004316CD  Unknown               Unknown  Unknown
libc-2.28.so       000015112C45D7E5  __libc_start_main     Unknown  Unknown
access-om3-MOM6-C  00000000004315EE  Unknown               Unknown  Unknown

We are using FMS 2023.02, it looks like this might have been fixed in a 2023.02.01 patch, so i didn't investigate further.

Ill tag this against to be hopefully addressed in a future 0.4.0 access-om3 release