My UM vn13.9 UKESM1.1 global AMIP suite, u-dv727, is a suite I tried to rebuilt the u-dv077 that I am asking about in the other ticket. It ran for 6 month (run2) and then failed with UPANCIL problem. This needs to be addressed but I leave it with the other ticket for dv077.
Here after I tested a couple of things and put the settings back. I tried to run it from the beginning again (run4) and it now fails as soon as atmos_main starts. The error message is like this;
? Error code: 22
? Error from routine: io:buffin
? Error message: Error in buffin errorCode= 0.00 len=0/27648
? Error from processor: 0
? Error number: 62
Similarly to before, there is no difference between run2 and run4 as far as I’m aware. In fact if I go to /home/users/masaru.yoshioka.ext/cylc-run/u-dv725 and do
diff run2/app/um/rose-app.conf run4/app/um/rose-app.conf
it doesn’t return anything at all. Although I cannot completely rule out the possibility that I did something on run2/app/um/rose-app.conf after it ran, I don’t think it is very likely based on the dates of the file (run2/app/um/rose-app.conf is older than pe_output).
Right before the error message, the pe_output (dv725.fort6.pe000) shows this;
Unit 40 open on filename /home/users/masaru.yoshioka.ext/cylc-run/u-dv725/run4/share/data/etc/ancil/qrclim.sulpdms
--> File Type: 1 , Read Only: T , Write Only: F
--> Local: T AllLocal: F Remote: F Broadcast: T
--> Local: T AllLocal: F Remote: F Broadcast: T
---End File States ----------------------
I set PRINT_STATUS=PrStatus_diag in another suite u-dv763 where I was having the same problem, but it didn’t provide any additional info. Can anybody see the problem?
I’ve been really confused with these mysterious behaviours of the model runs. I hope anybody can provide some advice.
Thanks.
Masaru