[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nfcreate error 5010

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: nfcreate error 5010
  • Date: Wed, 27 Jun 2001 16:26:39 -0600
Steve,

> First off, his problem wasn't on babyblue, it was on
> chipeta. I realize his email to Russ was awfully unclear
> about that (particularly since the only machine mentioned
> by name in the mail was babyblue). No wonder you couldn't
> find the error code! Second, he's only experiencing it on batch
> jobs. On UNICOS, an error code of 5010 is an internal
> library error indicating that the library got an ENOMEM
> (out of memory) on an internal call to malloc.
> 
> I'm assuming that when netcdf called fopen, the fopen failed
> because buffer space couldn't be allocated.  My assumption is that
> he hit either his job or job step memory limit. I told him
> to increase both of them. I haven't heard back since.

Thanks!  I'll file this in our searchable netcdf support database (it
gets done automatically by CC:ing to support-netcdf) so we can find it
the next time someone asks about "error 5010".

--Russ