Opened 12 years ago

Closed 12 years ago

#100 closed help (fixed)

zero-sized .leave files

Reported by: luke Owned by: um_support
Component: UM Model Keywords: leave
Cc: Platform:
UM Version:

Description

I occasionally have a problem with my .leave files being of zero size - not just not having any output, but also lacking any header information. There doesn't seem to be any consistent way of knowing when this will happen, or how to fix it.

I am not over quota, and sometimes deleting all references to the job in the tmp directory on devt will allow for the .leave files to be written, and some times it won't.

This is causing debugging to be a very slow and annoying process - does anybody have any suggestions?

Change History (2)

comment:1 Changed 12 years ago by lois

Hello Luke,

do you mean that you have no helpful messages in your .leave file or do you mean that you get nothing in your UM diagnostic output files?

HPCx is sometimes very unhelpful because the I/O buffers are not flushed. So that when your job crashes it fails to write out all the information about the crash, it is all retained in the buffer. To flush these buffers and so get something about what happened you need to set an environment variable in the UMUI.

Go to
submodel independent → script inserts and modifications
and in the first table of environment variables set
XLFRTEOPTS
to
"namelist=old,buffering=disable_all"

You can also switch on more of the diagnostic messages via the UMUI
submodel independent → output choices

and set it to 'extra diagnostic messages'

so that you get more output and hopefully less of the interesting messages are stuck in the I/O buffer!

If you are having problems with the model diagnostic files then we will need to look at the problem again.

I hope that this helps

Lois

comment:2 Changed 12 years ago by lois

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

After an exchange of emails I hope that it will be ok if we close this ticket. Please let us know as soon as this happens again and we will investigate.
Thanks
Lois

Note: See TracTickets for help on using tickets.