Conference decwet::networker

572.0. "nsrd doesn't start other processes" by KAHLUA::LEMONS (And we thank you for your support.) Fri Apr 11 1997 09:46

    NetWorker Serve for Digital UNIX V4.2B with these patches:
    # setld -i | grep BRX
    BRXCKIT321                      NetWorker Digital Client Kit
    BRXCKIT422           installed  NetWorker Digital UNIX Client
    BRXP10SOAKIT422      installed  NetWorker Server Patch for Digital UNIX
    BRXP1CKIT422         installed  NetWorker Client Patch for Digital UNIX
    BRXP1SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXP3CKIT422         installed  NetWorker Client Patch for Digital UNIX
    BRXP3SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXP4SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXP5CKIT422         installed  NetWorker Client Patch for Digital UNIX
    BRXP5SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXP6SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXP7SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXP8SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXP9CKIT422         installed  NetWorker Client Patch for Digital UNIX
    BRXP9SOAKIT422       installed  NetWorker Server Patch for Digital UNIX
    BRXRNOTES422         installed  NetWorker Release Notes and
    Documentation
    BRXSMAN422           installed  NetWorker Server Reference Pages
    BRXSOAKIT422         installed  NetWorker Server for Digital UNIX
    #
    Digital UNIX V4.0a
    
    This morning we used 'nsrjb -d -S 200' to insert a NetWorker tape
    created on another server into our jukebox; this tape does not have a
    bar code label.  After the above command completed, we entered a 'nsrjb
    -I -S 200', hoping that NetWorker would then recognize that at least
    some kind of tape  was present in slot 200; instead the command hung. 
    After five minutes, we killed the process, created another process, and
    used it to issue a 'nsr_shutdown'.  We then issued a 'nsrd'.  A 'ps ax
    | grep nsr' showed that nsrd did start, and was accumulating cpu time,
    but it was not starting the other NetWorker daemons.  We finally
    shutdown our NetWorker server and reloaded it.  Still, the nsrd process
    seems to be accumulating cpu time, but the other processes aren't
    starting.
    
    # ps aux | grep nsr
    root       773 98.7  1.1 3.62M 1.4M ??       R    11:24:38    19:37.41
    /usr/bin/nsrd
    root      2011  0.0  0.1 1.57M 136K ttyp1    S  + 11:45:41     0:00.01
    grep nsr
    #
    [wait ~15 seconds]
    # ps aux | grep nsr
    root       773 98.5  1.1 3.62M 1.4M ??       R    11:24:38    19:56.77
    /usr/bin/nsrd
    root      2013  0.0  0.1 1.57M 136K ttyp1    S  + 11:46:02     0:00.01
    grep nsr
    #
    
    The /nsr/logs/daemon.log and messages logs do not show any errors. uerf
    doesn't show any errors since the system booted.
    
    What else can I check?
    
    Thanks!
    tl

    Hi
    
    All is well now; nsrd did finally start its processes.  But it took 28
    minutes to do so this time, as opposed to ~20 seconds to start firing
    them up usually.  Did that nsrjb -I -S on an un-bar coded tape
    massively confuse things?
    
    Thanks!
    tl

	It shouldn't be a problem.  If you have problems restarting
	nsrd in the future use the command 'nsrd -D5' in a window.
	It will tell you all that it is doing and might help us
	understand what the problem is.  If you try a save be sure
	that nsrexecd is running.

    Roger
    
    Thanks for the valuable tid bit; I'll file that away, and use it next
    time.
    
    tl