Re: Re [2]: cr_restart: ->cri_syscall(CR_OP_RSTRT_REAP): Invalid argument

From: Paul H. Hargrove (PHHargrove_at_lbl_dot_gov)
Date: Wed Nov 02 2005 - 14:18:22 PST

  • Next message: Michael Klemm: "Re: Re [2]: cr_restart: ->cri_syscall(CR_OP_RSTRT_REAP): Invalid argument"
      There are two possible reasons that this same file is always showing
    up in this way.  The most likely is that something in the compiled app
    has generated this file, mmaped it, and then unlinked it.  This is one
    possible way to deal with temporary files.  If this is what is
    happening, then I don't have an immediate solution for you, but I'm
    looking into it.
      The second, less likely, option is that BLCR is terribly confused.  If
    you could 'ls -l /proc/<pid>/fds' and 'cat /proc/<pid>/maps' for the
    running application, look for the /var/run/nscd file in either place and
    let me know what you find.  If it is in either place, then BLCR is not
    Christian Iwainsky wrote:
    > unfortunately there is no such file,
    > but in the message it is always the same file
    > Paul H. Hargrove schrieb:
    >> I think I may now see at least part of the problem, here:
    >> Nov  2 16:30:32 faui21l kernel: vmadump: mmap failed:
    >> /var/run/nscd/db5bHKnB (deleted)
    Paul H. Hargrove                          PHHargrove_at_lbl_dot_gov
    Future Technologies Group                 
    HPC Research Department                   Tel: +1-510-495-2352
    Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

  • Next message: Michael Klemm: "Re: Re [2]: cr_restart: ->cri_syscall(CR_OP_RSTRT_REAP): Invalid argument"