named[21133]: can't fdopen tmpfile

Kevin Darcy kcd at daimlerchrysler.com
Thu Jan 3 00:47:09 UTC 2002


Looks like named lost track of its temporary files or some other process
was mucking with them at the time.


- Kevin

"England, Robert (Robert)" wrote:

> Can anyone tell what this message means? This the first time I have seen
> this. The problem appears to have resolved itself. But I would like to
> understand what it means.
>
> Thanks,
>
> -Bob
>
> Dec 18 19:28:45 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.156.HfeOrP)
> Dec 18 19:32:21 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.14.LfeOrP)
> Dec 18 19:33:08 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.24.MfeOrP)
> Dec 18 19:36:12 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.14.QfeOrP)
> Dec 18 19:39:27 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.15.VfeOrP)
> Dec 18 19:39:39 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.192.19.180.WfeOrP)
> Dec 18 19:40:32 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.14.XfeOrP)
> Dec 18 19:43:50 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.149.2feOrP)
> Dec 18 19:50:19 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.128.94.7feOrP)
> Dec 18 20:46:33 rootdns2 named[21133]: can't fdopen tmpfile
> (sec_qip/db.135.156.9geOrP)



More information about the bind-users mailing list